> For the complete documentation index, see [llms.txt](https://docs.voveid.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voveid.com/docs/dashboard/team-roles-and-permissions.md).

# Team roles and permissions

Use the **Members** area of the VOVE ID dashboard to control what each teammate can see and do.

## Who can manage access

Only users with the appropriate organization admin access can manage members, roles, and permissions.

From **Settings** > **Members**, authorized admins can:

* invite new team members
* assign one or more roles to a member
* create custom roles for specific teams or workflows
* edit the permissions granted to the **Member** role and any custom role
* disable or delete custom roles that are no longer needed
* review the member and role audit trail

## Roles

### Admin

The **Admin** role has full dashboard access, including member management, role management, and sensitive review actions.

### Member

The **Member** role is the default base role for regular users. Unlike **Admin**, its permissions can be customized per organization.

## Custom roles

Custom roles help you separate access by function, for example:

* KYC reviewers
* compliance operations
* AML analysts
* support teams that only need read access

Custom roles are managed from **Settings** > **Members** > **Permissions**.

When you create a custom role, you can turn individual permissions on or off for that role. You can also:

* rename the role later
* temporarily disable it without deleting it
* delete it when it is no longer needed

If a deleted role was a member's only role, that user falls back to **Member**.

## Manual verification permission

The permission used for manual KYC review is:

* **Identity Verification** > **Manual verification**

This permission allows an authorized reviewer to:

* open the manual verification workflow on a user's session
* upload supporting documents when needed
* review and edit extracted document data
* approve a session through the manual verification flow
* perform session status updates tied to manual review

If a user does not have this permission, they should not be able to use protected manual-review actions.

## Recommended setup

Most teams use a setup like this:

* use **Admin** for trusted dashboard operators
* create one or more custom reviewer roles for operational teams
* grant **Manual verification** only to users who should handle sensitive review actions
* review role assignments regularly

## Audit trail

The dashboard includes an audit trail for member and role changes. Use it to review:

* member role assignments
* role creation, rename, disable, and delete actions
* permission changes made to editable roles

For session-specific review actions, also check the audit history attached to the user's verification session.