> 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/resources-and-clients.md).

# Your Resources and Your Customers'

Plenit is designed for the channel: you, as a partner, use the platform not only for your own company, but above all to **serve your clients**.

That means that in your day-to-day work you manage two layers at once, and the dashboard keeps them separate so they don't get mixed up.

### The two layers

* **Yours** — the subscriptions, users, and services of **your own organization**.
* **Your clients' side** — everything you deploy and manage for the **organizations of your clients**, the companies you serve.

Each client is, within Plenit, one **organization** more. You access them with the same account, but their resources are not yours: they belong to that client's organization.

### How this appears in the dashboard

To avoid confusing one layer with the other, several screens of **Home** separate them into **two tabs**:

| Screen (on Home) | Your side tab    | Clients tab          |
| ---------------- | ---------------- | -------------------- |
| Subscriptions    | My subscriptions | Client subscriptions |
| Users            | My users         | Client users         |
| Events           | My events        | Customer events      |

The logic is always the same: one tab brings together what belongs to your organization and the other, what corresponds to your clients.

![](/files/551091baa2dee807bc12afa4613acf899fdaecb5)

### When to use each view

* Use the tabs **clients'** when you want the big picture of everything you manage for third parties: how many subscriptions they have in total, what users there are, or what has happened.
* If what you want is to work in depth on a specific client, the most direct way is **to enter their organization** from the Organization level in the menu: there you directly see their side, without tabs.

> #### 📘 Yours and your clients', always distinguished
>
> This separation is consistent across the platform.&#x20;
>
> Wherever you see the two tabs, the first is your organization and the second, the set of your clients.&#x20;
>
> That way you avoid accidentally touching a client's subscription thinking it's yours, or vice versa.

### Next steps

* Complete the concepts with [My Profile, ](/docs-en/platform/accounts/concepts/my-profile.md)your personal identity on the platform.
* Put subscription and user management into practice in the [How-to.](/docs-en/platform/accounts/how-to.md)

<br>


---

# 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/resources-and-clients.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.
