Skip to main content
Some permissions only work when a role also grants another one. For example, a user with Update on Manage Silver Entities still can’t save an entity unless they can also update the pipeline it belongs to. Use the tables below when you build a role, or when a user has a permission but the related button is missing, disabled, or fails when they use it. Feature names match the permission matrix. All records means the permission applies to every connection or pipeline, not to specific records.
The permission matrix turns on a group’s top-level feature, such as Instance Settings, and Admin App Access when you grant any permission inside the group. It doesn’t add Read when you grant Update, so add both where a table lists both.

Data Connections

Manage Data Connection Settings and Manage Data Connection Resources apply to every connection. They only take effect on connections the user can also read under Manage Data Connections.

Data Pipelines

Instance Settings

Access Control

Application Permissions

Troubleshooting

If a user has a permission but the feature still doesn’t work, find the task in the tables above and check that their roles grant everything in the Also needed column. Remember that roles are additive: the user needs the permission from at least one assigned role. Changes take effect within about a minute.

Roles and permissions

Create roles and assign them to users

Troubleshooting

Common issues and solutions for user management