> For the complete documentation index, see [llms.txt](https://help.solar-archive.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solar-archive.com/docs/admin-ui/settings/branding-settings.md).

# Branding Settings

The Branding section in the Settings menu allows Distributors, Partners, and Tenants to customize the look and feel of the platform to align with their corporate identity. Branding settings include the ability to upload custom logos and configure a custom colour scheme. If a specific tier does not set up branding they will inherit the branding from the tier above.

### Logos

· Small Logo: This is a square SVG image used in areas where a compact logo is needed.\
· Large Logo: A wider 500×150 SVG image, typically used in login pages or other areas where a larger brand presence is required.

### Colour Scheme

Users can define their branding colours by setting HEX values for three main UI elements:

· Primary Colour: Used for buttons and action elements.\
· Secondary Colour: Used for the navigation bar.\
· Tertiary Colour: Used for link text.

<figure><img src="/files/esHr65tkAX5XlYpEhwxQ" alt=""><figcaption></figcaption></figure>


---

# 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://help.solar-archive.com/docs/admin-ui/settings/branding-settings.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.