# Personal Account Permissions

Source: https://userguide.qualytics.io/settings/access/users/permissions/

This page covers the roles and permissions required to manage Personal Accounts.

> **Note: Admin only**
>
> Only users with the **Admin** user role can manage other users' Personal Accounts (invite new users, edit their user role, assign teams, deactivate, or reactivate). Individual users cannot modify their own user role or team assignments.

## User Roles (Workspace-Level)

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| View user list | Not allowed | Allowed | Allowed |
| Export the Access Report (every user's effective access to every datastore) to an enrichment datastore from a [Flow](https://userguide.qualytics.io/flows/actions/how-tos/operation/configure-a-global-export-action/) | Not allowed | Not allowed | Allowed |
| Invite user | Not allowed | Not allowed | Allowed |
| View and revoke invitations | Not allowed | Not allowed | Allowed |
| View, configure, and test sign-in providers | Not allowed | Not allowed | Allowed |
| Approve or reject identity links | Not allowed | Not allowed | Allowed |
| View the sign-in log | Not allowed | Not allowed | Allowed |
| Reset own password | Allowed | Allowed | Allowed |
| Edit user (user role, teams) | Not allowed | Not allowed | Allowed |
| Deactivate user | Not allowed | Not allowed | Allowed |
| Reactivate user | Not allowed | Not allowed | Allowed |
| [Enable or disable Qualytics team access](https://userguide.qualytics.io/managed-deployment/qualytics-team-access/) (managed deployments) | Not allowed | Not allowed | Allowed |
| Generate own Personal Token | Allowed | Allowed | Allowed |
| Review AgentQ audit history | Not allowed | Not allowed | Allowed |
| Comment on a check template's Timeline | Allowed | Allowed | Allowed |
| Delete another user's comment | Not allowed | Not allowed | Allowed |

> **Note: Comments on the Timeline**
>
> The two rows above are the only comment actions decided by the user role. A check template does not belong to a datastore, so any user can read its Timeline, comment, reply, and manage their own comments. Deleting another user's comment is reserved for the **Admin** user role, on every asset, and editing another user's comment is never allowed. On containers, quality checks, and anomalies, commenting is gated by team permissions instead: see [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/).

Password recovery requires an existing password account, an enabled Email & Password provider, and working email delivery. See [Reset Your Password](https://userguide.qualytics.io/settings/access/sign-in-providers/how-tos/reset-password/). Provider administration and the related Access tabs are covered in [Sign-In Provider Permissions](https://userguide.qualytics.io/settings/access/sign-in-providers/deep-dive/permissions/).

## UI Behavior Without Permission

| Scenario | What the user sees |
| --- | --- |
| User has the **Member** user role | Cannot access the Access settings page to manage other users. Can still manage their own Personal Tokens on the Tokens page. |
| User has the **Manager** user role | Can view the user list and the team list on the Access settings page but cannot edit, deactivate, or reactivate other users. |
| User has the **Admin** user role | Full access to manage all users: edit their user role, assign teams, deactivate, and reactivate. |

The AgentQ audit is also restricted to the **Admin** user role. Managers can manage the AgentQ integration but cannot open its workspace-wide audit history.

> **Info**
>
> For detailed information about team-level permissions (Editor, Author, Drafter, Viewer, Reporter), refer to the [Team Permissions](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/) documentation.

## Lineage Access

Lineage edits use team permissions as well as the user role. The **Manager** role alone does not grant write access.

| Action | Member | Manager | Admin |
| --- | --- | --- | --- |
| Create, edit or delete lineage connections; submit OpenLineage changes | Editor on every affected datastore | Editor on every affected datastore | All datastores |
| Read OpenLineage job/run details | Viewer on every managed endpoint's datastore | Viewer on every managed endpoint's datastore | All datastores |

An Admin restricted to a team follows that team's permissions. Submitting owner names through OpenLineage does not change user roles or team access. See [Lineage Permissions](https://userguide.qualytics.io/lineage/deep-dive/permissions/#team-permissions) and the [Team Permission Matrix](https://userguide.qualytics.io/settings/access/teams/team-permissions/overview/#permission-matrix).

*Last updated: October 27, 2026.*
