Permission Sets
- Elaine Foley
Create a Content Permission Set
Click create
Provide name
Set exclusive, meaning overwriting all other permissions when applied e.g. for embargo or archival.
Save
After Creating the Content Permission Set
On the right side set Role Permissions (permission level per role, e.g. only admins can view, edit & delete)
On the left side set Permission Set Permissions (which role can apply this permission set, e.g. only admins can apply and manage this permission set)
Create a Schema permission set
Click create
Provide name
Set exclusive, meaning overwriting all other permissions when applied e.g. for embargo or archival.
Save
After Creating the Schema Permission Set
On the right side add Role Permissions (permitted content modifications per role e.g. product can mange the schema, dealers can view the schema and its items)
On the left side add permission set permissions (permitted access to this specific permission set per role e.g. product can apply the schema permission set)
Add Permission Set to Schema
To add a schema permission set to a schema :
Open Schemas
Find your schema and doubleclick to open the details.
On the right side find “Permissions”
Add one or multiple Permission Sets
Validate the permissions using the matrix.
Save.
* Disable the View for all button, which grants view for all permission by default on schema creation.
Checking the Effective Permissions on a Schema
After adding permissions to a schema you can check the effective permissions using the permission matrix. There you see the (1) applied permission sets with exclusive ones listed in the permission set name and you find the matrix (2) which shows how these permission sets are combined and which permissions are active on the schema e.g. in the screenshot Editor Corporate do not have access anymore.
Open the Permissions and find the permission matrix.
Use the switches next to the Permission Sets to check the effects of disabling/unassigning them.
General Remarks
The advanced view of the permissions applied to a Content Item is not restricted and can be seen by all users that have access to the content item. Please note this is for display only and does not remove Permission Sets from the schema itself.
Permission Matrix
As you can see in the above screenshot there are three permission sets applied to this schema, and the default “View for all”. As you can see the applied permission sets build on each other. The effective permissions are displayed in the matrix. I can also see what they would be if I removed the permission set for example by turning the slider on or off for each permission set. Please note this is for display only and does not remove permission sets from the schema itself.
In the case of exclusive permission sets, these will negate any non-exclusive permission sets applied. In this example, I have added an Schema managebly by product | Exclusive permission set to the example above. As you can see the negated permissions are denoted with a red cross:
If View for all is also enabled this effectively gives all users View permission on the schema.