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

# Users, roles, and quotas

![Users, roles, and quotas](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FSvMpCgulV2C0pE8pGFw7%2Fve20261112v5-admin-users.png?alt=media)

## Goal

Create accounts and keep class capacity inside licence and host limits.

## Roles (source)

| Role       | Typical use                                                      |
| ---------- | ---------------------------------------------------------------- |
| **admin**  | Users, licence, Assist LLM, management network, wipe/maintenance |
| **editor** | Build and operate labs; import images; MCP tools when licensed   |
| **user**   | Use shared / owned labs within quotas                            |

## Recipe: add a user

1. Administration -> **Users** (admins only)
2. Enter username and initial password
3. Choose role: `admin`, `editor`, or `user`
4. Optional: set **CPU quota** and **RAM quota (MB)** (`0` = unlimited)
5. Create the user
6. Ask them to change password on first login when prompted

Licence **max users** is enforced on create (Licence).

## Recipe: edit quotas later

1. Find the user in the Users table
2. **Edit quotas**
3. Set CPU and RAM MB (`0` = unlimited)
4. Confirm

Quotas apply to nodes the user **owns** when starting. Use them so one student cannot exhaust the classroom host.

## Recipe: change role or disable

Use the role dropdown on the user row. Disable or delete unused accounts when seats are tight.

## Expected result

* Students can sign in to the web UI
* Clear errors when licence seats or CPU/RAM quotas are exceeded

## If it fails

| Symptom            | Fix                                                               |
| ------------------ | ----------------------------------------------------------------- |
| Cannot open Users  | You are not admin                                                 |
| Cannot create user | Seat count exhausted - disable unused accounts or upgrade edition |
| Start blocked      | Check per-user CPU/RAM quotas and concurrent lab limits           |

## Related

* Licence editions and activation
* Classroom for instructors


---

# 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.vex-nx.com/admin-guide/users-roles-and-quotas.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.