# Entity Resolution Recipe Permissions

Source: https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/permissions/

The Entity Resolution recipe has no permissions of its own. Each step performs an ordinary platform action, and that action's permissions apply. The check is created, dry-run, and activated like any check, the scan and the materialize are ordinary operations, and the anomaly is acknowledged like any anomaly. This page gathers those requirements in one place. For the canonical matrices, see [User Roles](https://userguide.qualytics.io/settings/access/users/roles/overview/) and [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).

> **Note: Two Permission Systems**
>
> **User Roles** (Member, Manager, Admin) control what a user can do across the platform. **Team Permissions** (Reporter, Viewer, Drafter, Author, Editor) control what a user can do on the specific datastores they reach through team membership. They are independent systems with different scopes.

## User Roles (Platform-Level)

Every role can use the recipe. No step is reserved for Managers or Admins.

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| Open Recipes and browse a recipe's steps | Allowed | Allowed | Allowed |
| Receive AI suggestions and analyses | Allowed | Allowed | Allowed |
| Create, validate, and activate the check | Allowed | Allowed | Allowed |
| Run the scan | Allowed | Allowed | Allowed |
| Write the golden set | Allowed | Allowed | Allowed |
| Acknowledge the anomaly | Allowed | Allowed | Allowed |

Each of these still requires the matching team permission on the source datastore, listed below.

## Team Permissions (Datastore-Level)

The team permission is checked on the **source datastore** the selected table belongs to. The golden set is written to that datastore's enrichment destination as part of the materialize operation, so no separate permission on the destination is needed.

| Action | Reporter | Viewer | Drafter | Author | Editor |
| --- | --- | --- | --- | --- | --- |
| Browse the recipe's steps and field metrics | Allowed | Allowed | Allowed | Allowed | Allowed |
| Load the scan's source records for remediation (Scan, Remediate) | Not allowed | Allowed | Allowed | Allowed | Allowed |
| Receive AI suggestions and analyses | Allowed | Allowed | Allowed | Allowed | Allowed |
| Create the Draft check (Review) | Not allowed | Not allowed | Allowed | Allowed | Allowed |
| Validate the check (dry run, then activate) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Run the scan (Scan) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Write the golden set (Materialize) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |
| Acknowledge the anomaly (Materialize) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Create a computed asset from Select Asset (as owner) | Not allowed | Not allowed | Not allowed | Allowed | Allowed |
| Create a computed asset from Select Asset (any owner) | Not allowed | Not allowed | Not allowed | Not allowed | Allowed |

> **Note: Completing the recipe end to end**
>
> The scan and the materialize are operations, and running operations needs the **Editor** team permission. A user with **Editor** on the source datastore can complete the whole recipe alone. A **Drafter** can build the check up to Review, which saves it as a Draft. **Validate** runs the dry run and then activates the check in one step, so it needs the **Author** team permission. A Drafter can still dry-run the Draft check from the check's own menu, outside the recipe. Both need an Editor to run the scan and write the golden set.

## How Both Layers Work Together

To take a table all the way to a golden set, a user must satisfy both layers:

1. **User Role**: at least **Member**
2. **Team Permission**: **Editor** on the source datastore

> **Info: Admin Bypass**
>
> Users with the **Admin** role bypass team permission checks and can complete the recipe on any datastore.

The AI suggestions follow the same rule as viewing: any team permission on the datastore, starting at **Reporter**, plus the Member role. Whether a given AI step is available at all depends on the AgentQ data sharing level, not on the user's permissions. See [AgentQ Access Controls](https://userguide.qualytics.io/agentq/deep-dive/access-controls/).

## UI Behavior Without Permission

| Scenario | What the User Sees |
| --- | --- |
| User cannot dry-run checks on the datastore (below Drafter) | **Open in Recipe** and **Remediate in Recipe** are not shown on the check and anomaly details. The recipe itself still opens from the Recipes page, but on Review it can neither check for a conflicting check nor create the Draft check, and shows a permission error. |
| User is below Viewer on the datastore | The Scan step cannot load the source records, so remediation cannot start. |
| User cannot run operations on the datastore (below Editor) | **Scan in Recipe** is not shown on the check details; an active check shows **Open in Recipe** instead. Inside the recipe, **Scan** and **Materialize** fail with a permission error, and you can try again once the permission is granted. |
| User cannot create computed assets on the datastore | The **Computed Table** (or **Computed File**) and **Computed Join** cards are not shown on Select Asset; only **Existing Table** is offered. |
| AgentQ data sharing level below what a step needs | The step reports that its AI suggestions or recommendations could not load and lets you continue manually. The other AI steps keep working. |
| No AI provider configured | No AI banners appear anywhere in the recipe, and the **Get AI suggestions** offer on Remediate is absent. Every step works manually. |

## Important Notes

- **The check is an ordinary check.** Once the recipe has created it, editing, cloning, archiving, or deleting it from the datastore page follows the usual [quality check permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).
- **Entering from a check or an anomaly checks the same permissions** as building the recipe from scratch. The entry-point buttons are hidden when you lack them; see [Entry Points and Resuming](https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/entry-points/).
- **Masked fields stay masked.** The recipe never asks to reveal masked values. They appear masked in the dry-run preview and in the remediation view, and are written masked to both outputs, whatever your team permission.

## See Also

- **How It Works**

  The phases, the two prerequisites, what the run reads and writes, and AgentQ's role.

  [How It Works](https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/how-it-works/)
- **Build and Validate**

  Select Asset, Distinction Field, Compare Fields, Match Threshold, Review, and Validate, step by step.

  [Build and Validate](https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/build-and-validate/)
- **Scan and Remediate**

  The full scan, choosing golden records, writing the golden set, and the completion summary.

  [Scan and Remediate](https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/scan-and-remediate/)
- **Entry Points and Resuming**

  Open in Recipe, Scan in Recipe, Remediate in Recipe, and how progress is kept between visits.

  [Entry Points and Resuming](https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/entry-points/)
- **Examples**

  Real scenarios showing the recipe taking a table from suspected duplicates to a golden set.

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

  Guidelines for preparing the asset, choosing fields, tuning the threshold, and remediating.

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

*Last updated: October 5, 2026.*
