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

# Details

The organization reference: the list and the six sections of an organization's dashboard, field by field.

The field-by-field reference for organizations.

There are no steps here: you’ll find what each screen shows, what its fields mean, and what actions are available to you.

Consult it whenever you need the exact data.

### Explore the details

<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>Organization list</strong></td><td>The columns, order, and actions of your client organizations list.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles/list.md">Organizations List</a></td></tr><tr><td><strong>Profile</strong></td><td>The organization data, its settings (language, billing, time zone, currency), and its deletion.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles/profile.md">Profile</a></td></tr><tr><td><strong>Subscriptions</strong></td><td>The catalog for deploying services and the view of active subscriptions with their metrics.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles/subscriptions.md">Subscriptions</a></td></tr><tr><td><strong>Users</strong></td><td>The list, the user form, and the permissions screen.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles/users.md">Users</a></td></tr><tr><td><strong>Contacts</strong></td><td>Contacts by type: primary, operations, and billing.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles/contacts.md">Contacts</a></td></tr><tr><td><strong>Customization</strong></td><td>The branding of the User Portal and the Admin Panel, and email settings.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles/customization.md">Customization</a></td></tr><tr><td><strong>Events</strong></td><td>The organization's activity log.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/details/events.md">Events</a></td></tr></tbody></table>


---

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