# Flow Permissions

Source: https://userguide.qualytics.io/flows/flow/deep-dive/permissions/

A Flow follows the datastores it relates to. Any [user role](https://userguide.qualytics.io/settings/access/users/roles/overview/) can view Flows and their executions, as long as the user can see every datastore the Flow names (see [Who Sees a Flow](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#who-sees-a-flow)). Changing a Flow (creating, editing, publishing, activating or deactivating, executing, aborting or deleting its executions, or deleting it) needs the **Editor** team permission on every datastore the Flow relates to. This applies to Members and Managers alike. Admins can manage every Flow.

## Related Datastores

A Flow relates to a datastore when the datastore appears in its configuration:

| Source | Related Datastores |
| --- | --- |
| Trigger | The datastores picked in the trigger's **Datastores** filter. With **is not any of**, every other datastore. |
| Operation actions | The datastore each Sync, Profile, Scan, Export, or Materialize action runs on. |
| Anomaly actions | The datastores picked in the action's datastore filter. |
| Global Export actions | The enrichment datastore the export writes into. |

Notification, ticketing, and workflow actions don't add related datastores.

### Flows That Reach Every Datastore

Leaving a datastore filter empty doesn't mean the Flow relates to no datastore. It means the Flow acts on all of them:

- An **Operation Completed**, **Anomalous Table or File Detected**, **Anomaly Detected**, or **Anomaly Status Changed** trigger with no **Datastores** fires on events from every datastore. So does one whose **Datastores** filter uses **is not any of**, since it reaches every datastore it does not exclude, including datastores added later.
- An anomaly action with no datastore filter archives or deletes anomalies on every datastore.

Managing such a Flow needs the **Editor** team permission on every datastore in the deployment, enrichment datastores included. Wherever the Flow's related datastores are shown, they read **All**.

### Flows With No Related Datastore

A **Schedule** or **Manual** Flow whose actions only notify or call a workflow relates to no datastore, so it reads and changes no data. Any Member or Manager can manage it, whatever their teams.

## Who Sees a Flow

A Flow is shown only to users who can see every datastore it names. A Flow names:

- The datastores picked in its trigger's **Datastores** filter, including the ones an **is not any of** filter excludes.
- The datastore of each operation action.
- The datastores picked in its anomaly actions.
- The enrichment datastore its Global Export actions write into.

Any team permission on a datastore is enough to see it, **Reporter** included. If one of those datastores is only on teams the user is not on, the Flow is hidden from that user everywhere: the Flows list, the Flows filters, Global Search, tag pages, and the executions list. Opening its link shows an error and returns to the Flows list.

A Flow that names no datastore is shown to every user. This includes a Flow that reaches every datastore because its filters are empty. Admins see every Flow.

> **Note: Hidden Flows still run**
>
> Hiding a Flow changes only who can see it. The Flow still runs on its trigger, whoever causes the event.

## User Roles

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| View Flows and their configuration [1](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:view) | Allowed | Allowed | Allowed |
| View executions and their details [1](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:view) | Allowed | Allowed | Allowed |
| Create and publish a Flow [2](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:related) | Allowed | Allowed | Allowed |
| Edit and publish changes to a Flow [2](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:related) | Allowed | Allowed | Allowed |
| Activate or deactivate a Flow [2](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:related) | Allowed | Allowed | Allowed |
| Execute a Flow [2](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:related) | Allowed | Allowed | Allowed |
| Abort or delete an execution [2](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:related) | Allowed | Allowed | Allowed |
| Delete a Flow [2](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#fn:related) | Allowed | Allowed | Allowed |
| Create, edit, delete, or execute a Flow with a **Global Export** of check templates | Not allowed | Allowed | Allowed |
| Create, edit, delete, or execute a Flow with a **Global Export** of the Access Report | Not allowed | Not allowed | Allowed |

> **Note: Global Export actions are gated by role**
>
> A [Global Export](https://userguide.qualytics.io/flows/actions/deep-dive/operation/#global-export) action writes organization-wide data, so its rule depends on what it exports, on top of the team permission on its enrichment datastore. Exporting **Check Templates** needs the **Manager** or **Admin** role. Exporting **Access Report** needs the **Admin** role, and a Flow that contains one can only be created, edited, activated or deactivated, deleted, or manually executed by an Admin. The check happens when a person acts on the Flow, so once an Admin publishes it, the Flow still runs on its trigger (for example, its schedule) without anyone present.

> **Info: Changing the related datastores changes who can edit**
>
> Publishing a change to a Flow's datastores also changes who can manage it from then on. A Flow that starts reaching every datastore can only be edited by Admins and by users with the **Editor** team permission on every datastore.

## UI Behavior

| Scenario | What the User Sees |
| --- | --- |
| A Member or Manager opens the Flows page | The **Add Flow** button is shown. The list, its filters, and the executions list leave out every Flow that names a datastore on a team the user is not on. |
| A Member or Manager opens the link to a Flow they cannot see | An error says the Flow could not be retrieved, and the Flows list opens instead. |
| A Member or Manager picks a datastore in the Flow editor | Every datastore input, in the trigger and in the actions, lists only the datastores the user holds the **Editor** team permission on. Admins see every datastore. |
| A Member or Manager configures an event trigger or an anomaly action | The datastore filter is required, and the trigger's **Save** stays disabled until a datastore is picked, so the Flow can't be saved reaching every datastore. Admins, and users with the **Editor** team permission on every datastore, can leave it empty. |
| A user opens a Flow they can manage | The side panel shows **You can edit**, and the canvas offers its editing controls. |
| A user opens a Flow they cannot manage | The side panel shows **Read only**, the row's options menu is hidden on the Flows list, and the canvas offers no editing controls. This includes a Manager opening a Flow that contains a Global Export of the Access Report. |
| A user opens **Related datastores** in the Flow editor | Each related datastore shows a pencil when the user edits it or an eye when it is read only for them, and the footer states what managing the Flow requires. |
| A user cannot manage an execution | The row's **Abort** and **Delete** buttons are hidden, and bulk selection explains that the user doesn't have permission to manage the execution. |

## See Also

- **How It Works**

  The canvas, Flow settings, chaining rules, and the publish lifecycle behind every edit.

  [How It Works](https://userguide.qualytics.io/flows/flow/deep-dive/how-it-works/)
- **Triggers**

  The six trigger types, schedule configuration, and the filter conditions each type supports.

  [Triggers](https://userguide.qualytics.io/flows/flow/deep-dive/triggers/)
- **Actions**

  The five action categories, the chaining rules between them, and where each is documented.

  [Actions](https://userguide.qualytics.io/flows/flow/deep-dive/actions/)
- **Executions**

  The Definitions and Executions tabs, execution states, and the read-only execution graph.

  [Executions](https://userguide.qualytics.io/flows/flow/deep-dive/executions/)
- **Examples**

  Real scenarios showing how a trigger and a chain of actions combine into a working automation.

  [Examples](https://userguide.qualytics.io/flows/flow/deep-dive/examples/)
- **Best Practices**

  Guidelines for building Flows that stay quiet when healthy and loud when something breaks.

  [Best Practices](https://userguide.qualytics.io/flows/flow/deep-dive/best-practices/)

---

1. Members and Managers see a Flow only when they can see every datastore it names. See [Who Sees a Flow](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#who-sees-a-flow).
2. Members and Managers need the **Editor** team permission on every datastore the Flow relates to, or on every datastore when the Flow reaches all of them. A Flow with no related datastore needs no team permission. Admins are not subject to team permissions.

*Last updated: November 5, 2026.*
