Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
Description
The current flow is as follows:
- registering a content type will create a new workspace
- this new workspace has no permissions set
- hence superuser can access this new workspace, but for any other role permissions would need to be explicitly set first - which some may miss and be confused about.
We will add this section to the docu section on content types (not in the tutorial only); mdrapela.
AC of this ticket:
- hint at the need to set permissions when workspace is created
- consider workspace permissions in ACL & app permissions
Checklists
Acceptance criteria
Attachments
Issue Links
- is causing
-
MAGNOLIA-7892 DOC: Setting permissions when a CT workspace has been created
-
- Open
-
- is duplicated by
-
MGNLUI-6196 Content types are not considered in ui-admincentrals appLauncherLayout
-
- Closed
-