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 | |
| 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 Assets | |
| 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 |
Warning
Even with Editor permission, users cannot delete source or 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.
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.