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) 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 | |
| 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) | |
| Assign Users to Anomaly | |
| Add Comment to Anomaly | |
| Tags | |
| View Tags | |
| Assign Tags to Datastores, Containers, and Fields | |
| Assign Tags to Draft and 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
Authors cannot run operations, manage enrichment, or modify datastore settings. For those capabilities, Editor permission is required.
Dry Run and Masked Fields
Authors can run a Dry Run, but the Show masked values toggle is only visible to the Editor role. When an Author runs a Dry Run on a check that targets masked fields, those values stay masked in the results.
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.