Skip to content

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 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
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 and 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 (unrestricted)
Reveal an owned masked Computed Field in Data Preview

Note

Authors cannot run operations, manage enrichment, or modify datastore settings. For those capabilities, the Editor team permission is required.

Masked values and Authors

An Author can reveal masked fields in exactly one place: Data Preview, and only for the masked Computed Fields they own. Every other masked field in that same preview stays masked, and the reveal is written to the 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: 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.

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.

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.

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.