Schema Permission Sets

You can apply Schema Permission Sets only to schemas (List, Layer, Virtual Type and Fieldset&Relation). Not to File Types. Your role must at least have Apply permissions in the Permission Set Permissions of each permission set and have at least Manage permissions on the schemas.

Permission

What it means for lists

What it means for layers

What it means for virtual types

What it means for fieldsets and relationships

View for all applied

see view below.

see view below.

Always applied, cannot be changed.

Always applied, cannot be changed.

View

  • No effect if View for all applied.

  • Able to apply list items on content with sufficient content permissions.

  • Able to apply list items to a list with sufficient schema permissions.

  • Able to see the list if you have the user role permission Manage list items.

  • A user with View permission on a content item and a layer will see any referenced list item and the card view without the eye icon.

  • View permissions on the list are also required in order to be able to add its fields to a channel filter (User Role Manage Channels required)

  • JSON Export the list together with User Role Permission ManageListItems.

  • No effect if View for all applied.

  • Able to apply the layer to content if the user has sufficient content permissions.

  • A user with View permission on a content item will see the assigned layers the user has View permissions on. The user will not see any layer applied to the content item where the user has no View permission on the layer.

  • JSON Export the layer together with User Role Permission Manage metadata schema.

No effect, virtual types always have View for all applied.

No effect, fieldsets and relationships always have View for all applied.

Edit (manage items)

  • Able to add new list items while tagging

  • Able to add/remove/edit list items in the list

  • Able to add new list items with Excel

  • Able to add new list items with JSON import. You will need the user role permission Manage Metadata schema to create new lists

No effect

Able to create new virtual items in the content browser.

No effect

Manage (schema)

  • Able to create/manage/delete lists with the user role permission Manage metadata schema.

  • Able to add/remove schema permission sets where the user has the permission set permission Apply

  • Able to create/manage/delete layer with the User Role Permission Manage metadata schema.

  • Able to add/remove schema permission sets where the user has the permission set permission Apply.

  • Able to create/manage/delete virtual types with the User Role Permission Manage metadata schema.

  • Able to add/remove schema permission sets where the user has the permission set permission Apply.

  • Able to create/manage/delete fieldsets and relationships with the User Role Permission Manage metadata schema.

  • Able to add/remove schema permission sets where the user has the permission pet permission Apply.

Schema permission not applied

Only the owner of the list and users with the Super Admin user role assigned have access to the list unless View for All is enabled.

Only the owner of the layer and users with the Super Admin user role assigned have access to the layer unless View for All is enabled.

No effect, virtual types always have View for all applied.

No effect, fieldsets and relationships always have View for all applied.

A content item can still be updated even if it contains tagbox, or fieldset and relationship items assigned to a layer that you do not have permissions to edit (no view permission on the list the tagboxes are in). If you have permissions on a content item you can find it via the search with search terms that are in layers you have no permissions to see.