Manager
The Manager role provides administrative access over global assets such as datastores, tags, and notifications, and can create connections. However, Managers are subject to team permissions when interacting with datastore content. They can list all datastores but cannot view their content without explicit team permission.
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 (updating and deleting them requires Admin)
- Manage tags (create, update, delete) and 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 and manage tags. If a user only needs to work within existing datastores, the Member role with appropriate team permissions is sufficient.
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.
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) | |
| Create enrichment datastores (with Editor team permission on at least one team) | ||
| List datastores (all visible, content team-scoped) | ||
| Delete datastores | ||
| Manage datastore teams (with Editor team permission) | ||
| Connections | Create connections | |
| Update connections | ||
| Delete connections | ||
| Tags | View tags | |
| Create, update, delete tags | ||
| Notifications | View notification rules | |
| Create, update, delete notification rules | ||
| Library | View library | |
| Manage library content | ||
| Access | View users | |
| View teams | ||
| Manage users or teams | ||
| Flows | Create, edit, delete flows (with Editor team permission on every datastore the Flow references) | |
| Integrations | Add integrations | |
| Sync integrations (all datastores, or one datastore with Editor team permission) | ||
| Datastore Groups | Create, edit, delete groups | |
| Assign datastores to groups (with Editor team permission) | ||
| Filter and Sort | Filter Explore by datastores in your teams | |
| Filter Explore by all workspace datastores | ||
| Filter Explore by any workspace tag | ||
| Filter Presets | Create a filter preset | |
| Apply a filter preset | ||
| Edit or delete a filter preset you created | ||
| Edit or delete a filter preset created by another user | ||
| Tokens | Generate personal tokens | |
| Generate service tokens | ||
| Settings UI | Connections, Integrations, Access, Tokens, Status tabs | |
| Defaults tab | ||
| Audit tab | ||
| Health | View health status | |
| Capture Dataplane diagnostics | ||
| View platform activity log (Audit) | ||
| View AgentQ audit history | ||
| Field Status | Manage field status (with Editor team permission) |
Note
Managers cannot manage users, teams, or service users. For those capabilities, Admin access is required. Managers are also subject to team permissions. They can list datastores but need team membership to view datastore content.