Roles (deprecated)
Deprecated, see Access Control
Overview
You can assign Users and Access Tokens to different roles that come with different sets of permissions.
Roles
You can assign Users and Access Tokens to the following roles:
AdminEditorViewer
The API role is a legacy role that you could assign to Access Tokens but that is no longer available for new access tokens. Existing tokens with the API role still work.
Permissions
Each role comes with a given set of permissions on the various Sifflet objects. Unless specified, the following matrix applies regardless of how you are trying to access the information (UI, API, CLI, etc.).
| Scope | Admin | Editor | Viewer |
|---|---|---|---|
| INTEGRATIONS | |||
| Secrets management (create, edit, delete) | ✅ | ❌ | ❌ |
| Integrations management (create, edit, delete, trigger run) | ✅ | ✅ | ❌ |
| Submit dbt metadata files and trigger the related data source refresh (API only) | ✅ | ✅ | ❌ |
| Create declarative pipeline & edge lineage (API only) | ✅ | ❌ | ❌ |
| DATA CATALOG | |||
| Data catalog search | ✅ | ✅ | ✅ |
| Data assets (read) | ✅ | ✅ | ✅ |
| Data assets (edit - manual or through AI suggestions) | ✅ | ✅ | ❌ |
| Preview data | ✅ | ✅ | ❌ |
| MONITORS | |||
| Monitors (read)(overview, runs, details) | ✅ | ✅ | ✅ |
| Show failing rows | ✅ | ✅ | ❌ |
| Data point qualification on monitors' runs | ✅ | ✅ | ❌ |
| Monitors (create, edit, delete, trigger run) | ✅ | ✅ | ❌ |
| INCIDENTS | |||
| Incidents management (assignment, closing) | ✅ | ✅ | ❌ |
| SETTINGS | |||
| Business Glossary (read) | ✅ | ✅ | ✅ |
| Business Glossary (create, edit, delete) | ✅ | ✅ | ❌ |
| Tags (read) | ✅ | ✅ | ✅ |
| Tags (create, edit, delete) | ✅ | ✅ | ❌ |
| Domains (read, create, edit, delete) | ✅ | ❌ | ❌ |
| Users (read, create, edit, delete) | ✅ | ❌ | ❌ |
| Access Tokens (read, create, delete) | ✅ | ❌ | ❌ |
| SSO (read, create, edit, delete) | ✅ | ❌ | ❌ |
| Alert Destinations (read, create, edit, delete) | ✅ | ❌ | ❌ |
Updated 11 days ago
Did this page help you?

