Details
-
Bug
-
Resolution: Fixed
-
Critical
-
1.3.0
-
None
Description
Thanks to the Modular Privilege Pattern and Default Groups concept, we now have default groups OOTB for editors, developers, etc. in the product itself.
Meanwhile, content-types still only grant workspace access to superuser, and !content-type apps are generated with superuser permissions as well (clone this ticket in MGNLUI to infer differently). See https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/browse/magnolia-ui-framework-jcr/src/main/resources/contenttypes/appTemplate.ftl#19
Solution intent
Apps from regular modules are responsible for providing their own roles for apps and add them to the default groups (e.g. editors).
In case of content-types, we'd have to create a role programmatically and assign it as well to the editors group (upon registration). Superuser is clearly insufficient for this concept.