> 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-manage-users.md).
# How to Manage Your Users
From **Users** you keep the people in your organization up to date: you change their details, control who has active access, and remove anyone who should no longer enter.
> #### 📘 **What will you achieve?**
>
> Having your user list under control: edit their details, enable or disable their access, and delete anyone who no longer belongs there.
### Before you start
You need to be logged in and have permission to manage users. You work from **Users**, with two paths depending on where you are:
* **From Home** — in **Home > Users**, tab **My users**, you see the people in your organization.
* **From an organization** — in **Organization > Users**, you see only those of that organization.
If what you want is to create a user, go to [How to create users.](/docs-en/platform/accounts/how-to/how-to-add-users.md)
### Edit a user
In the user's row, open the actions menu (⋮). It has four options: **Edit**, **Permissions**, **Delete** and **Delete notifications**.
Press **Edit** to open its form, organized into three tabs: **Profile**, **Other contacts** and **Permissions**.
In **Profile** you change their details, language and time zone, and manage their password (keep the current one, force a new one at the next login, or enter one manually) and their two-step verification.
In **Other contacts** you decide whether it uses the main organization's data or its own. In **Permissions** you define their access, which we cover in [How to apply permissions to a user. ](/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)
Press **Save** when finished.
### Enable or disable a user
In the column **Status**, use the toggle to set the user to **Enabled** or **Disabled**. A disabled user cannot access the platform, but remains in the list.
> #### 📘 **Disabling is not deleting.**
>
> Disabling cuts off access temporarily and you can re-enable it whenever you want. Deleting is permanent.
### Delete a user
In the actions menu, click **Delete**. A confirmation modal opens **confirmation** indicating that the user will be unsubscribed from all the services they are in. For security, you will need to type **DELETE** to confirm.
> #### ❗️ **Irreversible action.**
>
> Deleting a user is permanent and cannot be undone.
### The "Clients" tab
In **Home > Users** you have two tabs.
**My users** are those of your own organization (what we have seen).
**Clients** gathers the users from all of your clients' organizations, with their **Main organization**.
Its actions menu is more limited: **Edit** and **Change main organization**.
Change their organization
### Conclusion
With these actions you manage your users' day-to-day: you adjust their details, control their access by enabling or disabling them, and delete them when they should no longer enter.
To define what each one can access (the dashboard, the organization's sections, and their subscriptions), use **Permissions** in the actions menu. Permission assignment is covered in[ How to apply permissions to a user.](/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)
### Next steps
* Haven't created it yet? Start with [How to create users.](/docs-en/platform/accounts/how-to/how-to-add-users.md)
* Define what each one can access in [How to apply permissions to a user.](/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)
* See what each column in the list shows in [The lists.](/docs-en/platform/accounts/details/lists.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/accounts/how-to/how-to-manage-users.md?ask=&goal=
```
`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.