> 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/how-to/how-to-customize-the-user-portal-and-admin-panel.md).

# How to Customize the User Portal and the Admin Panel

Apply your brand to the two surfaces the end customer sees and configure email with your identity.

In Plenit, you work in **white label**: the end customer sees **your brand**, not ours.

This guide takes you through the two surfaces you customize, the **User Portal** (what the customer uses) and the **Admin Panel**, and through the configuration of the **email** you use to communicate with them.

The reason for the model lies in [The end customer and the partner's brand.](https://docs.plenit.com/docs-en/platform/organizations/concepts/end-client-and-brand.md)

> #### 📘 What will you achieve?
>
> The portal and customer panel with your visual identity and your domain, and emails sent with your brand. From the customer's point of view, the service is yours.<br>

### Before you begin

You need to be logged in and have customization permission for the organization. Have your logo, your favicon, your main color, and, if you are going to use your own domain, access to that domain's DNS management ready.

### 1. Open Customization

Enter the organization and open **Customization**. You will see the two blocks you will configure, **User Portal** and **Admin Panel**, and the section **Email**.

![Customization section of an organization](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-d8314b215894a396ade1879683306f44db350b2b%2FCAPTURA%201%20%C2%B7%20Organizaci%C3%B3n%20_%20Personalizaci%C3%B3n%20%C2%B7%20resaltar%20los%20bloques%20Portal%20de%20usuario%2C%20Panel%20de%20administraci%C3%B3n%20y%20Correo%20electr%C3%B3nico.jpg?alt=media)

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-01570c1cb8d7530fa73024277ab0753614c3bb93%2FCAPTURA%201bis%20%C2%B7%20Organizaci%C3%B3n%20_%20Personalizaci%C3%B3n%20%C2%B7%20resaltar%20los%20bloques%20Portal%20de%20usuario%2C%20Panel%20de%20administraci%C3%B3n%20y%20Correo%20electr%C3%B3nico.jpg?alt=media" alt=""><figcaption><p>Customization section of an organization</p></figcaption></figure>

### 2. Customize the User Portal

Expand the block **User Portal** and configure:

* **Portal name** and **Description**.
* **Visual identity** — **Background image** (with **View Gallery**), **Logo**, **Favicon** and the color **Main** (in `#hex`).
* **Custom domain** — enter your **URL** in its field. For it to work, create the record **CNAME** indicated by the panel (table **HOST · TYPE · VALUE**) in your domain's DNS management. The button **Reset** returns to the default address.
* **Certificate** — choose **Generate Let's Encrypt certificate** or **Upload my own certificate**.

Click **Save** to apply the block, or **Cancel** to discard.

![User Portal customization](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-5235deab676ab7452e104d1fa31badacc541e74b%2FCAPTURA%202%20%C2%B7%20Organizaci%C3%B3n%20_%20Personalizaci%C3%B3n%20_%20Portal%20de%20usuario%20%C2%B7%20resaltar%20identidad%20visual%20URL%20CNAME%20y%20certificado.jpg?alt=media)

> #### 🚧 Use your own values
>
> The panel still shows some inherited example name and domain. Ignore them and fill in your brand and your domain.

### 3. Customize the Admin Panel

Expand the block **Admin Panel** and configure it with the same elements from the previous step: name, description, visual identity, domain with its CNAME, and certificate. It is the surface from which you manage; the portal is the one the customer uses. Save when finished.

### 4. Configure the email

In **Email** you define how and with what appearance emails are sent to the end customer.

* **Sending mode**:
  * **Use the established email template**.
  * **Send from a specific email account**, through our mail servers. When you choose it, you specify the **Sending email** and the **Display name**.
* **Appearance of sent emails**:
  * **Use the established email template**.
  * **Custom** — you define the **Organization name**, the **Logo**, the color **Main** and the **Email signature**.

![Email settings in Customization](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-8323cf0d101e572d13ba725e5d79b37f523937a6%2FCAPTURA%203%20%C2%B7%20Organizaci%C3%B3n%20_%20Personalizaci%C3%B3n%20_%20Correo%20electr%C3%B3nico%20%C2%B7%20resaltar%20Modo%20de%20env%C3%ADo%20y%20Aspecto%20de%20los%20correos.jpg?alt=media)

> #### ❗️ Activate SPF and DKIM
>
> For emails to be delivered correctly from your own account, you need to activate **SPF** and **DKIM**. When you complete and submit the form, we will give you instructions to do so.

Before confirming it, click **Send test email** and check that it arrives with your brand and with the appearance you defined.

### Conclusion

With customization in place, the end customer sees your portal, accesses it through your domain, and receives your emails.

You have configured the two surfaces and the email, so the entire experience is presented with your brand and Plenit remains underneath as the platform that makes it possible.

### Next steps

* Review each field in [Customization.](https://docs.plenit.com/docs-en/platform/organizations/detalles/customization.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/how-to/how-to-customize-the-user-portal-and-admin-panel.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.
