> 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/accounts/how-to/how-to-assign-user-permissions.md).

# How to Assign Permissions to a User

Permissions define what each user can see and do: whether they can enter the dashboard, which sections of their organization they manage, which subscriptions they can access, and which part of your partner operations you let them see. 

They are configured from the **Permissions** tab on a user.

> #### 📘 **What will you achieve?** 
>
> A user with access adjusted to what they need: neither more nor less. From whether they can enter the dashboard to the details of each section, each subscription, and the partner operations.

### Before you begin

You need to be logged in and have permission to manage users. Open the user (from **Users**, in their actions menu **⋮ > Permissions**, or in the **Permissions** tab when editing them). 

It works the same from Home and from an organization.

### The main switch

At the very top you have **Allow dashboard access?**. 

It is the master control:

* **Enabled** — the user can log in to the dashboard. Below, you define in detail what they can see.
* **Disabled** — the user does not enter the administration dashboard. Useful for someone who only uses a specific service (for example, a Remote Desktop) without managing anything.

![The Permissions tab, with the dashboard access switch](/files/572b95aeddc39cca5dc862c96d44161a57e65e72)

With access enabled, the details are divided into two tabs: **My organization** and **Partner permissions**. Each one has its own switch to enable or leave it disabled.

### My organization

Activate the block **My organization** (Enable switch) to define what the user can do in their own organization. 

Each section has a dropdown with two levels:

* **Admin** — manages that section.
* **No access** — cannot see it.

The sections you control are **Billing** (usage, invoices, and payment method), **Profile**, **Users**, **Contacts**, **Customization**, **Delete subscriptions, servers, or disks** and **Subscriptions**.

![My organization, with permissions by section](/files/0858a9911936e69449a43f1da8ac2c19e901171b)

Below, a table **Services · Subscription · Permissions** lets you fine-tune access **to each subscription** separately (Storage, Remote Desktop, Servers, DNS, and more), also with Admin or No access.

> #### 📘 **Custom access** 
>
> You can give Admin in some sections and No access in others, and the same subscription by subscription. This lets you build profiles as broad or as limited as you need.

### Partner permissions

The tab **Partner permissions** controls which part of **your operations as a Plenit partner** you grant to that customer user. Activate it (Enable switch) and adjust each block with Admin or No access:

* **General** — the main dashboard and the management of your customers' organizations, users, subscriptions, and events.
* **Go to Market** — quotes, customer billing, rates, and resource customization.
* **Migrations** — the migration tool.

![Partner permissions, with General, Go to Market, and Migrations](/files/8db73242db772d0f42766b25c43ab9e16bc00e96)

> #### 🚧 **Grant this carefully** 
>
> Partner permissions opens parts of your partner operations. Give access only to what you really want that user to see, and leave the rest as No access.

### Save

When you have the distribution the way you want it, save the changes. The user will then see and manage exactly what you have granted them.

### Conclusion

With permissions, you decide the scope of each user on three levels: whether they enter the dashboard, what they do inside their organization (section by section and subscription by subscription), and which part of your partner operations you let them see. It is the tool for giving each person exactly the access they need.

### Next steps

* Does the user not exist yet? Create it in [How to add users.](/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)
* Edit, activate, or delete it in [How to manage your users](https://claude.ai/chat/como-gestionar-tus-usuarios).


---

# 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/accounts/how-to/how-to-assign-user-permissions.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.