# Team Permissions

Source: https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/

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](https://userguide.qualytics.io/settings/access/users/roles/overview/) documentation.

> **Tip**
>
> Admins can preview the platform as a single-team Manager by enabling [Team Restriction Mode](https://userguide.qualytics.io/using-the-platform/web-app/top-right-menu/user-profile/team-restriction/). 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**](https://userguide.qualytics.io/settings/access/teams/team-permissions/editor/) | Editor + Author + Drafter + Viewer + Reporter |
| 4 | [**Author**](https://userguide.qualytics.io/settings/access/teams/team-permissions/author/) | Author + Drafter + Viewer + Reporter |
| 3 | [**Drafter**](https://userguide.qualytics.io/settings/access/teams/team-permissions/drafter/) | Drafter + Viewer + Reporter |
| 2 | [**Viewer**](https://userguide.qualytics.io/settings/access/teams/team-permissions/viewer/) | Viewer + Reporter |
| 1 | [**Reporter**](https://userguide.qualytics.io/settings/access/teams/team-permissions/reporter/) | Reporter only |

## Permission Matrix

Legend:

- Allowed The permission grants the ability to perform the action
- Not allowed The permission does not grant the ability to perform the action

| Action | Reporter | Viewer | Drafter | Author | Editor |
| --- | --- | --- | --- | --- | --- |
| **Datastores** |  |  |  |  |  |
| View Source Datastore | Allowed | Allowed | Allowed | Allowed | Allowed |
| Preview Source Datastore | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Edit Datastore Settings | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Edit Quality Score Settings | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Delete Source Datastore | Not allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| Create Source Datastore (single or multi-schema) [11](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:datastore-create-manager) | Not allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| Use an Existing Connection (add a datastore to it, test it, discover its catalogs, schemas, or paths) [12](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:connection-use) | Not allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| View Enrichment Datastore | Allowed | Allowed | Allowed | Allowed | Allowed |
| Preview Enrichment Datastore Containers | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Delete Enrichment Datastore | Not allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| Link / Change Enrichment Destination | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Edit Enrichment Settings | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| **Operations** |  |  |  |  |  |
| View Activity | Allowed | Allowed | Allowed | Allowed | Allowed |
| Run & Manage Operations (Sync, Profile, Scan, External Scan, Materialize, Export, Promote) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Schedule Operations (Sync, Profile, Scan, Materialize, Export) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Create/Delete Computed Asset (as owner) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Create/Delete Computed Asset (any owner) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Reassign Computed Asset owner | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| **Lineage** |  |  |  |  |  |
| View Datastore Lineage / Impact Analysis | Not allowed | Allowed | Allowed | Allowed | Allowed |
| View OpenLineage Job / Run Details | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Create / Edit / Delete Lineage Connections | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Ingest OpenLineage Events | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| **Profiles** |  |  |  |  |  |
| View Profiles | Allowed | Allowed | Allowed | Allowed | Allowed |
| Delete Profiles they started [3](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:profile-delete) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| **Quality Checks** |  |  |  |  |  |
| View Checks | Allowed | Allowed | Allowed | Allowed | Allowed |
| Create Draft Checks | Not allowed | Not allowed | Allowed | Allowed | Allowed |
| Save New Check as Draft / Restore Archived Check to Draft | Not allowed | Not allowed | Allowed | Allowed | Allowed |
| Create / Edit Active Checks | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Activate / Validate Check | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Edit Check Metadata | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Archive / Delete Checks | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Dry Run Check | Not allowed | Not allowed | Allowed | Allowed | Allowed |
| **Anomalies** |  |  |  |  |  |
| View Anomalies (including Description and Assignees fields) | Allowed | Allowed | Allowed | Allowed | Allowed |
| View Anomaly Source Records | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Change Anomaly Status (Acknowledge / Archive) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Edit Anomaly Description | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Add / Remove Anomaly Assignees | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Link / Unlink External Ticket on Anomaly [4](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:ticket-manager) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| **Timeline** [1](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:comment-template) |  |  |  |  |  |
| View the Timeline and its Comments | Allowed | Allowed | Allowed | Allowed | Allowed |
| Add Comment on the Timeline | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Reply to a Comment | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Edit Own Comment | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Delete Own Comment | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Edit Another User's Comment [2](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:comment-admin) | Not allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| Delete Another User's Comment [2](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:comment-admin) | Not allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| **Tags** |  |  |  |  |  |
| View Tags | Allowed | Allowed | Allowed | Allowed | Allowed |
| Assign Tags to Datastores, Containers, and Fields | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Assign Tags to Draft Quality Checks | Not allowed | Not allowed | Allowed | Allowed | Allowed |
| Assign Tags to Active Quality Checks | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Assign Tags to Anomalies | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Create / Edit / Delete the Team's Own Tags [10](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:team-tags) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| **Datastore Groups** |  |  |  |  |  |
| View Datastore Groups | Allowed | Allowed | Allowed | Allowed | Allowed |
| Assign Datastore to Group | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| **Flows** [8](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:flow-related) |  |  |  |  |  |
| View Flows and Executions Related to the Datastore [9](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:flow-view) | Allowed | Allowed | Allowed | Allowed | Allowed |
| Create / Edit / Execute / Delete Flows Related to the Datastore | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| **AI Use Cases** [5](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:ai-use-case-scope) |  |  |  |  |  |
| View AI Use Case & Attestations | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Create / Edit / Delete AI Use Case [6](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:ai-use-case-owner) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Capture Baseline | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Submit for Review / Reopen Draft [6](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:ai-use-case-owner) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Generate Attestation | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Certify / Revoke AI Use Case [7](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:ai-use-case-certify) | Not allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| **Field Status** |  |  |  |  |  |
| View Field Status | Allowed | Allowed | Allowed | Allowed | Allowed |
| Mask / Unmask Field | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Exclude Field | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Restore Field | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Delete Field | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Merge Fields | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| View Masked Field Values [13](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#fn:masked-computed-owner) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |

> **Note: Tag rules span two axes**
>
> Managing tag definitions (create, update, delete) depends on the tag's scope. Admins manage every tag. A [team tag](https://userguide.qualytics.io/tags/deep-dive/team-tags/) 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.

> **Note: 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.

> **Note: 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.

> **Note: 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](https://userguide.qualytics.io/lineage/deep-dive/permissions/#team-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.

  [Editor](https://userguide.qualytics.io/settings/access/teams/team-permissions/editor/)
- **Author**

  Quality check management: activate, validate, and manage check lifecycle.

  [Author](https://userguide.qualytics.io/settings/access/teams/team-permissions/author/)
- **Drafter**

  Check creation: create and save checks as drafts for future activation.

  [Drafter](https://userguide.qualytics.io/settings/access/teams/team-permissions/drafter/)
- **Viewer**

  Read access: view anomalies, source records, and comment on the Timeline.

  [Viewer](https://userguide.qualytics.io/settings/access/teams/team-permissions/viewer/)
- **Reporter**

  Report access: dashboards, overviews, and analytical insights.

  [Reporter](https://userguide.qualytics.io/settings/access/teams/team-permissions/reporter/)

---

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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](https://userguide.qualytics.io/recipes/data-suitability/deep-dive/ai-use-cases/) for the certification lifecycle.
8. A Flow relates to the datastores in its trigger filter, its operation and anomaly actions, and its Global Export destination. Managing it needs the **Editor** team permission on every one of them, whatever the user role, and on every datastore when the Flow reaches all of them. A Flow that relates to no datastore needs no team permission. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/).
9. 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.
10. Held through the team, not a datastore: an Editor team manages its own [team tags](https://userguide.qualytics.io/tags/deep-dive/team-tags/), whatever the members' user roles. The **Public** team is the exception. Its tags count as global, so only Admins manage them.
11. 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](https://userguide.qualytics.io/source-datastore/datastore/multi-schema/permissions/). Adding the datastore to an existing connection also needs the **Editor** team permission on a datastore that already uses that connection.
12. 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](https://userguide.qualytics.io/settings/connections/manage-connections/).
13. **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](https://userguide.qualytics.io/fields/computed-fields/getting-started/) they own. Any other masked field in that same preview stays masked, and the reveal is recorded in the [masking audit log](https://userguide.qualytics.io/fields/field-status/concepts/field-masking/#masking-audit-log) exactly like an Editor's. An Author with no owned masked computed field in the container cannot reveal anything.

*Last updated: November 5, 2026.*
