Permission Sets

Create a Permission Set

1. Open Permission Set

2. Select Content or Schema Permission

3. Provide details

4. Save

After Creating the Permission Set

1. Add Role Permissions (permitted content modifications per role)

2. Add Permission Set Permissions (permitted access to this specific Permission Set per role)

Add Permission Set to Schema

To add Permission Set to a schema :

• Select your schema.

• Click on Permissions and add one or multiple Permission Sets

  • The selected ones are shown before assigning them. 

• Disable the View for all button. It is currently enabled per default on the creation of a schema.

• Click on the Save button.

VIDEO: How to Add Permission Set to a Schema (List, Layer):

Checking the Effective Permissions on a Schema

After adding permissions to a schema you can check the effective permissions on the schema. 

1. Click on Permissions and then show advanced

2. Use the switches next to the Permission Sets to check the effects of disabling/unassigning them. 

VIDEO: How to Check Permission Using Matrix:

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 two permission sets applied to this schema. As you can see the applied permission sets build on each other. The effective permissions are displayed. 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. 

As you can see the applied permission sets build on each other unless there are exclusive permission sets. In the case of exclusive permission sets, these will negate any non-exclusive permission sets applied. In this example, I have added an Archived (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) then you will see this reflected in the advanced view:

Access Permission Set in Search or Filter

The Permission Sets of a Content Item are saved in a field called: 

permissionSetIds

Therefore you can access Permission Sets via this field in Display Pattern, Filter, Query Filter, or searches. 

Access Permission Set in Sidebar Filter

Some default system fields are used to aggregate Ids from Picturepark system items e.g. permissionSetIds or layerSchemaIds or contentSchemaId and display them in Filters. 

1. Open Filters

2. Add a new Filter

3. Select Permission

4. Save

Update a Permission Set

1. Open Permission

2. Select Permission Set

3. Update

4. Save

Update View for All or Exclusive

Enabling View for all in the schema settings applies View Permission to the Schema for all users in the Picturepark.

View for all is independent of applied permission sets. Please note that exclusive permission sets will not turn off View for all. If you are applying an exclusive permission set that is intended to "turn off" other non-exclusive permission please do not forget to also disable View for all.

Remove all Permission Sets from Content

1. Open the Content Item

2. Clicking on Remove All will remove all permission sets. 

3. See "View for all" still switched on (not affected by "Remove All" function)

VIDEO: How to Remove all Permission Sets from Content:

Delete a Permission Set

1. Open Permission

2. Select your Permission Set

3. Look for the delete icon 

   

4. Choose delete from the context menu or the toolbar in the browser or detail view

5. Confirm your desire to delete. 

VIDEO: How to Delete in the Browser View

Delete Content Assigned to a Permission Set

To find the Content Items assigned to a Permission Set (Content) you can filter or search in the Content Browser.