| Assign a role to a user | If this permission is not granted, the user cannot see the Assign role option in Project Settings > Team > Members. |
| Can add app installations | If this permission is not granted, the Explore apps banner is hidden in the Apps section of the UI. Projects where this permission is not granted to the user do not display on the project selector dropdown for new app installations. |
| Can create content permissions | If this permission is not granted, users cannot see the Add permission option in the Public Content API, roles, and PATs sections of the project settings. |
| Can create new permanent auth tokens | This permission allows users to create new permanent auth tokens. If this permission is not granted, users can't see the + Add Token button at the top of the Permanent Auth Tokens screen in Project Settings. |
| Can delete app installations | If this permission is not granted, the user cannot see the Uninstall app option in the app cards context menu. |
| Can delete content permissions | If this permission is not granted, users cannot see the Delete option for content permissions in the Public Content API, roles, and PATs sections of the project settings. |
| Can delete existing permanent auth tokens | This permission allows users to delete permanent auth tokens. If this permission is not granted, users can't see the Delete option inside the context menu of permanent auto tokens in the Access section of Project Settings. |
| Can read content permissions | If this permission is not granted, the user cannot see the Content permissions block for roles and PATs. |
| Can read existing permanent auth tokens | This permission allows users to see the Access section in Project Settings. If you want to give someone access to the API Playground, this permission needs to be granted, along with Can see API Playground, because on the Playground, we load Auth Tokens to show them on the dropdown. |
| Can see Role & Permissions Settings | If this permission is not granted, the user cannot see the Roles menu in the project settings. |
| Can see schema view | View permission that allows a user to see the Schema builder. You can choose to deselect this permission to hide the schema view for roles for which it's not relevant. |
| Can see Team Member Settings | If this permission is not granted, the user cannot see the Members tab in Project Settings > Team. |
| Can update app installations | This permission grants the user the ability to see the Edit button on app cards. |
| Can update content permissions | If this permission is not granted, users cannot see the Edit option for content permissions in the Public Content API, roles, and PATs sections of the project settings. |
| Can update existing permanent auth tokens | This permission allows users to edit permanent auth tokens. If this permission is not granted, users can't see the Edit option inside the context menu of permanent auto tokens in the Access section of Project Settings. |
| Can use the playground | If this permission is not granted, the users cannot see the API Playground in the top-level menu, and the Preview in playground option in the Content editor and Assets. |
| Change the name, picture and description of a project | This permission allows users to edit the project details in Project Settings > General > Project. The whole section will be visible but grayed out and read-only if this permission is not granted. |
| Create a new environment backup | This permission allows creating a new environment backup. |
| Create locales | This permission allows users to create new locales in a project. If this permission is not granted, users cannot use the Add button at the top of the existing locales in Project Settings > General > Locales. |
| Create new components | If this permission is not granted to a user who has the Can see schema view permission, they will be able to access the Schema builder, but will not be able to use the + Add button to create new components. |
| Create new entries | This permission grants you the ability to create new entries. If you do not select it, the user will not see the + Add entry button at the top right corner of the content editor screen. |
| Create new enumerations | If this permission is not granted to a user who has the Can see schema view permission, they will be able to access the Schema builder, but will not be able to use the + Add button to create new enumerations. |
| Create new environment | If this permission is not granted, the Clone button in Project Settings > General > Environments is disabled. |
| Create new fields | If this permission is not granted, the user cannot see the Fields side panel in the schema builder. |
| Create new models | If this permission is not granted to a user who has the Can see schema view permission, they will be able to access the Schema builder, but will not be able to use the + Add button to create new models. |
| Create new roles | If this permission is not granted, the user cannot see the option to add a custom role in the UI. |
| Create new webhooks | If this permission is not granted, the user cannot see the + Add webhook button. |
| Create public content views | Enable this permission to allow users to create custom content views in the content editor. If this permission is not granted, users won't see the Add custom view button at the top of the screen. |
| Create public view groups | This permission grants users the ability to create view groups. |
| Create remote sources | If this permission is not granted to a user who has the Can see schema view permission, they will be able to access the Schema builder, but will not be able to see the + Add button to create new remote sources. |
| Create stages | This permission allows users to see the + Add stage button in Project Settings > General > Content Stages. |
| Create taxonomy | If this permission is granted to a user who has the Can see schema view permission, they will be able to access the Schema builder, and view the Nodes amd Settings tab of the taxonomy. Additionally, Users need the Create taxonomy node permission to use the + Add button to create a taxonomy. |
| Create taxonomy node | If this permission is granted to a user who has the Can see schema view permission, they will be able to access the Schema builder, and view the Nodes amd Settings tab of the taxonomy. Users can use the + Add child node button to add new taxonomy nodes. If they have the Create taxonomy permission, they can use the + Add button to create a taxonomy. |
| Delete an existing environment | If this permission is not granted, the Delete and Promote to master options in Project Settings > General > Environments are disabled. |
| Delete an existing environment backup | This permission allows deleting an existing environment backup. |
| Delete an existing role | If this permission is not granted, the user cannot see the Delete option for custom roles. |
| Delete an existing webhook | This permission grants users the ability to see the Delete option for webhooks. |
| Delete existing components | If this permission is not granted, the user cannot see the Delete option inside a component's context menu. |
| Delete existing entries | This permission grants you the ability to delete entries. If this is not selected, you will not see the Delete button. |
| Delete existing enumerations | This permission allows users to delete enumerations. If this permission is not granted, users can't see the Delete option inside the context menu at the top of the enumeration details screen. |
| Delete existing fields | This permission allows users to see the Delete option inside the context menu of the fields added to a model in the Schema builder and delete the field. Users must be able to read the schema and models to reach this screen. |
| Delete existing models | If this permission is not granted, the user cannot see the Delete option for models in the UI. |
| Delete locales | This permission allows users to delete locales in a project. If this permission is not granted, users cannot use the Delete button next to locales in Project Settings > General > Locales. |
| Delete public content views | This permission allows the user to delete custom views. If this permission is not granted, users cannot see the Delete custom view option inside the context menu at the top of the custom view screen. |
| Delete public view groups | If this permission is not granted, the user will get logged out when attempting to use the Delete button for public view groups. |
| Delete remote sources | If this permission is not granted, users cannot see the Delete option for remote sources. |
| Delete stages | If this permission is not granted, the Delete option in Project Settings > General Content Stages will throw an error when the user clicks on it. |
| Delete taxonomy | This permission allows users to delete a taxonomy. If this permission is not granted, users can't see the Delete option inside the context menu at the top of the taxonomy details screen. |
| Delete taxonomy node | This permission allows users to delete taxonomy node. If this permission is not granted, users can't see the Delete option next to the taxonomy node. |
| Invite a user into an existing project | If this permission is not granted, the user cannot see the Invite members button in Project Settings > Team > Members. |
| Promote an existing environment | If this permission is not granted, the user will get an error when using the Promote to master button in Project Settings > General > Environments. |
| Publish non-published entries | This permission allows users to publish entries that exist only in the DRAFT stage (entries that have been saved but never published). |
| Read audit logs | If this permission is not granted, users cannot see the Audit logs tab in Project Settings. |
| Read existing environment backups and their details | This permission allows reading existing environment backups and their details. |
| Read existing webhooks | If this permission is not granted, the user cannot see the Webhooks tab in Studio's main navigation |
| Remove a user from an existing project | This permission grants users the ability to see the Remove option for users. |
| Restore an existing environment backup to a standard environment | This permission allows restoring an existing environment backup to a standard environment. |
| Update an existing environment | This permission grants the ability to edit environments through the API. |
| Update an existing environment backup | This permission allows updating an existing environment backup. |
| Update existing components | This permission grants users the ability to edit the information in the Settings tab of components. To reach this screen, users will need permissions to read the schema and models.
If an entry is in the DRAFT stage, you can update and save it, but as soon as it's updated, if you do not have permission to update published entries, you won't be able to keep working on it. |
| Update existing enumerations | This permission grants users the ability to edit enumeration details. To reach this screen, users will need permissions to read the schema and enumerations. |
| Update existing fields | This permission allows users to see the Edit button on the field cards in models, and edit the field details. Users must be able to read the schema and models to reach this screen.
If this permission is not granted, users cannot see the Edit field button, and the drag-and-drop anchor is not displayed. |
| Update existing models | This permission grants users the ability to edit the information in the Settings tab of models. To reach this screen, users will need permissions to read the schema and models. |
| Update existing non published entries | This permission allows the user to save a content entry without publishing. If this permission is disabled, the user won't see the Save button at the top-right corner of content entries and will only see the Publish button. |
| Update existing webhooks | If this permission is not granted, the user cannot see the Edit button for webhooks. |
| Update published entries | This permission grants you the ability to update published entries. If this is not selected, when an entry is published, you do not see the Save button. |
| Update stages | If this permission is not granted, the user cannot see the Content stages option in their project settings. |
| Update system content views | If this permission is not granted, the user cannot see the Update default view in the Content editor and in Assets. |
| Update existing roles | If this permission is not granted, the user can open all existing roles, but all update-related buttons will be hidden, and they will get an error when attempting to edit content permissions. |
| Update locales | This permission allows users to edit locales in a project. If this permission is not granted, when users go to Project Settings > General > Locales, they will find that the locales are read-only and are grayed out. |
| Update public content views | This permission allows the user to edit custom views. If this permission is not granted, users cannot see the Edit custom view option inside the context menu at the top of the custom view screen. |
| Update public view groups | If this permission is not granted, you cannot update view groups. |
| Update remote sources | This permission grants users the ability to edit the information in the Settings tab of remote sources. To reach this screen, users will need permissions to read the schema and remote sources.
If this permission is not granted, the user can reach the Settings screen, but the Save button is hidden. |
| Update taxonomy | This permission allows users to update a taxonomy. If this permission is not granted, users can't modify any details in the taxonomy Settings page, or add any child nodes. |
| Update taxonomy node | This permission allows users to update a taxonomy node. If this permission is not granted, users can't add a new child node, rename or move the rename or move the node to another parent, and can only view details in the taxonomy Settings page. |