Skip to content

Drafter

The Drafter permission is designed for users who need to create and prepare quality checks without the ability to activate them. Drafters write and save checks as drafts, which can then be reviewed and activated by users with Author or Editor permissions.

Who Should Have Drafter Access?

Drafter is designed for junior data quality analysts and contributors who need to:

  • Create new quality checks as drafts on assigned datastores
  • Save checks as drafts for review before activation
  • Run a Dry Run on a check to test its logic before activation
  • Set the Owner and Default Anomaly Assignee when authoring a draft check
  • Assign tags to draft quality checks
  • Preview datastore content and view profiles

Tip

Drafter is ideal for teams that follow a review workflow; drafters create checks, and authors or editors review and activate them.

Includes

Drafter includes all capabilities of Viewer and Reporter.

Capability Table

Action Drafter
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

¹ Drafters can only set these fields while creating a draft check. See the Drafters and check fields note below for the full rule.

Drafters and check fields

Drafters can set Owner and Default Anomaly Assignee only while creating a draft check. Once the check is activated, modifying these fields requires Author or Editor permission.

Drafters and check tags

Drafters can assign tags while a quality check is in Draft status. Assigning tags to an active quality check requires Author or Editor permission.

Note

Drafters cannot activate checks via the Validate action. Created checks remain in Draft status until an Author or Editor activates them.

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.

Dry Run and Masked Fields

Drafters can run a Dry Run, but the Show masked values toggle is only visible to users with the Editor team permission. When a Drafter runs a Dry Run on a check that targets masked fields, those values stay masked in the results.

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.