Schema permission sets
💡 Permission on Schemas (who can view, edit)
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, virtual types always have View for all applied. | No effect, fieldsets and relationships always have View for all applied. |
Edit (manage items) |
| No effect | Able to create new virtual items in the content browser. | No effect |
Manage (schema) |
|
|
|
|
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 a tagbox, or fieldset and relationship items assigned to a layer that you do not have permission 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.