> 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/account-and-organization.md).
# Account and Organization
At Plenit, two concepts coexist that are easy to confuse, but that perform very different functions: your **account** and the **organizations**.
Understanding how they differ and how they relate is the basis for navigating the platform without getting lost, because almost everything you see in the dashboard depends on this distinction.
### What your account is
Your **account** is your personal identity within Plenit. It is a single user, linked to your **email**, with your **password** and your data: first name, last name, position, phone number, language, and time zone. It is you, and it is the same wherever you are.
Your account does not contain services or subscriptions: it contains **who you are** and **how you access**. Everything personal (your profile, your security, your accesses) is managed from **My Profile**.
### What an organization is
A **organization** is a company or work environment within Plenit. It is the container where the resources really live: the **subscriptions** contracted, **users** who work in it, its **customization** branding, **contacts** and its own activity log.
Each organization also has its identifying details: a **name**, a **industry** and a **main contact**. When you work within an organization, everything you do is limited to it.
> #### 📘 The difference in one sentence
>
> Your **account** you are you. An **organization** organization is where the work is.
>
> You join organizations; they are not exclusively yours.
### One user, multiple organizations
The relationship between account and organization **is not one-to-one**:
* The same **user** user **can belong to** multiple organizations
* at the same time. **organization** The same **can have**.
multiple users
This is exactly what a partner needs: with a single account you can access both your own organization and those of the clients you manage, without logging in separately to each one.
### Your role in each organization
In each organization you belong to, you have a **permission** or role, which defines what you can do within it. In the dashboard, that permission appears next to each organization (for example, **Administrator**).
The role is **per organization**, not global: the same user can have one permission in one organization and a different one in another. That is why two people looking at the same screen can see different actions, depending on their role in that specific organization.
See which organizations you belong to and with which role from **My Profile > Organizations**, where you have the complete list and a name search tool.
### Your main organization
Among all your organizations, one acts as **main organization** and has a practical role: in your profile you can choose between **using the contact details of your main organization** or **defining your own contact details** for your user. In this way, your contact information can inherit from that organization or be specific to your user, depending on what you prefer.
### Why it matters
This distinction explains much of how the dashboard works:
* What you do in your **account** (your profile, your password, your language) accompanies you across all organizations.
* What you do within an **organization** is limited to that organization (its subscriptions, its users, its customization).
That is why the dashboard clearly separates **your global view** (everything that is yours, on Home) from **the view of a specific organization** We see it in [How the dashboard is organized.](/docs-en/platform/accounts/concepts/the-panel.md)
> #### 📘 At a glance
>
> * **User / account**: a person, an identity, an access.
> * **Organization**: a company or environment with its subscriptions, users and data.
> * **Permission / role**: what you can do within an organization (for example, Administrator).
> * **Main organization**: the reference organization for your contact details.
### Next steps
* Discover how this distinction organizes the dashboard in [How the dashboard is organized.](/docs-en/platform/accounts/concepts/the-panel.md)
* Understand the channel model in [Your resources and those of your clients.](/docs-en/platform/accounts/concepts/resources-and-clients.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 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/accounts/concepts/account-and-organization.md?ask=&goal=
```
`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.