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

# How the Panel is Organized

Everything in Plenit is navigated from a **side menu** structured in three levels.

It is not an aesthetic detail: each level answers a different question — what do I have in total, what services are there, what is happening in this organization — and understanding them saves you from going around trying to find where everything is.

### The three levels

#### 1. Home — your global view

It is the **overall picture of everything yours**, aggregated across all your organizations. It brings together:

* **Overview** — your entry point, with an overview of your activity and your counters for organizations, subscriptions, and users.
* **Organizations** — all the organizations you manage, where you also create new ones. Their management is documented in its own section, **Organizations**.
* **Subscriptions** — all subscriptions, adding yours and your clients'.
* **Users** — all users, yours and your clients'.
* **Events** — the activity and access log.

#### 2. Cloud Services, Marketplace and IT Management — the services

It is the layer of **Plenit services**, with a cross-cutting view of what you have contracted and what you can contract. From here you access the catalog (Servers, Remote Desktop, Disaster Recovery, storage, and more), the Marketplace, and IT Management.

#### 3. Organization — a single organization

It is the level limited to **the organization you have selected**. Here you manage, only for that organization: its **Subscriptions**, **Users**, **Customization**, **Profile**, **Contacts**, **Events** and the **Partner Zone**. Each of these sections is documented in its own section.

```mermaid
graph LR
    N1["<b>1 · Home</b><br/>Your global view<br/>———<br/>• Overview<br/>• Organizations<br/>• Subscriptions<br/>• Users<br/>• Events"]
    N2["<b>2 · Services</b><br/>Plenit catalog<br/>———<br/>• Cloud Services<br/>• Marketplace<br/>• IT Management"]
    N3["<b>3 · Organization</b><br/>One single company<br/>———<br/>• Subscriptions<br/>• Users<br/>• Personalization<br/>• Profile<br/>• Contacts<br/>• Events"]
    U["<b>User menu</b><br/>———<br/>• Usage<br/>• Payment Methods<br/>• Organization Profile<br/>• My Profile<br/>• Log out"]

    N1 --> N2 --> N3
    N3 -.- U 
```

> #### 📘 Your account, always at hand
>
> Apart from the three levels, your **account** is always accessible from the **user menu**, in the lower-left: from there you open My Profile, change the theme (light or dark), and log out.

### Global view versus organization view

The fundamental difference between **Home** and the level **Organization** is the **scope**: how much of what you see it covers.

|                     | Home (global view)                                                | Organization (single)                      |
| ------------------- | ----------------------------------------------------------------- | ------------------------------------------ |
| **Scope**           | All your organizations at once                                    | Only the selected organization             |
| **What you see**    | The total of your organizations, subscriptions, users, and events | What belongs to that organization          |
| **When you use it** | To get the overall picture and jump between organizations         | To work in depth within a specific company |

That is why there are sections that appear **in both places** —Subscriptions, Users and Events—: they are not duplicated; they show the same thing with different scope. For example, in **Home > Subscriptions** you can see all the subscriptions of all your organizations at a glance; if you enter a client's organization, you only see theirs.

To switch organizations, use the **Organization selector** selector in the side menu.

> #### 🚧 Warning: there are two places called "Organizations"
>
> It is the most common confusion. They are not the same:
>
> * **Home > Organizations** — the **management**: you view and manage **all** your organizations and create new ones. We document it in its own section, **Organizations**.
> * **My Profile > Organizations** — the **personal**: you check which **you belong to** and with what **role**.
>
> Quick rule: to manage organizations, go to Home (section **Organizations**); to orient yourself and see your role, go to My Profile.

### Next steps

* Dive deeper into how yours and your clients' are separated in [Your resources and those of your clients.](/docs-en/platform/accounts/concepts/resources-and-clients.md)
* Get to know your personal space within the dashboard in [My Profile.](/docs-en/platform/accounts/concepts/my-profile.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/the-panel.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.