> 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'

Why several Home screens separate what belongs to your organization from what belongs to your customers in two tabs.

Plenit is designed for the channel: you, as a partner, not only use the platform 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'** — everything you deploy and manage for the **your clients' organizations**, the companies you serve.

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

### How it is reflected in the dashboard

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

| Screen (on Home) | Your 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 gathers what belongs to your organization and the other, what corresponds to your clients.

![](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-faa9258b036ff1f916ad416ac47917ab17a8d96c%2Fdiagram-your-resources-and-clients.png?alt=media)

### When to use each view

* Use the tabs **of 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 thing is **to enter their organization** from the Organization level in the menu: there you see their own information directly, without tabs.

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

### Next steps

* Complete the concepts with [My Profile, ](https://docs.plenit.com/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.](https://docs.plenit.com/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 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/resources-and-clients.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.
