> 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/productos/file-storage/details/customization.md).

# Customization

You can present the service under your own brand, so your clients access an environment with your identity and not a generic one.

It is one of the levers that sets you apart as a partner.

### What you can customize

| Item        | What it is                                     |
| ----------- | ---------------------------------------------- |
| Domain      | Your own access domain, configured via CNAME   |
| Logo        | Your logo in the interface                     |
| Colors      | The interface palette, aligned with your brand |
| Favicon     | The icon shown in the browser tab              |
| Certificate | The SSL certificate for the custom domain      |

### The certificate, under control

When you configure your domain via CNAME with its SSL certificate, the service notifies you before the certificate expires, so you can renew it on time and access is not interrupted.

> 📘 White-labeling is a sales argument
>
> Accessing "files.yourclient.com" with your logo, and not a generic domain, reinforces your position as a provider. 
>
> Customization is not about aesthetics: it is part of how the client perceives the service as yours.

### Where to go next

* How the end user accesses it: [Access.](/docs-en/productos/file-storage/details/access.md)
* The notifications, including the certificate expiration notice: [Subscription and fee.](/docs-en/productos/file-storage/details/subscription-and-quota.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/productos/file-storage/details/customization.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.