> 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/concepts/the-organization-panel.md).

# The Organization Dashboard

The six sections of an organization's dashboard and how to enter and work in it.

Each organization has its own dashboard, with everything needed to manage it.

It is the section **Organization** of the sidebar, and it expands into six sections.

### How you enter an organization

To work within an organization, select it in the **organization selector** on the sidebar (top left, under the name of the active organization).

You can also enter from the organization list with the action **Go to organization**.

> #### 📘 **You always work within an organization**
>
> The selector shows which organization you are operating in at any given time. If you manage several, check which one is active before making changes.
>
> How to switch between them, in [How to change organization.](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-manage-users.md)

### The six sections

* **Subscriptions** — the subscriptions for that organization, with their usage metrics. It is the view of a single organization; signup and management are covered in [How to create and manage your subscriptions.](https://docs.plenit.com/docs-en/platform/organizations/detalles/subscriptions.md)
* **Users** — the organization's users: individual or bulk signup, editing, and permissions. Details are in the Account How-to guides.
* **Customization** — the branding of the User Portal and the Admin Panel (logo, colors, favicon, domain and certificate) and email configuration. Here you define, among other things, what the end customer will see in their portal.
* **Profile** — the organization's details (company name, tax ID, address), its settings (language, billing mode, time zone, currency) and the option to delete it.
* **Contacts** — the organization's contacts by type: primary, operations, and billing.
* **Events** — the organization's activity log. It is the same log you see in your account; how to consult and export it, in [How to consult and export your events.](https://docs.plenit.com/docs-en/platform/organizations/detalles/events.md)

### Next steps

* Review each section in detail in [Details.](https://docs.plenit.com/docs-en/platform/organizations/detalles.md)
* Learn how to create, edit, block, or delete organizations in [How-to.](https://docs.plenit.com/docs-en/platform/organizations/how-to.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 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/concepts/the-organization-panel.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.
