# Author

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

The Author permission is focused on quality check lifecycle management. Authors can create, activate, validate, and manage the status of quality checks and their associated anomalies. This is the permission level for users who own the data quality rules on assigned datastores.

## Who Should Have Author Access?

Author is designed for **data quality analysts** and **data stewards** who need to:

- Create, edit, and delete quality checks (both draft and active)
- Activate and validate checks to make them operational
- Change the status of checks (e.g., from draft to active)
- Edit check metadata (descriptions, tags, and configurations)
- Set the **Owner** and **Default Anomaly Assignee** on checks
- Run a [Dry Run](https://userguide.qualytics.io/data-quality-checks/checks/how-tos/dry-run/) to validate check logic
- Create, edit, and delete Computed Assets (Computed Tables, Computed Files, Computed Joins) they personally own. Managing computed assets owned by other users requires Editor. For a cross-datastore Computed Join, the Author also needs at least **Viewer** permission on the right-side datastore to use its containers as join inputs.
- Triage anomalies by changing their status (acknowledge, archive), editing their description, and assigning users to them
- Assign tags to quality checks and anomalies
- Create, edit, and delete Computed Tables, Computed Files, and Computed Joins they own (see the Hybrid Gate note below)

> **Tip**
>
> Author is the minimum permission level required to **activate** quality checks. Drafters can create checks, but only Authors (and above) can make them operational.

## Includes

Author includes all capabilities of **Drafter**, **Viewer**, and **Reporter**.

## Capability Table

| Action | Author |
| --- | --- |
| **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) | 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 | Allowed |
| Save New Check as Draft / Restore Archived Check to Draft | Allowed |
| Create / Edit Active Checks | Allowed |
| Activate / Validate Check | Allowed |
| Edit Check Metadata | Allowed |
| Archive / Delete Checks | Allowed |
| Dry Run Check | Allowed |
| Set Check Owner / Default Anomaly Assignee | Allowed |
| **Anomalies** |  |
| View Anomalies | Allowed |
| View Anomaly Source Records | Allowed |
| Change Anomaly Status (Acknowledge / Archive) | Allowed |
| Edit Anomaly Description | Allowed |
| Assign Users to Anomaly | 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 and Active Quality Checks | Allowed |
| Assign Tags to Anomalies | 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 | Allowed |
| Capture Baseline | Allowed |
| Submit for Review / Reopen Draft | Allowed |
| Generate Attestation | 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 (unrestricted) | Not allowed |
| Reveal an owned masked Computed Field in Data Preview | Allowed |

> **Note**
>
> Authors **cannot** run operations, manage enrichment, or modify datastore settings. For those capabilities, the [Editor](https://userguide.qualytics.io/settings/access/teams/team-permissions/editor/) team permission is required.

> **Info: Masked values and Authors**
>
> An Author can reveal [masked fields](https://userguide.qualytics.io/fields/field-status/concepts/field-masking/) in exactly one place: **Data Preview**, and only for the masked [Computed Fields](https://userguide.qualytics.io/fields/computed-fields/getting-started/) they own. Every other masked field in that same preview stays masked, and the reveal is written to the [masking audit log](https://userguide.qualytics.io/fields/field-status/concepts/field-masking/#masking-audit-log) just as it would be for an Editor. An Author who owns no masked computed field in the container cannot reveal anything there.
>
> Everywhere else, revealing masked values requires [Editor](https://userguide.qualytics.io/settings/access/teams/team-permissions/editor/): Anomaly Source Records, Quality Check Dry Runs, Field Profile histograms, and Export/Materialize outputs. Authors can still run a Dry Run, but the **Show masked values** toggle is not available to them, so masked values stay masked in the results.

> **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: Hybrid Gate for Computed Assets**
>
> **Computed Assets** (Computed Tables, Computed Files, and Computed Joins) honor a **Hybrid Gate** that extends the Author permission. An Author can Create, Edit, and Delete a computed asset when they are (or will be) its owner, even though the capability table above shows the action as Not allowed at the datastore level. Reassigning ownership always requires the **Editor** team permission.

> **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 10, 2026.*
