Team Permissions¶
Team permissions control what actions users can perform on datastores and their associated data assets. Each team is assigned a single permission level that applies to all datastores assigned to that team.
Note
Admins are not subject to team permissions and can access all data assets. Team permissions only apply to users with the Manager and Member roles. For platform-level permissions, see the User Roles documentation.
Tip
Admins can preview the platform as a single-team Manager by enabling Team Restriction Mode. This is helpful for demonstrating team permissions or diagnosing access issues reported by Members and Managers.
Permission Hierarchy¶
Permissions follow a hierarchical model. Higher permissions include all capabilities of lower permissions:
| Level | Permission | Includes |
|---|---|---|
| 5 | Editor | Editor + Author + Drafter + Viewer + Reporter |
| 4 | Author | Author + Drafter + Viewer + Reporter |
| 3 | Drafter | Drafter + Viewer + Reporter |
| 2 | Viewer | Viewer + Reporter |
| 1 | Reporter | Reporter only |
Permission Matrix¶
Legend:
- The permission grants the ability to perform the action
- The permission does not grant the ability to perform the action
| Action | Reporter | Viewer | Drafter | Author | Editor |
|---|---|---|---|---|---|
| Datastores | |||||
| View Source Datastore | |||||
| Preview Source Datastore | |||||
| Edit Datastore Settings | |||||
| Edit Quality Score Settings | |||||
| Delete Source Datastore | |||||
| Create Source Datastore (single or multi-schema) 11 | |||||
| Use an Existing Connection (add a datastore to it, test it, discover its catalogs, schemas, or paths) 12 | |||||
| View Enrichment Datastore | |||||
| Preview Enrichment Datastore Containers | |||||
| Delete Enrichment Datastore | |||||
| Link / Change Enrichment Destination | |||||
| Edit Enrichment Settings | |||||
| Operations | |||||
| View Activity | |||||
| Run & Manage Operations (Sync, Profile, Scan, External Scan, Materialize, Export, Promote) | |||||
| Schedule Operations (Sync, Profile, Scan, Materialize, Export) | |||||
| Create/Delete Computed Asset (as owner) | |||||
| Create/Delete Computed Asset (any owner) | |||||
| Reassign Computed Asset owner | |||||
| Lineage | |||||
| View Datastore Lineage / Impact Analysis | |||||
| View OpenLineage Job / Run Details | |||||
| Create / Edit / Delete Lineage Connections | |||||
| Ingest OpenLineage Events | |||||
| Profiles | |||||
| View Profiles | |||||
| Delete Profiles they started 3 | |||||
| Quality Checks | |||||
| View Checks | |||||
| Create Draft Checks | |||||
| Save New Check as Draft / Restore Archived Check to Draft | |||||
| Create / Edit Active Checks | |||||
| Activate / Validate Check | |||||
| Edit Check Metadata | |||||
| Archive / Delete Checks | |||||
| Dry Run Check | |||||
| Anomalies | |||||
| View Anomalies (including Description and Assignees fields) | |||||
| View Anomaly Source Records | |||||
| Change Anomaly Status (Acknowledge / Archive) | |||||
| Edit Anomaly Description | |||||
| Add / Remove Anomaly Assignees | |||||
| Link / Unlink External Ticket on Anomaly 4 | |||||
| Timeline 1 | |||||
| View the Timeline and its Comments | |||||
| Add Comment on the Timeline | |||||
| Reply to a Comment | |||||
| Edit Own Comment | |||||
| Delete Own Comment | |||||
| Edit Another User's Comment 2 | |||||
| Delete Another User's Comment 2 | |||||
| Tags | |||||
| View Tags | |||||
| Assign Tags to Datastores, Containers, and Fields | |||||
| Assign Tags to Draft Quality Checks | |||||
| Assign Tags to Active Quality Checks | |||||
| Assign Tags to Anomalies | |||||
| Create / Edit / Delete the Team's Own Tags 10 | |||||
| Datastore Groups | |||||
| View Datastore Groups | |||||
| Assign Datastore to Group | |||||
| Flows 8 | |||||
| View Flows and Executions Related to the Datastore 9 | |||||
| Create / Edit / Execute / Delete Flows Related to the Datastore | |||||
| AI Use Cases 5 | |||||
| View AI Use Case & Attestations | |||||
| Create / Edit / Delete AI Use Case 6 | |||||
| Capture Baseline | |||||
| Submit for Review / Reopen Draft 6 | |||||
| Generate Attestation | |||||
| Certify / Revoke AI Use Case 7 | |||||
| Field Status | |||||
| View Field Status | |||||
| Mask / Unmask Field | |||||
| Exclude Field | |||||
| Restore Field | |||||
| Delete Field | |||||
| Merge Fields | |||||
| View Masked Field Values 13 |
Tag rules span two axes
Managing tag definitions (create, update, delete) depends on the tag's scope. Admins manage every tag. A team tag can also be managed by any user whose team holds the Editor team permission, whatever their user role. Global tags are Admin-only. Applying an existing tag to an asset, in contrast, is a team-permission action gated by the rows above. Users with the Manager user role do not bypass the team-permission gate for tag application: they must still hold the required team permission (Editor for datastores, containers, and fields; Drafter for draft quality checks; Author for active quality checks and anomalies) on the asset's datastore. Only Admin users bypass both axes.
AI Use Case authoring and certification are separate tiers
An Author on every bound datastore assembles the use case: bindings, schedule, baseline, and the immutable attestations. Moving the certification itself takes the Manager user role plus Editor on every bound datastore, so the person who prepares the evidence is not the person who signs it off. An Author can submit their work for review and reopen a draft; only a Manager of the data (or an Admin) can mark it Certified or revoke a certification. Reading a use case and its attestations needs Viewer - a Reporter cannot see governance records at all.
Computed Asset ownership
Computed Assets (Computed Tables, Computed Files, Computed Joins, and Computed Fields) follow a hybrid ownership model. Authors can create, edit, and delete computed assets they personally own. Editors can manage any computed asset on the datastore regardless of owner, and only Editors can reassign ownership to another user. Ownership covers the definition, not the run: profiling, scanning, and materializing a computed asset stay on the Editor permission even for the owner. For a cross-datastore Computed Join, the user also needs at least Viewer permission on the right-side datastore to use its containers as join inputs.
Lineage across datastores
Creating, editing or deleting lineage connections, and submitting OpenLineage changes, requires Editor on every affected datastore, including connections an event retires. OpenLineage job/run details require Viewer on every managed endpoint. A container graph can still show connected assets outside the user's team scope; seeing a node grants no edit permission. Unrestricted Admins have global access; an Admin restricted to a team follows that team's permissions. See Lineage Permissions.
Individual Permissions¶
For detailed descriptions of each permission level, see the individual pages:
-
Editor
Full datastore management: enrichment, operations, computed fields, and field status.
-
Author
Quality check management: activate, validate, and manage check lifecycle.
-
Drafter
Check creation: create and save checks as drafts for future activation.
-
Viewer
Read access: view anomalies, source records, and comment on the Timeline.
-
Reporter
Report access: dashboards, overviews, and analytical insights.
-
The Timeline rows in this table cover containers, quality checks, and anomalies, which are scoped by datastore teams. A check template also has a Timeline, but a template does not belong to a datastore, so team permissions do not apply there: any user with the Member user role (or higher) can read a template's Timeline, comment, reply, and manage their own comments, even a user whose team permission is Reporter. ↩
-
Deleting another user's comment requires the Admin user role, which is not bound by team permissions. Editing another user's comment is never allowed, for anyone. ↩↩
-
An Editor can delete only the Profile operations they started. Deleting a Profile someone else started requires the Admin user role, which is not bound by team permissions. ↩
-
In addition to the Author team permission on the anomaly's datastore, linking or unlinking an external ticket also requires the platform-wide Manager user role (or higher). Users with only the Author team permission but a Member user role cannot use the ticket link/unlink actions. ↩
-
An AI Use Case has no teams of its own. It derives every permission from the datastores it binds, and the requirement must hold on all of them - a use case spanning three datastores is only as accessible as its weakest binding. A user who loses access to one bound datastore stops seeing the use case entirely, rather than seeing a partial and misleading view of its governed inputs. Binding a container or a quality check is governed by the permission on that asset's datastore. ↩
-
Authoring an AI Use Case follows the same hybrid ownership model as Computed Assets. A user with the Member user role and the Author team permission can create use cases and edit, delete, baseline, and generate evidence for the ones they own; the Manager user role can author any use case, provided it holds Author on every bound datastore. The Admin user role is not bound by team permissions and can author any use case. Ownership is set at creation and never changes. Creating a use case with nothing bound yet still requires Author on at least one datastore. ↩↩
-
Certifying or revoking is gated at both layers, like datastore creation. It requires the Manager user role (or higher) plus the Editor team permission on every bound datastore. The Manager user role alone does not bypass the team permission. The Admin user role can certify or revoke any use case. This is deliberately not an authoring permission: an Author submits their work for review, and a Manager of the data signs it off. See AI Use Cases for the certification lifecycle. ↩
-
A Flow is shown only to users who can see every datastore it names: the datastores in its trigger filter (including the ones an is not any of filter excludes), its operation and anomaly actions, and its Global Export destination. Any team permission on a datastore counts, Reporter included. If one of those datastores is only on teams the user is not on, the Flow is left out of the Flows list, its filters, Global Search, tag pages, and the executions list, and opening its link shows an error and returns to the Flows list. A Flow that names no datastore, including one that reaches every datastore because its filters are empty, is shown to every user. Admins see every Flow. ↩
-
Creating a datastore is gated at both layers. It requires the Manager user role (or higher) plus the Editor team permission on at least one team the new datastore is assigned to (the Public team when none is chosen). No team permission grants it on its own, and the Manager role alone does not bypass the team permission: a Manager whose teams all sit below Editor cannot create datastores. The same rule applies to the multi-schema flow. See Multiple-Schema Permissions. Adding the datastore to an existing connection also needs the Editor team permission on a datastore that already uses that connection. ↩
-
Using a saved connection is gated at both layers, like creating a datastore. It requires the Manager user role (or higher) plus the Editor team permission on at least one datastore that already uses the connection. A connection that no datastore uses yet needs only the Manager role. No team permission grants it on its own. A connection used only by datastores on teams the user is not on does not appear in the connection list. See Manage Connections. ↩
-
Editor is the only permission that reveals masked values without restriction, and it is required on every reveal surface: Anomaly Source Records, Quality Check Dry Runs, Field Profile histograms, and Export/Materialize outputs. Data Preview is the single exception: there, an Author can also reveal the masked fields that are Computed Fields they own. Any other masked field in that same preview stays masked, and the reveal is recorded in the masking audit log exactly like an Editor's. An Author with no owned masked computed field in the container cannot reveal anything. ↩