[MGNLCT-188] Editors cannot see content-types apps by default Created: 11/Oct/21 Updated: 14/Oct/21 Resolved: 14/Oct/21 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | 1.3.0 |
| Fix Version/s: | 1.3.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Mikaël Geljić | Assignee: | Evzen Fochr |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
| Epic Link: | Sane Default Roles & Groups |
| Sprint: | SaaS 19 |
| Story Points: | 5 |
| 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 intentApps 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. |