# Reporter

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

The Reporter permission is the most restricted team access level in Qualytics. It provides read-only access to report-related information: dashboards, overviews, profiles, checks, anomalies, and observability data. Reporters can view and analyze data to generate insights without the ability to modify anything.

## Who Should Have Reporter Access?

Reporter is designed for **executives**, **compliance officers**, and **external auditors** who need to:

- View datastore overviews and activity summaries, and open enrichment datastores from the tree
- Access dashboards and observability metrics
- Review quality check configurations and anomaly summaries
- Monitor data quality trends across datastores
- Generate analytical insights from available data

> **Tip**
>
> Reporter is the right choice for stakeholders who need **visibility into data quality metrics** without interacting with the data directly. They can see what checks exist and what anomalies were found, but cannot drill into individual source records.

## Includes

Reporter is the base permission level; it does not include any other permissions.

## Capability Table

| Action | Reporter |
| --- | --- |
| **Datastores** |  |
| View Source Datastore | Allowed |
| Preview Source Datastore | Not 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 | Not 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 | Not allowed |
| View OpenLineage Job / Run Details | Not 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 | Not 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 | Not allowed |
| Reply to a Comment | Not allowed |
| Edit Own Comment | Not allowed |
| Delete Own Comment | Not 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 | Not 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**
>
> Reporters can read a Timeline and every comment on it, but **cannot** preview datastore content, view anomaly source records, or comment on the Timeline of a container, a quality check, or an anomaly; those capabilities require the [Viewer](https://userguide.qualytics.io/settings/access/teams/team-permissions/viewer/) team permission. Check templates are the exception: a template does not belong to a datastore, so team permissions do not apply to its Timeline and any user with the **Member** user role (or higher) can comment there. A Reporter can open an enrichment datastore, but browsing its containers requires Viewer.

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