> 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

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 the 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 an Organization Is</strong></td><td>A client's workspace: its subscriptions, users, contacts, billing, and branding.</td><td><a href="/pages/2e27f1b4728400d35bc29382760156d411b95a5e">/pages/2e27f1b4728400d35bc29382760156d411b95a5e</a></td></tr><tr><td><strong>The Organization Dashboard</strong></td><td>The six sections of an organization's dashboard and how to enter and work in it.</td><td><a href="/pages/842d017e0580eeda278fc7143d13c48c1d3fef10">/pages/842d017e0580eeda278fc7143d13c48c1d3fef10</a></td></tr><tr><td><strong>The End Customer and the Partner Brand</strong></td><td>Each organization is an end customer that sees your brand, not Plenit's, on its two surfaces.</td><td><a href="/pages/9314b6522025a31a563d739d2547af6428bb72d9">/pages/9314b6522025a31a563d739d2547af6428bb72d9</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/platform/organizations/concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.