# Viewer

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

The Viewer permission provides read access to datastore content, anomalies, and source records. Viewers can browse data, review anomaly details, and comment on the Timeline of containers, quality checks, and anomalies to document their observations. This is the standard read-access permission for most users.

## Who Should Have Viewer Access?

Viewer is designed for **business analysts**, **stakeholders**, and **team members** who need to:

- Review anomalies and their source records to understand data quality issues
- Comment and reply on the Timeline of containers, quality checks, and anomalies for collaboration and documentation
- Preview datastore content, including the containers in an enrichment datastore
- View tags assigned to assets

> **Tip**
>
> Viewer is the minimum permission level required to see **anomaly source records** and **preview datastore content**. Reporters can see anomaly summaries but cannot drill into individual records.

## Includes

Viewer includes all capabilities of **Reporter**.

## Capability Table

| Action | Viewer |
| --- | --- |
| **Datastores** |  |
| View Source Datastore | Allowed |
| Preview Source Datastore | Allowed |
| Edit Datastore Settings | Not allowed |
| Delete Source Datastore | Not allowed |
| Multi-Schema Datastore Creation | Not allowed |
| Use an Existing Connection | Not allowed |
| View Enrichment Datastore | Allowed |
| Preview Enrichment Datastore Containers | Allowed |
| Delete Enrichment Datastore | Not allowed |
| Link / Change Enrichment Destination | Not allowed |
| Edit Enrichment Settings | Not allowed |
| **Operations** |  |
| View Activity | Allowed |
| Run & Manage Operations | Not allowed |
| Schedule Operations | Not allowed |
| Create/Delete Computed Asset (as owner) | Not allowed |
| Create/Delete Computed Asset (any owner) | Not allowed |
| Reassign Computed Asset owner | Not allowed |
| **Lineage** |  |
| View Datastore Lineage / Impact Analysis | Allowed |
| View OpenLineage Job / Run Details | Allowed |
| Create / Edit / Delete Lineage Connections | Not allowed |
| Ingest OpenLineage Events | Not allowed |
| **Profiles** |  |
| View Profiles | Allowed |
| Delete Profiles | Not allowed |
| **Quality Checks** |  |
| View Checks | Allowed |
| Create Draft Checks | Not allowed |
| Save New Check as Draft / Restore Archived Check to Draft | Not allowed |
| Create / Edit Active Checks | Not allowed |
| Activate / Validate Check | Not allowed |
| Edit Check Metadata | Not allowed |
| Archive / Delete Checks | Not allowed |
| Dry Run Check | Not allowed |
| Set Check Owner / Default Anomaly Assignee | Not allowed |
| **Anomalies** |  |
| View Anomalies | Allowed |
| View Anomaly Source Records | Allowed |
| Change Anomaly Status (Acknowledge / Archive) | Not allowed |
| Edit Anomaly Description | Not allowed |
| Assign Users to Anomaly | Not allowed |
| **Timeline** |  |
| View the Timeline and its Comments | Allowed |
| Add Comment on the Timeline | Allowed |
| Reply to a Comment | Allowed |
| Edit Own Comment | Allowed |
| Delete Own Comment | Allowed |
| Edit Another User's Comment | Not allowed |
| Delete Another User's Comment | Not allowed |
| **Tags** |  |
| View Tags | Allowed |
| Assign Tags to Datastores, Containers, and Fields | Not allowed |
| Assign Tags to Draft Quality Checks | Not allowed |
| Assign Tags to Active Quality Checks | Not allowed |
| Assign Tags to Anomalies | Not allowed |
| Create / Edit / Delete the Team's Own Tags | Not allowed |
| **Datastore Groups** |  |
| View Datastore Groups | Allowed |
| Assign Datastore to Group | Not allowed |
| **Flows** |  |
| View Flows and Executions Related to the Datastore | Allowed |
| Create / Edit / Execute / Delete Flows Related to the Datastore | Not allowed |
| **AI Use Cases** |  |
| View AI Use Case & Attestations | Allowed |
| Create / Edit / Delete AI Use Case | Not allowed |
| Capture Baseline | Not allowed |
| Submit for Review / Reopen Draft | Not allowed |
| Generate Attestation | Not allowed |
| Certify / Revoke AI Use Case | Not allowed |
| **Field Status** |  |
| View Field Status | Allowed |
| Mask / Unmask Field | Not allowed |
| Exclude Field | Not allowed |
| Restore Field | Not allowed |
| Delete Field | Not allowed |
| Merge Fields | Not allowed |
| View Masked Field Values | Not allowed |

> **Note**
>
> Viewers **cannot** create or modify quality checks, change anomaly status, or manage tags. For check creation, the [Drafter](https://userguide.qualytics.io/settings/access/teams/team-permissions/drafter/) team permission is required. For anomaly triage, the [Author](https://userguide.qualytics.io/settings/access/teams/team-permissions/author/) team permission is required.

> **Note: Comments on the Timeline**
>
> 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. On an archived asset, existing comments stay readable, but no comment can be added, edited, or deleted while the asset stays archived.

> **Note: Flows and connections**
>
> A Flow is shown only to users who can see every datastore it names, and any team permission is enough to see a datastore. Managing a Flow needs **Editor** on every datastore it relates to. Reusing a saved connection (adding a datastore to it, testing it, or discovering its schemas) needs the **Manager** user role plus **Editor** on a datastore that already uses the connection. A saved connection that no datastore uses yet needs only the **Manager** user role. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#who-sees-a-flow) and [Manage Connections](https://userguide.qualytics.io/settings/connections/manage-connections/).

> **Note: AI Use Cases**
>
> An AI Use Case takes its permissions from the datastores it binds, and the team permission must hold on all of them. With the **Member** user role, an **Author** can edit, delete, capture a baseline for, submit, and generate attestations only for the use cases they created. The **Manager** user role can author any use case, provided it holds **Author** on every bound datastore. Certifying or revoking needs the **Manager** user role plus **Editor** on every bound datastore, so no team permission grants it on its own. The **Admin** user role is not bound by team permissions and can author, certify, or revoke any use case. See [AI Use Cases](https://userguide.qualytics.io/recipes/data-suitability/deep-dive/ai-use-cases/).

> **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).

*Last updated: November 5, 2026.*
