> For the complete documentation index, see [llms.txt](https://support.holidayhero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.holidayhero.com/the-basics/brands/appearance.md).

# Appearance

A strong brand is the foundation of a memorable guest experience. With your own colors, imagery, and custom domain, your brand identity is unique. HolidayHero seamlessly integrates all these elements.

***

### What is appearance? <a href="#appearance" id="appearance"></a>

The **Appearance** tab on a [brand](/the-basics/brands.md) controls what your guests actually see: the logo at the top of the app and in every email, the background image behind the web app, whether guests get the web app or the native app, and the colours the whole guest experience is painted in.

Every listing is served through a brand, so changing a brand's appearance changes the look of the guest app for every reservation on that brand.

#### Logo <a href="#logo" id="logo"></a>

Three images make up the visual identity of the brand. Each one is optional, but the more you fill in the more the guest app feels like yours.

| Image                | Where it is used                                                                               |
| -------------------- | ---------------------------------------------------------------------------------------------- |
| **Logo**             | The header of the guest app, and all emails.                                                   |
| **Square Logo**      | Push notifications, web app bookmarks and the web app icon. Use a genuinely square image here. |
| **Background Image** | The background of the web version of the guest app.                                            |

Click **Select …** under an image to upload a new one.

#### App Access <a href="#app-access" id="app-access"></a>

**App Access** decides which apps your guests can use for this brand:

| Option                 | Meaning                                                  |
| ---------------------- | -------------------------------------------------------- |
| **Both; Web & Native** | Guests can use the browser-based app and the native app. |
| **Web Only**           | Guests only get the browser-based app.                   |
| **Native Only**        | Guests only get the native app.                          |

#### Colors <a href="#colors" id="colors"></a>

The guest app is built from **twelve** colours. That is a lot to pick by hand, so you have two ways to work.

**Start from a palette**

At the top of the **Colors** section you'll find a grid of **palettes** — ready-made colour sets that are designed to work together. Each card shows a small preview of the guest app in that palette: the background, a card, and the accent colours. They come in two groups:

| Group       | What it looks like                                                                                                                        |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Classic** | Confident, high-contrast sets — dark themes such as **Midnight** and **Charcoal**, and clean light ones such as **Coastal** and **Mono**. |
| **Pastel**  | Soft, light sets such as **Blossom**, **Mint** and **Sky**. Gentle and welcoming rather than bold.                                        |

<figure><img src="https://3950018645-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWWiwAsWOs8WeAQ2KJS3%2Fuploads%2FDfBqTHduBa1svuX4QnMM%2Fbrand-palettes.webp?alt=media&amp;token=ea5713d8-bd75-4c4f-8ad3-751263f1560d" alt=""><figcaption><p>The palettes on a brand's Appearance tab</p></figcaption></figure>

To use one:

1. Open the brand and go to the **Appearance** tab.
2. Scroll to **Colors**. If the palettes aren't showing, click **Choose a palette** on the right.
3. Click the palette you like. A tick appears on it and every colour is filled in behind the scenes.
4. Click **Save**.

{% hint style="info" %}
&#x20;If the brand already uses its own colours, the palettes start hidden and the colour fields are shown instead — no point in a wall of palettes for a brand that isn't using one. **Choose a palette** brings them back, and **Hide palettes** puts them away again.&#x20;
{% endhint %}

{% hint style="info" %}
Clicking a palette only fills in the fields — nothing is stored until you press **Save**. Pick a different palette, or leave the page, and nothing changes.&#x20;
{% endhint %}

A palette is a *starting point*, not a mode. Once you've saved, the brand simply has twelve colours like any other brand — the tick on a palette card only means your current colours happen to still match that set exactly. As soon as you change one colour, the tick disappears. That is normal.

**Set the colours yourself**

The twelve individual colour fields are tucked away while a palette is selected. Click the **Custom** card — the dashed one at the bottom, under **Your own colours** — to reveal them. The palettes fold away at the same time, so you're left with just your colours.

**Custom** changes nothing on its own. That means you can pick the palette that comes closest to your identity first, then click **Custom** and adjust the handful of colours you want to differ.

Each colour has a swatch you can click to open a colour picker, and a text field where you can paste a hex code such as `#0c111e` — handy when you're matching an existing brand guide.

{% hint style="info" %}
Once you've changed a colour by hand, clicking a palette would overwrite all twelve of them — so you'll be asked to confirm first. Cancel and your own colours stay exactly as they were.&#x20;
{% endhint %}

| Colour                       | What it paints                                                           |
| ---------------------------- | ------------------------------------------------------------------------ |
| **Base**                     | The background of the guest app.                                         |
| **On Base**                  | Text and icons drawn on the background — and on cards.                   |
| **Card Even** / **Card Odd** | The backgrounds of alternating cards, sitting on top of the base colour. |
| **Primary**                  | The main accent: buttons, active states and links.                       |
| **On Primary**               | Text drawn on top of the primary colour.                                 |
| **Secondary**                | The supporting accent.                                                   |
| **On Secondary**             | Text drawn on top of the secondary colour.                               |
| **Success**                  | Positive states, such as a confirmed or paid reservation.                |
| **On Success**               | Text drawn on top of the success colour.                                 |
| **Error**                    | Negative states, such as a failed payment.                               |
| **On Error**                 | Text drawn on top of the error colour.                                   |

{% hint style="info" %}
The **On …** colours are what makes a brand readable. Whatever you pick for **Primary**, the **On Primary** colour has to stand out clearly against it — otherwise the text on your buttons disappears. The same goes for every other pair. Cards use **On Base** for their text, so keep **Card Even** and **Card Odd** close to **Base** in lightness.
{% endhint %}

**Reset Colors** (next to the section title) puts all twelve colours back to the HolidayHero defaults. You'll be asked to confirm, and — like the palettes — nothing is stored until you press **Save**.

***

#### Frequently Asked Questions <a href="#frequently-asked-questions" id="frequently-asked-questions"></a>

<details>

<summary>Do I have to use a palette?</summary>

No. Palettes exist to save you time if you don't have a designer. If you have brand colours of your own, set the twelve colours by hand — or pick the palette closest to your identity and then adjust it.

</details>

<details>

<summary>I picked a palette but nothing changed for my guests.</summary>

Picking a palette only fills in the form. Scroll to the bottom of the page and click **Save**.

</details>

<details>

<summary>Where did the colour fields go?</summary>

They're hidden while a palette is selected, because the palette already sets all twelve. Click the **Custom** card under **Your own colours** to bring them back.

</details>

<details>

<summary>Where did the palettes go?</summary>

They fold away as soon as you switch to your own colours, so the section stays short. Click **Choose a palette**, at the right of the **Colors** section, to show them again.

</details>

<details>

<summary>Why did the tick disappear from the palette I chose?</summary>

The tick marks the palette your colours *currently* match exactly. Change a single colour and your brand is no longer that palette, so the tick goes away. Your colours are still saved — this is only a label.

</details>

<details>

<summary>Can I add my own palette to the list?</summary>

Not yourself, no. The palettes are curated by HolidayHero. If you'd like one added, get in touch with support and tell us the colours you have in mind.

</details>

<details>

<summary>Where do I change the brand's name, domain or legal links?</summary>

On the **General** tab — see [Brands](/the-basics/brands.md).

</details>

***

## Agent Instructions: Querying This Documentation <a href="#agent-instructions-querying-this-documentation" id="agent-instructions-querying-this-documentation"></a>

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:

```
GET https://support.holidayhero.com/the-basics/workspace/brands/appearance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language. 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.
