> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/organizations/detalles/users.md).

# Users

The section **Users** manages the people in that organization: their registration, their data and, above all, their permissions. 

Management is the same as at your account level, so here we describe what is specific to the organization panel and link to the guides.

### The list

It shows all the organization's users ("All users (N)"), with the buttons **Import users** and **New user** and a **Filter** by name or email. The columns are:

| Column   | What it shows                                                         |
| -------- | --------------------------------------------------------------------- |
| User     | Name and email.                                                       |
| State    | Enabled / Disabled toggle.                                            |
| Services | The services it has access to.                                        |
| Actions  | The menu (⋮) with Edit, Permissions, Delete notifications and Delete. |

### The user form

When creating or editing a user, the form has three tabs: **Profile**, **Other contact details** and **Permissions**.

* **Profile** — General (Email as read-only, First name, Last name, Phone and Position optional) and Settings (Language, Time zone), plus Password (keep / force / enter manually) and Two-step verification.
* **Other contact details** — use the organization's ones or define your own data.

The step-by-step guide for these tasks is in the account guides:[ How to create users](/docs-en/platform/accounts/how-to/how-to-add-users.md) and[ How to manage your users.](/docs-en/platform/accounts/how-to/how-to-manage-users.md)

### The Permissions tab

Defines what the user can access. At the top, a general toggle, **Allow dashboard access?**, decides whether they can log in to the dashboard. Below, two tabs:

**My organization** — access within the organization, section by section, with a dropdown **Admin** or **No access**:

| Section                                 | What it controls                    |
| --------------------------------------- | ----------------------------------- |
| Billing                                 | Usage, invoices and payment method. |
| Profile                                 | The organization's data.            |
| Users                                   | User management.                    |
| Contacts                                | The organization's contacts.        |
| Customization                           | Branding and email.                 |
| Delete subscriptions, servers, or disks | Resource deletion.                  |
| Subscriptions                           | The organization's subscriptions.   |

Plus a table **Services · Subscription · Permissions**, where you define access to each subscription as User or No access.

**Partner permissions** — access to the partner operations that you grant to the customer user, also with Admin or No access:

| Block        | What it opens                                                                                          |
| ------------ | ------------------------------------------------------------------------------------------------------ |
| General      | The main dashboard and the management of your clients' organizations, users, subscriptions and events. |
| Go to Market | Quotes, Customer invoicing, Rates and Resource customization.                                          |
| Migrations   | The migration tool.                                                                                    |

> 🚧 **Tags under review** The two-step verification options may still be labeled "Panel" with the previous brand. Check the exact name when configuring them.

The step-by-step assignment is in [How to apply permissions to a user.](/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)

### Next steps

* Review the other sections of the dashboard in [Details.](/docs-en/platform/organizations/detalles.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/platform/organizations/detalles/users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.