Summary: Subject Area Security Model in OAC
Content (required):
I'm looking to implement an object level security model. For example purposes, I will reference 2 users (Alice & Bob), 3 Groups (HR: ReadOnly, HR: ContentDev, & Finance: ContentDev) and 2 Subject Areas (Headcount Analytics, Finance Analytics)
Setting the stage:
Alice is part of the HR: ReadOnly & HR: ContentDev groups.
Bob is part of the HR: ReadOnly & Finance: ContentDev groups.
The intent of these groups are as follows:
HR: ReadOnly (DV Consumer) - should have access to view DV content that was created with the Headcount Analytics subject area.
HR: ContentDev (DV ContentAuthor) - should have access to view & create DV content with the Headcount Analytics subject area.
Finance: ContentDev (DV ContentAuthor) - should have access to view & create DV content with the Finance Analytics subject area.
Goal behavior:
Bob is able to see content created with the Headcount Analytics subject area but is unable to create content with the Headcount Analytics subject area. He should be able to create content with the Financial Analytics subject area.
Alice is able to see content created with the Headcount Analytics subject area but is unable to see anything create with the Financial Analytics subject area and is unable to create any content with the Financial Analytics subject area.
Current Behavior:
If we restrict the Headcount Analytics subject area in the RPD permissions - we remove the ability for Finance: ContentDev users to create with the subject area, however, if those users are also members of HR: ReadOnly it removes all visibility of data within the content created with the Headcount Analytics subject area.
Version (include the version you are using, if applicable):
Code Snippet (add any code snippets that support your topic, if applicable):