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

# Organizations

Create, configure, and manage the organizations you serve, move between them, and work with each one's dashboard.

An organization is the workspace where a client's subscriptions, users, contacts, billing, and brand live.

From Plenit, you manage as many as you need: yours and those of the clients you serve.

The setup and management of its users and subscriptions are documented in Account; here you focus on the organization itself: creating it, configuring it, its dashboard, and the full list.

### Most viewed articles

1. [What an organization is](https://docs.plenit.com/docs-en/platform/organizations/concepts/what-it-is.md)
2. [The end customer and the partner's brand](https://docs.plenit.com/docs-en/platform/organizations/concepts/end-client-and-brand.md)
3. [The organization dashboard](https://docs.plenit.com/docs-en/platform/organizations/concepts/the-organization-panel.md)
4. [Organization list](https://docs.plenit.com/docs-en/platform/organizations/detalles/list.md)
5. [Organization profile](https://docs.plenit.com/docs-en/platform/organizations/detalles/profile.md)
6. [Subscriptions](https://docs.plenit.com/docs-en/platform/organizations/detalles/subscriptions.md)
7. [Users and permissions](https://docs.plenit.com/docs-en/platform/organizations/detalles/users.md)
8. [Customization and white-label](https://docs.plenit.com/docs-en/platform/organizations/detalles/customization.md)
9. [Contacts](https://docs.plenit.com/docs-en/platform/organizations/detalles/contacts.md)
10. [Switch organization](https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-create-an-organization.md)

### Explore Organizations

<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>Create and launch your first customer organization.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>What an organization is, white-label, and its dashboard.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Create, customize, and manage your organizations.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/how-to.md">How-to</a></td></tr><tr><td><strong>FAQ</strong></td><td>Quick answers to the most common questions about organizations.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/faq.md">Frequently Asked Questions</a></td></tr><tr><td><strong>Details</strong></td><td>The list, the form, and the organization dashboard.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles.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 events tab in the organization dashboard.


---

# 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/organizations.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.
