Skip to content

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
Preview Source Datastore
Edit Datastore Settings
Delete Source Datastore
Multi-Schema Datastore Creation
Use an Existing Connection
View Enrichment Datastore
Preview Enrichment Datastore Containers
Delete Enrichment Datastore
Link / Change Enrichment Destination
Edit Enrichment Settings
Operations
View Activity
Run & Manage Operations
Schedule Operations
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
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
Set Check Owner / Default Anomaly Assignee
Anomalies
View Anomalies
View Anomaly Source Records
Change Anomaly Status (Acknowledge / Archive)
Edit Anomaly Description
Assign Users to Anomaly
Timeline
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
Delete Another User's Comment
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
Datastore Groups
View Datastore Groups
Assign Datastore to Group
Flows
View Flows and Executions Related to the Datastore
Create / Edit / Execute / Delete Flows Related to the Datastore
AI Use Cases
View AI Use Case & Attestations
Create / Edit / Delete AI Use Case
Capture Baseline
Submit for Review / Reopen Draft
Generate Attestation
Certify / Revoke AI Use Case
Field Status
View Field Status
Mask / Unmask Field
Exclude Field
Restore Field
Delete Field
Merge Fields
View Masked Field Values

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

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.

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 and Manage Connections.

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.

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.