[MAGNOLIA-7891] CT-Apps: Hint at the need to set permissions when workspace is created Created: 08/Sep/20  Updated: 27/Oct/21

Status: Selected
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Jan Schulte Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File product.yaml     File products-app.yaml    
Issue Links:
causality
is causing MAGNOLIA-7892 DOC: Setting permissions when a CT wo... Open
duplicate
is duplicated by MGNLUI-6196 Content types are not considered in u... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Content Types phase 2
Story Points: 2

 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.

See tutorial: https://documentation.magnolia-cms.com/display/DOCS62/Part+II+-+Complex+content+types+and+security+set+up#PartII-Complexcontenttypesandsecuritysetup-Settingupsecurity

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

 
 



 Comments   
Comment by Simon Lutz [ 30/Sep/20 ]
  • register content type -> new workspace is created
  • 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

See tutorial: https://documentation.magnolia-cms.com/display/DOCS62/Part+II+-+Complex+content+types+and+security+set+up#PartII-Complexcontenttypesandsecuritysetup-Settingupsecurity

  • add this section to the docu section on content types (not in the tutorial only) mdrapela
  • turning this ticket into an improvement: hint at the need to set permissions when workspace is created
    • workspace permissions in ACL & app permissions
Generated at Mon Feb 12 04:27:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.