> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/reference/user-management.md).

# User Management

Account settings, user roles, and permissions across ARENA360

{% embed url="<https://youtu.be/e2IH2gasNrs>" %}

Manage user accounts, roles, and permissions across the ARENA360 platform. This guide covers user invitations and role-based access control across all products.

***

## User Roles & Permissions

* **Users:** This is where all user accounts are listed. You can edit a user profile or create a new user account.

### Inviting Users

To invite a new user (Admin only):

1. Click your avatar icon → **User Management**
2. Go to **Users** in the sidebar
3. Click **Invite User**
4. Enter the user's email address
5. Select the appropriate role(s)
6. Click **Send Invitation**

The user will receive an email invitation to join your organization.

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-4e1d4453683b66de2d7944bf9130a6a3d899378b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-97206505b94d285fb9267be4fe67f0a61263545d%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Editing User Roles

To change a user's role (Admin only):

1. Click your avatar icon → **User Management**
2. Go to **Users** in the sidebar
3. Find the user in the list
4. Click the three-dots menu (⋮)
5. Select **Edit roles**
6. Choose the new role(s)
7. Click **Update**

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-fe5659eec8238a1d13d10866d672c3a70397249e%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

***

### ARENA360 Roles

ARENA360 uses a capability-based roles and permissions model. **Each product has specific roles, and each tier inherits all capabilities from the previous one**.

| Role                      | Capabilities                                                                               |
| ------------------------- | ------------------------------------------------------------------------------------------ |
| **TRADE - Admin**         | Full control and user management. Invite users, edit roles, manage account-level settings. |
| **TRADE - Senior Trader** | Advanced trading & configuration capabilities (edit odds, distributor, data limits)        |
| **TRADE - Trader**        | Trading using existing configurations. Cannot edit configurations or odds settings.        |
| **TRADE - Analyst**       | View-only access. Monitoring and support. Cannot place orders or change configurations.    |

***

## Related

* [Profile & Account Settings](/u/trade/user-guide/configuration/user-avatar.md) — Avatar menu, profile, and time zone settings
* [Authentication](/u/reference/authentication.md) — Platform authentication overview
* [DEFEND Authentication](/u/defend/integration-guide/authentication.md) — DEFEND-specific API setup


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lsports.eu/u/reference/user-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.