> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/xcover-journeys/integration/branding-and-theming.md).

# Branding & Theming

White-label configuration including logos, colors, fonts, and how to request changes.

XCover Journeys is white-labelled by default. Cover Genius configures your branding during onboarding — no partner code is required.

### What Cover Genius configures

* **Logo** — your brand logo displayed in the journey header
* **Primary color** — used for buttons, links, and interactive elements
* **Secondary color** — used for accents and supporting elements
* **Fonts** — your brand typefaces for headings and body text
* **Favicon** — your icon shown in the browser tab

### Requesting changes

To update your branding, contact your Cover Genius integration manager with the following assets:

* **Logo** — SVG or PNG (transparent background)
* **Colors** — hex codes (e.g., `#1A1A1A`)
* **Fonts** — web font files (WOFF2) or a link to the hosted font
* **Favicon** — ICO or PNG, 32x32px

{% hint style="info" %}
Changes are applied in a new deployment — they do not require a release on your side.
{% endhint %}

### Managed by Cover Genius

The following elements are part of the journey implementation and are not customizable per partner:

* Page layout and step order
* Component structure and form fields
* Payment form appearance
* Journey navigation behavior


---

# 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://partner-docs.covergenius.com/xcover-journeys/integration/branding-and-theming.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.