Skip to content

Check Permissions

This page covers the team permissions for working with checks on a datastore. Each rule type's Permissions page repeats the matrix for that rule. For the full reference of user roles, see User Roles, and for every team-permission-gated action, see Team Permissions Overview.

Checks

The table below shows which team permissions can perform each action on a check, on a datastore the user has access to:

Action Reporter Viewer Drafter Author Editor
View a check
Create a check as Draft
Create a check as Active
Edit a check while it stays Draft
Edit an Active check, or activate a Draft
Archive a check
Restore an archived check as Draft
Restore an archived check as Active
Delete an archived check permanently
  • Draft work is available from the Drafter permission upward: creating a check as Draft, editing it while it stays Draft, and restoring an archived check as Draft.
  • Anything that puts a check into evaluation requires at least the Author permission: creating or activating an Active check, editing an Active check, archiving, restoring as Active, and deleting permanently.
  • Admins bypass team permissions. Managers do not: like Members, they need the required permission in at least one team assigned to the datastore.

Ownership

Action Required permission on the check's datastore
See the Owner field Reporter
Be selectable as an owner Drafter
Be selectable as default anomaly assignee Viewer
Change the owner (explicit transfer) Author, or Drafter on a Draft check
Activate a Draft check (may trigger transfer) Author

The owner dropdown is populated with the users with at least the Drafter permission on the datastore. Users without that permission are filtered out and cannot be assigned ownership, even by an Author. See Team Permissions for the full permission matrix.

AI Managed

AI Managed Permission Matrix

The table below shows which team permissions can perform AI Managed-check actions on a datastore the user has access to:

Action Reporter Viewer Drafter Author Editor
View AI Managed checks
Change status (Active/Draft) of an AI Managed check
Edit description, tags, additional metadata, anomaly message field 1
Edit owner, anomaly assignee 1
Edit rule properties, coverage, filter, fields (triggers conversion to Authored) 1
Validate / Activate the converted check
Run a Profile operation that creates new AI Managed checks
Delete an AI Managed check

Key Details

  • Viewing AI Managed checks is available to all team permissions, including Reporter and Viewer.
  • Editing organizational fields (description, tags, additional metadata, anomaly message field, owner, anomaly assignee) does not convert the check to Authored. A Drafter can make these edits only while the check is in Draft status. On an Active check they require Author. Switching the check status between Active and Draft requires Author and does not convert the check either. Invalid and Discarded are archive statuses: a user who can archive the check picks one of them in the Archive dialog. Choosing Invalid also keeps future AI generation from recreating the check.
  • Editing rule properties, coverage, filter, or fields requires at least Author permission, or Drafter while the check is in Draft status. Saving any of those edits automatically converts the check to Authored, takes ownership away from Qualytics if applicable, and removes the check from automatic Profile management.
  • Running a Profile operation, which is what generates AI Managed checks in the first place, requires the Editor permission.
  • Admins bypass team permissions and can manage AI Managed checks on every datastore in the workspace. Managers do not bypass team permissions. Like Members, they need the required permission in at least one team assigned to the datastore.

Team Context

Permissions for editing or deleting AI Managed checks are evaluated against the datastore's team assignments. A user must have the required team permission in at least one team that the datastore belongs to. For more details on how teams work, see the Team Permissions page.

UI Behavior by Team Permission

Scenario What the user sees
Reporter or Viewer team permission The AI Managed check is visible in read-only mode. The Edit, Validate, and Update controls are not available.
Drafter team permission The user can edit the check, including rule properties, coverage, filter, and fields, only while it is in Draft status. Editing an Active check, or moving it between Active and Draft, requires Author.
Author or Editor team permission All edit controls are available. Editing a property that affects evaluation flips the check from AI Managed to Authored on save.
User has no team access to the datastore The datastore is not listed, so the user cannot see its checks at all.

Full Permissions Reference

For the complete permissions and roles matrix across all Qualytics features, see the Team Permissions page.

See Also


  1. A Drafter can make this edit only while the check is in Draft status. On an Active check it requires Author. ↩↩↩