> 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.md).

# Accounts

Your personal identity in Plenit: one user, multiple organizations, and your global view of everything that's yours.

Your account is your personal identity in Plenit: a single user that can belong to multiple organizations, with a distinct role in each one.

From here, you can navigate the dashboard, configure your information, and review everything assigned to you. Managing organizations (creating them, editing them, or entering one) lives in its own section, Organizations.

### Most viewed articles

1. [Add users](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-add-users.md)
2. [Manage your users](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-manage-users.md)
3. [Apply permissions to a user](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)
4. [Manage your subscriptions](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-manage-subscriptions.md)
5. [Configure your security emails](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-configure-security-emails.md)
6. [View and export your events](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-view-and-export-events.md)
7. [My Profile](https://docs.plenit.com/docs-en/platform/accounts/concepts/my-profile.md)
8. [Your account and your organization](https://docs.plenit.com/docs-en/platform/accounts/concepts/account-and-organization.md)
9. [Account security](https://docs.plenit.com/docs-en/platform/accounts/details/security.md)
10. [The Home lists](https://docs.plenit.com/docs-en/platform/accounts/details/lists.md)

### Explore Account

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quick start</strong></td><td>Set up your account and get oriented in the dashboard in four steps.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>Your account and organizations, the dashboard, and My Profile.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Add users, apply permissions, manage subscriptions, and view your events.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/how-to.md">How-to</a></td></tr><tr><td><strong>FAQ</strong></td><td>Quick answers to the most common questions about your account.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/faq.md">Frequently Asked Questions</a></td></tr><tr><td><strong>Details</strong></td><td>Profile fields, lists, security, and events.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/details.md">Details</a></td></tr></tbody></table>

### Support

Need help with your servers?

Open a ticket or write to us via [WhatsApp](https://docs.plenit.com/docs-en/support/whatsapp.md) from the Support section.

### Latest updates

July 1, 2026 — New user import from template in Home.

July 1, 2026 — New UX


---

# 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.plenit.com/docs-en/platform/accounts.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.
