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

# Concepts

The key organization concepts: what an organization is, the six sections of its dashboard, and how the end customer sees your brand.

Understand what an organization is before setting it up: each client's workspace, how its dashboard is structured, and why the end customer sees your brand and not Plenit's.

Here's why, without steps.

{% hint style="info" %}
Looking for the step-by-step guide? You have it in How-to. Here we explain what each thing is and how it fits together.
{% endhint %}

### Explore the concepts

<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>What is an Organization</strong></td><td>A client's workspace: their subscriptions, users, contacts, billing, and brand.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/concepts/what-it-is.md">What Is an Organization</a></td></tr><tr><td><strong>The Organization Dashboard</strong></td><td>The six sections of an organization's dashboard and how to get in and start working in it.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/concepts/the-organization-panel.md">The Organization Dashboard</a></td></tr><tr><td><strong>The End Customer and the Partner's Brand</strong></td><td>Each organization is an end customer that sees your brand, not Plenit's, on both of its interfaces.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/concepts/end-client-and-brand.md">The End Customer and the Partner Brand</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/concepts.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.
