> ## Documentation Index
> Fetch the complete documentation index at: https://docs.velyti.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Users and roles

> Invite your team and choose their roles and branches.

Everything about who can sign in and what they can do lives in **Administration** > **Users**: that is where you invite your team and give them their roles. You need the matching permissions to see and change users.

![The Users list.](https://mintcdn.com/steven-org/noO9Oyl9XjPvnXlz/images/en/users.png?fit=max\&auto=format\&n=noO9Oyl9XjPvnXlz\&q=85\&s=28d4efdbb9a23fdb951f67a1486c25f1)

The Users list.

## Users

The **Users** page lists your team. Search by name, username or email, and filter by **Any role** or **Any status**. A summary shows how many users are active and how many inactive.

Each user is **Active** or **Inactive**. An account that was invited and has not set its password yet shows **Invitation pending**, or **Invitation expired** if the link lapsed.

### Invite a user

**1. Open the form**

Choose **New user**.

**2. Fill in the details**

Enter the given names, last name, ID number, email and a **Username**. The username is unique across all of Velyti.

**3. Choose the roles**

Choose at least one role. Each role says what it is for. A user may hold several roles, and their permissions add up.

**4. Send the invitation**

The app sends an email with a link to set a password. The link expires in 72 hours. Nobody types a colleague's password: the person sets their own.

If the email does not arrive, open the user's row actions and choose **Resend invitation**, or use **Reset access**. The app shows an **Access link** once. Copy it and hand it over through a safe channel: Velyti only keeps its fingerprint. The app says whether the email also went out; if it did not, hand the link over yourself.

> [!WARNING]
>
> **Reset access** generates a link to set a new password and closes the person's open sessions.

### Whom you can manage

You can edit, deactivate, delete or send an access link only to users whose permissions you also hold and who work only in your branches; the **Administrator** can manage everyone. For anyone else those actions do not appear, so their password, email or account cannot be changed by someone with less access.

### Branches

When you **Edit** a user, **Branches** sets where they work: the branches whose vehicles, contracts and procedures they see and record. Choose **Every branch** (including those opened later) or **Only these branches** with at least one selected; it is saved with the rest of the form when you press **Save**. You can only give branches you work in yourself, and only someone who works in every branch can give every branch. The change reaches their session within a few minutes.

### Deactivate, activate or delete

| Action | What happens |
| - | - |
| **Deactivate** | The person cannot sign in until the account is reactivated. Their contracts do not change. An open session closes within a few minutes. |
| **Activate** | The person can sign in again with their usual password. |
| **Delete** | The account is erased with its sign-in details. Only an account without contracts or recorded actions can be deleted, and it cannot be undone. |

To stop someone signing in while keeping their name on the paperwork, deactivate them. Your plan may limit active users; see [Plan and billing](https://docs.velyti.com/en/administration/subscription.md).

## Roles

A role is a set of permissions for one kind of work. The standard roles are **Administrator**, **Basic user**, **Management**, **Sales advisor**, **Purchasing appraiser** and **Accounting**. A user holds the sum of the permissions of all their roles.

You choose which roles each person holds when you invite them or **Edit** their account; Velyti defines what each role allows. You never set permissions one by one.

> [!TIP]
>
> No role fits someone? Write to us from [Support](https://docs.velyti.com/en/help/support.md) and we adjust a role or create a new one for your company. Avoid giving **Administrator** to someone who does not run the company: it holds every permission, including creating users, seeing payments and giving Support access.

You can only give roles whose permissions you also hold; the **Administrator** can give them all.

See [Profile and settings](https://docs.velyti.com/en/administration/profile-and-settings.md) to check your own permissions, and [Glossary](https://docs.velyti.com/en/help/glossary.md) for terms.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.