> 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/account-settings/branding.md).

# Branding

**Description**

The Branding settings allow you to customize the visual identity of your platform, including favicons, logos, and statement branding.

**Steps**

1. Navigate to **Account > Branding** in the sidebar.
2. Configure the following branding elements:
   * **Favicon:** Upload a small square image (16x16 or 32x32 pixels) in SVG, ICO, or PNG format.
   * **Account Logotype (Light/Dark):** Upload two versions (dark and light) of your horizontal logotype for optimal visibility on different backgrounds.
   * **Statement Logo:** Upload a logo to be used on financial statements, preferably in SVG, PNG, or JPG format.
3. Click **Save** to apply changes.


---

# 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.revelator.com/pro/getting-started/account-settings/branding.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.