> 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/organizations/concepts/end-client-and-brand.md).

# The End Customer and the Partner Brand

Each organization is an end customer that sees your brand, not Plenit's, on its two surfaces.

Each organization is an end customer: the company you serve and for which you deploy and manage everything in Plenit.

And a central idea of the model: that end customer sees your brand, the partner's, not Plenit’s.

> #### 📘 **One organization, one end customer**
>
> The relationship is one to one: one organization corresponds to a single client company.
>
> The recommended approach is to keep one organization for each customer, without grouping several into the same one.

### Two surfaces, one brand

Plenit gives you two surfaces, and you can customize both with your brand:

* **The admin panel** — where you, as the partner, manage the organization and its services.
* **The user portal** — what the end customer uses in their day-to-day.

In both, you define the brand under which the service is presented. To the end customer, the service is yours: Plenit sits underneath as the platform that makes it possible.

### What you can customize

Broadly speaking, for each surface you define:

* **Visual identity** — portal name, logo, favicon, and primary color.
* **Own domain** — a custom URL, activated with a CNAME record, and a certificate (generated with Let's Encrypt or by uploading your own).
* **Email** — emails to the end customer can be sent with your template and from your own account, delivered through our mail servers. To ensure they arrive correctly, SPF and DKIM must be configured.

How to do it, field by field, is in [Customization.](https://docs.plenit.com/docs-en/platform/organizations/detalles/customization.md)

### Why it matters

For the end customer, the experience is that of a partner's service: your brand in the portal, your domain, and your emails. This strengthens your brand and your relationship with the customer, which is exactly the point of the model.

### Next steps

* Learn about the panel sections in [The organization panel.](https://docs.plenit.com/docs-en/platform/organizations/concepts/the-organization-panel.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 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/organizations/concepts/end-client-and-brand.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.
