Editor¶
The Editor permission is the highest level of team access in Qualytics. It grants full management capabilities over datastores and all their associated data assets. Editors are responsible for configuring datastores, running operations, managing enrichment, and controlling field-level settings.
Who Should Have Editor Access?¶
Editor is designed for data engineers and platform operators who need to:
- Configure and manage datastore settings and connections
- Run profiling, scanning, and quality check operations
- Manage enrichment datastores and scoring configurations
- Create and manage computed fields and computed assets (Computed Tables, Computed Files, Computed Joins), including assets owned by other users
- Reassign ownership of computed assets to another user (Editor is the only team permission that can do this)
- Control field status (masking, exclusion, deletion, merging)
- View masked field values, including the Show masked values toggle in Dry Run
- Schedule recurring operations
Tip
Editor is the only permission level that can run operations and manage datastore settings. If a user needs to trigger scans or modify datastore configuration, they need Editor access.
Includes¶
Editor includes all capabilities of Author, Drafter, Viewer, and Reporter.
Capability Table¶
| Action | Editor |
|---|---|
| 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 they started (deleting someone else's needs the Admin user role) | |
| 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 |
Warning
Even with Editor permission, users cannot delete datastores, including enrichment datastores. Only Admins can perform datastore deletion.
Computed Asset Ownership
Editor is the only team permission that can manage any computed asset (Computed Table, Computed File, Computed Join) on the datastore regardless of who owns it, and the only level that can reassign ownership to another user. Authors can only manage computed assets they personally own and cannot transfer ownership. For the full breakdown, see Computed Join Permissions.
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 with Unmasked Values
Editor is the only team permission that can toggle Show masked values when running a Dry Run. Drafters and Authors can run a Dry Run on the same check, but masked fields stay masked in their 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.