> 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/detalles/customization.md).

# Customization

The fields of the two brand surfaces and the email settings.

The section **Customization** defines the brand with which the service is presented.

It has two surfaces that you customize separately, the **User portal** (what the end customer uses) and the **Administration panel**, plus the email configuration.

The reason for all this is in [The end customer and the partner's brand](https://claude.ai/chat/el-cliente-final-y-la-marca).

### User portal and administration panel

Both surfaces are configured with the same elements:

| Item                        | What it is                                                                                                                                                                                                   |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Portal name and Description | The portal name and description.                                                                                                                                                                             |
| Visual identity             | Background image (with View Gallery), Logo, Favicon and Colors (primary color, in format `#hex`).                                                                                                            |
| Own domain                  | A URL field for your address and, below it, the CNAME block with the HOST · TYPE · VALUE table. You need to create that CNAME record for the new URL to work. A Reset button returns to the default address. |
| Certificate                 | You choose between Generate Let's Encrypt certificate or Upload my own certificate.                                                                                                                          |

You save each block with **Save** (or discard with **Cancel**).

### Email

Defines how and what appearance emails to the end customer have. You can click **Send test email** to check it.

**Sending mode:**

* Use the established email template.
* Sending from a specific email account (through our mail servers). When you choose it, you specify the sending email and display name.

**Appearance of sent emails:**

* Use the established email template.
* Custom: you define the organization name, logo, colors (Primary), and email signature.

> #### ❗️ **Enable SPF and DKIM**
>
> For emails to arrive correctly with your own account, SPF and DKIM must be enabled.
>
> After completing and submitting the form, you will receive instructions to do so.

### Next steps

* Understand the brand model in [The end customer and the partner brand.](https://docs.plenit.com/docs-en/platform/organizations/concepts/end-client-and-brand.md)
* Do it step by step in[ How to customize the user portal and the administration panel.](https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-customize-the-user-portal-and-admin-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/detalles/customization.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.
