> 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 Administration Panel
In Plenit you work in **white-label**: the end customer sees **your brand**, not ours.
This guide walks you through the two surfaces you customize, the **User portal** (what the customer uses) and the **Administration panel**, and through the configuration of the **email** with which you address them.
The reason for the model lies in [The end customer and the partner brand.](/docs-en/platform/organizations/concepts/end-client-and-brand.md)
> #### 📘 What will you achieve?
>
> The portal and the 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.
### Before you start
You need to be logged in and have customization permission over the organization. Have your logo, favicon, main color, and, if you are going to use your own domain, access to the DNS management for that domain ready.
### 1. Open Customization
Enter the organization and open **Customization**. You will see the two blocks you are going to configure, **User portal** and **Administration panel**, and the section for **Email**.
{/\* 📸 CAPTURE 1 · Organization > Customization · highlight the User Portal, Administration Panel and Email blocks \*/}
### 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 format `#hex`).
* **Own domain** — enter your **URL** in its field. For it to work, create the record **CNAME** shown in 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.
{/\* 📸 CAPTURE 2 · Organization > Customization > User Portal · highlight visual identity, URL, CNAME and certificate \*/}
> #### 🚧 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 Administration Panel
Expand the block **Administration 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 you're done.
### 4. Configure email
In **Email** defines 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. By choosing 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**.
{/\* 📸 CAPTURE 3 · Organization > Customization > Email · highlight Sending mode and Appearance of emails \*/}
> #### ❗️ Enable SPF and DKIM
>
> For emails to arrive correctly from your own account, you need to enable **SPF** and **DKIM**. When you complete and submit the form, we'll give you instructions on how to do it.
Before approving it, click **Send test email** and check that it arrives with your brand and with the appearance you have defined.
### Conclusion
With customization ready, the end customer sees your portal, accesses it through your domain, and receives your emails.
You have configured the two surfaces and 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.](/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 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/how-to/how-to-customize-the-user-portal-and-admin-panel.md?ask=&goal=
```
`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.