# Entity Resolution Check Permissions

Source: https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/permissions/

This page covers the team permissions required to view, create, edit, archive, and delete an Entity Resolution check on a source datastore. For the full reference of user roles, see [User Roles](https://userguide.qualytics.io/settings/access/users/permissions/). For the canonical matrix of every team-permission-gated action, see [Team Permissions Overview](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).

## Permission Matrix

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

| Action | Reporter | Viewer | Drafter | Author | Editor |
| --- | --- | --- | --- | --- | --- |
| View an Entity Resolution 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 |

## Key Details

- **Viewing** is available to all team permissions, including Reporter and Viewer.
- **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.
- The same rules apply through the API. The [API](https://userguide.qualytics.io/data-quality-checks/entity-resolution/api/) page lists the permission each endpoint requires.
- **Admins** bypass team permissions and can manage 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 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.

## See Also

- **How It Works**

  The complete reference: definition, field scope, field roles, comparison types, weights, threshold, and clustering.

  [How It Works](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/how-it-works/)
- **Anomaly Reporting**

  The anomaly message the check produces, what each number means, and how non-compliant clusters appear in Source Records.

  [Anomaly Reporting](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/anomaly-reporting/)
- **Examples**

  Production scenarios with sample records, cluster outcomes, and the resulting anomaly messages.

  [Examples](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/examples/)
- **Best Practices**

  Guidelines for blocking, weighting, tuning the threshold, and normalizing values before resolution.

  [Best Practices](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/best-practices/)

*Last updated: September 16, 2026.*
