# Check Permissions Source: https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/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](https://userguide.qualytics.io/settings/access/users/permissions/), and for every team-permission-gated action, see [Team Permissions Overview](https://userguide.qualytics.io/settings/access/teams/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 | Allowed | Allowed | Allowed | Allowed | Allowed | | Create a check as Draft | Not allowed | Not allowed | Allowed | Allowed | Allowed | | Create a check as Active | Not allowed | Not allowed | Not allowed | Allowed | Allowed | | Edit a check while it stays Draft | Not allowed | Not allowed | Allowed | Allowed | Allowed | | Edit an Active check, or activate a Draft | Not allowed | Not allowed | Not allowed | Allowed | Allowed | | Archive a check | Not allowed | Not allowed | Not allowed | Allowed | Allowed | | Restore an archived check as Draft | Not allowed | Not allowed | Allowed | Allowed | Allowed | | Restore an archived check as Active | Not allowed | Not allowed | Not allowed | Allowed | Allowed | | Delete an archived check permanently | Not allowed | Not allowed | Not allowed | Allowed | Allowed | - **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](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/) 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 | Allowed | Allowed | Allowed | Allowed | Allowed | | Change status (Active/Draft) of an AI Managed check | Not allowed | Not allowed | Not allowed | Allowed | Allowed | | Edit description, tags, additional metadata, anomaly message field [1](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/permissions/#fn:drafter-while-draft) | Not allowed | Not allowed | Allowed | Allowed | Allowed | | Edit owner, anomaly assignee [1](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/permissions/#fn:drafter-while-draft) | Not allowed | Not allowed | Allowed | Allowed | Allowed | | Edit rule properties, coverage, filter, fields *(triggers conversion to Authored)* [1](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/permissions/#fn:drafter-while-draft) | Not allowed | Not allowed | Allowed | Allowed | Allowed | | Validate / Activate the converted check | Not allowed | Not allowed | Not allowed | Allowed | Allowed | | Run a Profile operation that creates new AI Managed checks | Not allowed | Not allowed | Not allowed | Not allowed | Allowed | | Delete an AI Managed check | Not allowed | Not allowed | Not allowed | Allowed | Allowed | ### 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. > **Info: 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](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/) 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. | > **Info: Full Permissions Reference** > > For the complete permissions and roles matrix across all Qualytics features, see the [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/) page. ## See Also - **How a Check Works** What a check is made of, who creates it, how AI Managed checks are generated, how a Scan evaluates it, and how its status changes. [How a Check Works](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/how-it-works/) - **Authored Checks** What an Authored check is, who governs it, and how it differs from an AI Managed check. [Authored Checks](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/authored-checks/) - **AI Managed Checks** What an AI Managed check is, which edits convert it to Authored, and how to go back. [AI Managed Checks](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/ai-managed-checks/) - **Check Ownership** Who is responsible for a check, the four ways ownership changes, notifications, and filtering by owner. [Check Ownership](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/ownership/) - **Check Importance** How much a check's failures matter, and how its tags raise or lower it. [Check Importance](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/importance/) - **Impact Metrics** Numbers measured over a check's failed records that show how big a failure is. [Impact Metrics](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/impact-metrics/) - **Dry Run** What a Dry Run evaluates and how to read its results, anomalies, and source records. [Dry Run](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/dry-run/) - **Check Views** The check lists, the check page, and the side panel: how to reach each one, what it shows, and what you can do there. [Check Views](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/check-details/check-views/) - **Check Anomalies** The anomalies a check has produced, and how to triage them from the check's page. [Check Anomalies](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/check-details/anomalies/) - **Check Timeline** The change log of a check, its past versions, and the comments your team leaves on it. [Check Timeline](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/check-details/timeline/) - **Check Examples** Scenarios that show ownership and AI Managed checks in practice. [Check Examples](https://userguide.qualytics.io/data-quality-checks/checks/deep-dive/examples/) --- 1. A Drafter can make this edit only while the check is in Draft status. On an Active check it requires Author. *Last updated: November 10, 2026.*