Create Use Case Documentation (DOCU-176)

[DOCU-225] Controlling access to areas and components Created: 14/Nov/11  Updated: 31/Dec/14  Resolved: 31/Dec/14

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Neutral
Reporter: Antti Hietala Assignee: Antti Hietala
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:

 Description   

Write a use case how to configure permissions to sub-page elements. Demonstrate that Magnolia CMS has fine-grained access control beyond the page level.

  • Do a proof of concept based on the story.
  • If story is not feasible, or there is a better way to demonstrate granular access, document on the wiki page.
  • Figure out what nodes to set ACLs on to control permissions at dialog and component level.
  • Decide on a level of maturity for this use case. Should this be considered merely an approach (abstract, high-level, requires heavy customization like Multilanguage structure) or an actual procedure with complete step-by-step instructions and screenshots?


 Comments   
Comment by Ruth Stocks [ 31/Dec/14 ]

Documented at:

Generated at Mon Feb 12 01:07:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.