> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/getting-started/onboarding-to-revelator/white-label/adding-your-brand.md).

# Adding your brand

## Branding images & logos

Branding of account interface and emails that are seen by rights holders and users with company images and logos.- Upload branded images to \*Identity & branding\* section accessible from the \*Account\* menu item.

## Identity <a href="#color-scheme-and-font" id="color-scheme-and-font"></a>

Options to modify:**PrimaryColor**---The default Revelator primary color is \*Primary blue\*. Buttons across the platform have the primary color as the background color.**DarkColor**---The default Revelator dark color is \*Dark blue\*. Dark color appears often as a result of user actions, such as when hovering over buttons the background color changes from the primary color to the dark color.- Provide the hex code of any color to be used. For example, \*#4611ea\*.- The same color can be used for PrimaryColor and DarkColor


---

# 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.revelator.com/pro/getting-started/onboarding-to-revelator/white-label/adding-your-brand.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.
