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

# Concepts

The key ideas in your account: what your account is versus an organization, your profile, how the dashboard is organized, and how your resources are separated from your customers'.

Understand how your account is organized before working with it: what your account is, what an organization is, how the dashboard is structured, and why many screens separate yours from your clients'.

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>My Profile</strong></td><td>The personal face of your account: your data, your security, your organizations, and your activity, in four tabs.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/concepts/my-profile.md">My Profile</a></td></tr><tr><td><strong>Account and Organization</strong></td><td>What your account is, what an organization is, and why the same user belongs to several with a different role in each one.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/concepts/account-and-organization.md">Account and Organization</a></td></tr><tr><td><strong>How the Dashboard Is Organized</strong></td><td>The three levels of the menu and the difference between your global view and that of a single organization.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/concepts/the-panel.md">How the Dashboard Is Organized</a></td></tr><tr><td><strong>Your Resources and Those of Your Clients</strong></td><td>Why several Home screens separate your organization's content from your clients' content in two tabs.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/concepts/resources-and-clients.md">Your Resources and Your Customers'</a></td></tr><tr><td><strong>Glossary</strong></td><td>The terms that appear most often in the Account documentation, with a brief definition.</td><td><a href="https://docs.plenit.com/docs-en/platform/accounts/concepts/glossary.md">Glossary</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/accounts/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.
