Permission Sets

Create a Content Permission Set

1. Open Content permission sets

2. Click create

3. Provide name

   1. Set exclusive, meaning overwriting all other permissions when applied e.g. for embargo or archival.

4. Save

After Creating the Content Permission Set

1. On the right side set Role Permissions (permission level per role, e.g. only admins can view, edit & delete)

2. 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)

Open

Creating a content permission set for embargo content, only applicable by admins, where the content items are only available to admins.

Create a Schema permission set

1. Open Schema permission sets

2. Click create

3. Provide name

   1. Set exclusive, meaning overwriting all other permissions when applied e.g. for embargo or archival.

4. Save

After Creating the Schema Permission Set

1. 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)

2. 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)

Open

Schema permission set to manage a product list with product managing items and dealers only viewing items.

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.

Open

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 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 applied permission sets (1) and the resulting permission for the roles (2) shown in a matrix.

1. Open the Permissions and find the permission matrix.

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

Open

How to Check Permission Using Matrix by showing and hiding permission sets.

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

Open

The applied permission sets (1) and the toggle to show/hide this specific set (2) and the resulting permission for the roles (3) shown in a 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:

Open

Exclusive negates the permissions for Editor Corporate.

If View for all is also enabled this effectively gives all users View permission on the schema.

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

Open

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. Unassign permission sets one by one

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

VIDEO: How to Remove all Permission Sets from Content

Open

Unassign permission sets one by one.

Delete a Permission Set

1. Open Content Permission Set or Schema Permission Set

2. Select your Permission Set

3. Look for the delete icon 

   Open

   

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

5. Confirm your desire to delete. 

Open

Picturepark will not allow to delete a permission set that is still in use.

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.