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

# User management

> Invite users, assign roles, and control what each team member can access in the lite dashboard.

Give your team access to the lite dashboard while controlling what each person can see and do.

In lite, access is built around three things:

* **Users** are the people who can access your account.
* **Roles** group permissions for a specific type of responsibility.
* **Permissions** define the individual actions a role can perform.

When you invite a user, you assign them a role. The role determines what they can access and which actions they can take.

## Invite a user

1. **Open User Management.** Go to **Settings → User Management**.
2. **Add a new user.** Select **Add New User**.
3. **Enter the user's details.** Enter the user's **full name**, **email address**, and **mobile number**.
4. **Choose a role.** Select the role that matches what the user needs to do.
5. **Send the invitation.** Select **Submit Invitation**.

The invited user receives an invitation to join your lite account.

From **User Management**, you can also see each user's role, contact details, last activity, and current status.

## Choose a role

lite provides predefined roles for common responsibilities. Choose the role that most closely matches what the person needs to do.

| Role                  | Recommended for                               | Typical access                                                                                        |
| --------------------- | --------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Admin**             | Business owners and account administrators    | Broad access to manage users, roles, payments, finance operations, reports, and account configuration |
| **Financial Manager** | Finance leads and treasury teams              | Payments, beneficiaries, transfers, settlements, disputes, and financial reporting                    |
| **Finance Staff**     | Accountants and finance operations teams      | Preparing and monitoring beneficiaries and transfers                                                  |
| **Developer**         | Engineers and integration teams               | Transaction visibility, API keys, webhooks, and technical reporting                                   |
| **Support Agent**     | Customer support and payment operations teams | Transaction investigation, merchant information, users, and disputes                                  |
| **Viewer**            | Auditors, managers, and other stakeholders    | Read-only visibility into selected account information                                                |

### Admin

Use **Admin** for people responsible for administering the lite account.

Admins have broad access across the dashboard, including user and role management, payment operations, financial operations, reporting, and account configuration.

> **Warning**
>
> Admin access includes sensitive actions. Keep the number of Admin users limited to people who need this level of control.

### Financial Manager

Use **Financial Manager** for people responsible for payments and money movement.

A Financial Manager can work with areas such as:

* Transactions
* Captures, voids, and refunds
* Beneficiaries
* Transfers
* Settlements
* Disputes
* Financial reports

For example, a Head of Finance may need to refund a payment, review a transfer, reconcile settlements, and export monthly reports without managing technical integration settings.

### Finance Staff

Use **Finance Staff** for team members who support day-to-day finance operations with more limited access.

This role is suited to people who prepare and monitor beneficiaries and transfers while broader financial control remains with a Financial Manager or Admin.

### Developer

Use **Developer** for engineers who maintain or troubleshoot your lite integration.

Developer access focuses on technical areas such as:

* Viewing transactions
* Viewing reports
* Managing API keys
* Managing webhooks

This lets engineers work on the integration without giving them access to unrelated finance or user-management operations.

### Support Agent

Use **Support Agent** for people investigating merchant or customer payment issues.

Support access focuses on operational visibility, including:

* Viewing transactions
* Viewing merchant information
* Viewing users
* Working with disputes

For example, a support agent can investigate a reported payment and review the related dispute information without receiving administrative access to the account.

### Viewer

Use **Viewer** for people who need visibility without operational control.

This is suitable for auditors, managers, and other stakeholders who need to monitor selected account information without changing it.

## Create a custom role

Predefined roles cover common team structures. If your team needs a different combination of access, you can create a custom role.

> **Note**
>
> A custom role lets you choose permissions individually instead of giving the user access they do not need.

For example, you might need:

* A finance analyst who can view and export settlements without creating transfers.
* A technical support engineer who can view transactions and webhooks without managing API keys.
* An operations user who can issue refunds and respond to disputes without managing users.

1. **Open Roles Management.** Go to **Settings → User Management**, then select **Manage Roles**.
2. **Add a role.** Select **Add New Role**.
3. **Name the role.** Enter a **Role Name** that makes its purpose clear to your team.
4. **Choose permissions.** Select the actions this role is allowed to perform in each area.
5. **Create the role.** Create the role, then assign it when inviting or managing users.

## Available permissions

When creating a custom role, permissions are grouped by area.

| Area                  | Available permissions               |
| --------------------- | ----------------------------------- |
| **API Keys**          | View, Create, Edit, Delete          |
| **Beneficiaries**     | View, Create, Export, Check         |
| **Disputes**          | View, Create, Edit, Respond         |
| **Merchant Settings** | View, Edit                          |
| **Payment Methods**   | View, Create, Edit, Delete          |
| **Reports**           | View, Create, Export, Schedule      |
| **Roles**             | View, Create, Edit, Delete          |
| **Settlements**       | View, Export, Configure             |
| **Transactions**      | View, Export, Capture, Void, Refund |
| **Transfers**         | View, Create, Export, Check         |
| **Users**             | View, Create, Edit, Delete          |
| **Webhooks**          | View, Create, Edit, Delete          |

## Understand permission actions

The same action can appear across different areas of the dashboard.

| Permission    | What it allows                                                   |
| ------------- | ---------------------------------------------------------------- |
| **View**      | See the resource and its information                             |
| **Create**    | Create a new resource                                            |
| **Edit**      | Change an existing resource                                      |
| **Delete**    | Remove an existing resource                                      |
| **Export**    | Export or download data                                          |
| **Capture**   | Capture an authorized payment                                    |
| **Void**      | Cancel an authorization before it is captured                    |
| **Refund**    | Return funds for a payment                                       |
| **Check**     | Review a beneficiary or transfer as part of the finance workflow |
| **Respond**   | Respond to a dispute                                             |
| **Configure** | Change the available configuration for that area                 |
| **Schedule**  | Schedule a report                                                |

The permissions available depend on the area you are configuring.

## Which role should I choose?

| If this person needs to...                            | Start with            |
| ----------------------------------------------------- | --------------------- |
| Run and administer the lite account                   | **Admin**             |
| Manage payments, settlements, and treasury operations | **Financial Manager** |
| Prepare beneficiaries and transfers                   | **Finance Staff**     |
| Maintain the payment integration                      | **Developer**         |
| Investigate customer payment issues                   | **Support Agent**     |
| Monitor activity without making changes               | **Viewer**            |
| Have a specific combination of permissions            | **Custom role**       |

> **Tip**
>
> Give each person only the access they need for their responsibilities. Use a custom role when a predefined role gives them too much or too little access.

## Manage existing users

The **User Management** page gives you a central view of the people who can access your lite account.

For each user, you can see:

* Name
* Role
* Email address
* Phone number
* Last activity
* Status

Users with the required permissions can add, edit, or remove users and manage role access as responsibilities change.