# Manager

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

The Manager role provides administrative access over global assets such as datastores and notifications, and can create connections. However, Managers **are subject to team permissions** when interacting with datastore content. Like Members, they list and open only the datastores on their teams, and their team permission on each one sets what they can do there. A datastore outside their teams does not appear in datastore lists, counts, the Teams list, or lineage.

## Who Should Have Manager Access?

Manager is designed for **data engineers**, **team leads**, and **data platform operators** who need to:

- Create datastores, including enrichment datastores
- Create connections, delete connections no datastore uses, and edit or reuse connections used by a datastore where they hold the **Editor** team permission
- Manage notification rules
- Manage library content (check templates)
- View the user and team lists (read-only)
- Add and sync integrations
- Create and manage datastore groups

> **Tip**
>
> Manager is the minimum role required to **create datastores**. Global tags are managed by Admins, and a team's tags by its Editors, whatever their role. If a user only needs to work within existing datastores, the [Member](https://userguide.qualytics.io/settings/access/users/roles/member/) role with appropriate team permissions is sufficient.

> **Warning: Creating a datastore also needs the Editor team permission**
>
> The Manager role alone is not enough to create a datastore. Every datastore belongs to at least one team, and the Manager must hold the **Editor** team permission on one of the teams the new datastore is assigned to. A Manager whose teams all sit below Editor (for example, a member of the Public team only, after an Admin lowered the Public team's permission) cannot create datastores until an Admin adds them to a team with Editor or raises a team they already belong to. The **Add Datastore** form states this when it applies, and the API refuses the request the same way. See [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).

> **Info: A name used by a datastore you cannot see**
>
> Datastore names are unique across the platform, including datastores outside your teams. When you create or rename a datastore with a name that one of those datastores already uses, the request is refused with `The name '<name>' is already in use by a datastore you do not have permission to view. Choose a different name.` Pick another name; the other datastore stays hidden.

## Includes

Manager includes all capabilities of **Member**.

## Capability Table

| Category | Action | Allowed |
| --- | --- | --- |
| **Datastores** | Create source datastores (with Editor team permission on at least one team) | Allowed |
|  | Create enrichment datastores (with Editor team permission on at least one team) | Allowed |
|  | List datastores (team-scoped) | Allowed |
|  | Delete datastores | Not allowed |
|  | Manage datastore teams (with Editor team permission) | Allowed |
| **Connections** | Create connections | Allowed |
|  | Use an existing connection to add a datastore, test it, or discover its schemas (with Editor team permission on a datastore that uses the connection, or none when no datastore uses it yet) | Allowed |
|  | Update connections (with Editor team permission on a datastore that uses the connection) | Allowed |
|  | Delete connections (not used by any datastore) | Allowed |
| **Tags** | View tags | Allowed |
|  | Create, update, delete the tags of teams where you hold Editor | Allowed |
|  | Create, update, delete global tags | Not allowed |
| **Notifications** | View notification rules | Allowed |
|  | Create, update, delete notification rules | Allowed |
| **Library** | View library | Allowed |
|  | Manage library content | Allowed |
|  | Export check templates to an enrichment datastore | Allowed |
| **Access** | View users | Allowed |
|  | View teams | Allowed |
|  | Manage users or teams | Not allowed |
| **Flows** | View flows whose datastores are all on your teams, and flows that name no datastore | Allowed |
|  | Create, edit, delete flows (with Editor team permission on every datastore the Flow relates to) | Allowed |
|  | Create, edit, delete, or execute a Flow that exports the Access Report | Not allowed |
| **Integrations** | Add integrations | Allowed |
|  | Sync integrations (all datastores, or one datastore with Editor team permission) | Allowed |
| **Datastore Groups** | Create, edit, delete groups | Allowed |
|  | Assign datastores to groups (with Editor team permission) | Allowed |
| **Filter and Sort** | Filter Explore by datastores in your teams | Allowed |
|  | Filter Explore by all workspace datastores | Not allowed |
|  | Filter Explore by global tags and your teams' tags | Allowed |
|  | Filter Explore by another team's tags | Not allowed |
| **Filter Presets** | Create a filter preset | Allowed |
|  | Apply a filter preset | Allowed |
|  | Edit or delete a filter preset you created | Allowed |
|  | Edit or delete a filter preset created by another user | Allowed |
| **Tokens** | Generate personal tokens | Allowed |
|  | Generate service tokens | Not allowed |
| **Settings UI** | Connections, Integrations, Access, Tokens, Status tabs | Allowed |
|  | Defaults tab | Not allowed |
|  | Audit tab | Not allowed |
| **Health** | View health status | Allowed |
|  | Capture Dataplane diagnostics | Not allowed |
|  | View platform activity log (Audit) | Not allowed |
|  | View AgentQ audit history | Not allowed |
| **Field Status** | Manage field status (with Editor team permission) | Allowed |

> **Note**
>
> Managers **cannot** manage users, teams, or service users. For those capabilities, [Admin](https://userguide.qualytics.io/settings/access/users/roles/admin/) access is required. Managers are also **subject to team permissions**. They see and open only the datastores on their teams.

*Last updated: November 9, 2026.*
