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 see enrichment datastores in the listing
- 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 | |
| View Enrichment Datastore | |
| Preview Enrichment Datastore | |
| Delete Enrichment Datastore | |
| Operations | |
| View Activity | |
| Run & Manage Operations | |
| Schedule Operations | |
| Create/Delete Computed Asset (as owner) | |
| Create/Delete Computed Asset (any owner) | |
| Reassign Computed Asset owner | |
| Profiles | |
| View Profiles | |
| Delete Profiles | |
| Quality Checks | |
| View Checks | |
| Create Draft Checks | |
| Save / Restore 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 | |
| Datastore Groups | |
| View Datastore Groups | |
| Assign Datastore to Group | |
| 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 see an enrichment datastore listed, but opening its detail page in the web app also 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.