# User Roles

Source: https://userguide.qualytics.io/settings/access/users/roles/overview/

In Qualytics, every user is assigned a role that determines their platform-level permissions. Roles control what features and actions a user can perform globally, independent of team membership.

There are three user roles: **Admin**, **Manager**, and **Member**. Admins have the ability to edit any user's role from the user listing.

> **Info**
>
> User roles control **platform-level** permissions. For **datastore-level** access, see the [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/) documentation.

## Role Hierarchy

Roles follow a hierarchical model: higher roles include all capabilities of lower roles:

| Level | Role | Includes |
| --- | --- | --- |
| 3 | [**Admin**](https://userguide.qualytics.io/settings/access/users/roles/admin/) | Admin + Manager + Member |
| 2 | [**Manager**](https://userguide.qualytics.io/settings/access/users/roles/manager/) | Manager + Member |
| 1 | [**Member**](https://userguide.qualytics.io/settings/access/users/roles/member/) | Member only |

## Permission Matrix

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| **Users & Teams** |  |  |  |
| Manage users (create, edit, deactivate) | Not allowed | Not allowed | Allowed |
| Manage teams (create, edit, delete) | Not allowed | Not allowed | Allowed |
| View users and teams | Not allowed | Allowed | Allowed |
| Create service users | Not allowed | Not allowed | Allowed |
| Export the Access Report from a Flow | Not allowed | Not allowed | Allowed |
| **Datastores** |  |  |  |
| Create source datastores [7](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:datastore-create-team-perm) | Not allowed | Allowed | Allowed |
| Delete source datastores | Not allowed | Not allowed | Allowed |
| List datastores (team-scoped) | Allowed | Allowed | Allowed |
| Create enrichment datastores [7](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:datastore-create-team-perm) | Not allowed | Allowed | Allowed |
| Delete enrichment datastores | Not allowed | Not allowed | Allowed |
| **Connections** |  |  |  |
| Read connections | Allowed | Allowed | Allowed |
| Create connections | Not allowed | Allowed | Allowed |
| Use an existing connection (add a datastore to it, test it, discover its schemas) [4](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:connection-use-team-perm) | Not allowed | Allowed | Allowed |
| Update connections [3](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:connection-update-team-perm) | Not allowed | Allowed | Allowed |
| Delete connections [6](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:connection-delete-in-use) | Not allowed | Allowed | Allowed |
| **Tags & Notifications** |  |  |  |
| View tags | Allowed | Allowed | Allowed |
| Manage the tags of teams where you hold Editor (create, update, delete) | Allowed | Allowed | Allowed |
| Manage global tags and any team's tags, change a tag's scope | Not allowed | Not allowed | Allowed |
| View notification rules | Allowed | Allowed | Allowed |
| Manage notification rules | Not allowed | Allowed | Allowed |
| **Library** |  |  |  |
| View library | Allowed | Allowed | Allowed |
| Manage library | Not allowed | Allowed | Allowed |
| Export check templates to an enrichment datastore | Not allowed | Allowed | Allowed |
| **Tokens** |  |  |  |
| Generate personal tokens | Allowed | Allowed | Allowed |
| Generate service tokens | Not allowed | Not allowed | Allowed |
| Generate SCIM administration tokens | Not allowed | Not allowed | Allowed |
| **Flows** |  |  |  |
| View flows and their executions [5](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:flow-view-team) | Allowed | Allowed | Allowed |
| Create / Edit / Execute / Delete flows [2](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:flow-editor-team-perm) | Allowed | Allowed | Allowed |
| **Integrations** |  |  |  |
| Add integrations | Not allowed | Allowed | Allowed |
| Sync an integration across all its datastores | Not allowed | Allowed | Allowed |
| Sync an integration for one datastore (with Editor team permission) | Allowed | Allowed | Allowed |
| **Anomalies** |  |  |  |
| Link / Unlink external tickets on anomalies [1](https://userguide.qualytics.io/settings/access/users/roles/overview/#fn:ticket-team-perm) | Not allowed | Allowed | Allowed |
| **Datastore Groups** |  |  |  |
| Create / Edit / Delete groups | Not allowed | Allowed | Allowed |
| **Filter and Sort** |  |  |  |
| Filter Explore by datastores in your teams | Allowed | Allowed | Allowed |
| Filter Explore by all workspace datastores | Not allowed | Not allowed | Allowed |
| Filter Explore by global tags and your teams' tags | Allowed | Allowed | Allowed |
| Filter Explore by any workspace tag | Not allowed | Not allowed | Allowed |
| **Filter Presets** |  |  |  |
| Create a filter preset | Allowed | Allowed | Allowed |
| Apply a filter preset | Allowed | Allowed | Allowed |
| Edit or delete a filter preset you created | Allowed | Allowed | Allowed |
| Edit or delete a filter preset created by another user | Not allowed | Allowed | Allowed |
| **Field Status** |  |  |  |
| Manage field status (with Editor team permission) | Allowed | Allowed | Allowed |
| View masking audit log | Not allowed | Not allowed | Allowed |
| **Settings UI** |  |  |  |
| Connections tab | Allowed | Allowed | Allowed |
| Tokens tab | Allowed | Allowed | Allowed |
| Access tab | Not allowed | Allowed | Allowed |
| Integrations tab | Not allowed | Allowed | Allowed |
| Defaults tab | Not allowed | Not allowed | Allowed |
| Audit tab | Not allowed | Not allowed | Allowed |
| Status tab | Not allowed | Allowed | Allowed |
| **Platform** |  |  |  |
| View health status | Not allowed | Allowed | Allowed |
| View platform activity log (Audit) | Not allowed | Not allowed | Allowed |
| View AgentQ audit history | Not allowed | Not allowed | Allowed |
| Restart Dataplane | Not allowed | Not allowed | Allowed |
| Capture Dataplane diagnostics | Not allowed | Not allowed | Allowed |
| Manage global settings | Not allowed | Not allowed | Allowed |
| Subject to team permissions | Allowed | Allowed | Not allowed |

## Individual Roles

For detailed descriptions of each role, see the individual pages:

- **Admin**

  Full platform access. Manage users, teams, datastores, connections, and all settings.

  [Admin](https://userguide.qualytics.io/settings/access/users/roles/admin/)
- **Manager**

  Global asset management. Create datastores and connections, manage notifications.

  [Manager](https://userguide.qualytics.io/settings/access/users/roles/manager/)
- **Member**

  Standard access. Inherits permissions from team membership, manages own tokens.

  [Member](https://userguide.qualytics.io/settings/access/users/roles/member/)

---

1. In addition to the **Manager** user role, linking or unlinking an external ticket also requires the **Author** team permission (or higher) on the anomaly's datastore. Admins bypass the team-permission check; Managers do not.
2. Creating, editing, publishing, activating, executing, aborting, or deleting a Flow requires the **Editor** team permission on every datastore the Flow relates to, for Members and Managers alike. A Flow that relates to no datastore needs no team permission, and one that reaches every datastore needs the **Editor** team permission on all of them. Admins bypass the team-permission check. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/).
3. In addition to the **Manager** user role, editing a connection requires the **Editor** team permission on at least one datastore that uses it, so a Manager cannot edit a connection that no datastore uses yet. Admins bypass the team-permission check; Managers do not.
4. In addition to the **Manager** user role, using a connection that a datastore already uses requires the **Editor** team permission on at least one of those datastores. A connection that no datastore uses yet needs only the role. Admins bypass the team-permission check.
5. A Flow is shown only to users who can see every datastore it names, with any team permission. A Flow that names a datastore on a team the user is not on is hidden from the Flows list, search, and executions. A Flow that names no datastore is shown to everyone. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/#who-sees-a-flow).
6. A connection that one or more datastores still use cannot be deleted, whatever the role. Delete those datastores first.
7. In addition to the **Manager** user role, creating a datastore requires the **Editor** team permission on at least one of the teams the new datastore is assigned to (the Public team when none is chosen). A Manager whose teams all sit below Editor cannot create datastores. Admins bypass the team-permission check; Managers do not.

*Last updated: November 5, 2026.*
