> 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 a final customer: the company you provide service to and for which you deploy and manage everything in Plenit. 

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

> #### 📘 **One organization, one final 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 Administration Panel** — where you, as partner, manage the organization and its services.
* **The User Portal** — what the end customer uses in their day-to-day.

On both, you define the brand with which the service is presented. From the end customer's point of view, 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 main 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, sent 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.](/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 reinforces your brand and your relationship with the customer, which is exactly the point of the model.

### Next steps

* Learn about the sections of the panel in [The organization panel.](/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 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/organizations/concepts/end-client-and-brand.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.