> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/publishing/b2b-network/for-resellers/setup-and-configuration/configure-your-branding.md).

# Configure your branding

When operators are sharing bookings with you, GUIBO automatically adapts all travel documents to match your brand identity. Here's how to setup your branding:

<table><thead><tr><th width="175.88427734375">Asset</th><th>How to change</th></tr></thead><tbody><tr><td>Logo</td><td><strong>Account →</strong> <strong>Account Settings → General Settings → Logo upload</strong></td></tr><tr><td>Main color</td><td><strong>Account →</strong> <strong>Account Settings → General Settings → Colors</strong></td></tr></tbody></table>

### &#x20;Here's what gets re-branded:

<table><thead><tr><th width="177.35931396484375">Channel</th><th>Re-branding</th></tr></thead><tbody><tr><td><strong>Trip Link</strong></td><td>Reseller logo + reseller brand colors</td></tr><tr><td><strong>Tour Guide App</strong></td><td>Reseller app linked on trip link. Reseller logo displayed for downloaded guidebooks. Operator indicated as trip organizer</td></tr><tr><td><strong>Roadbook PDF</strong></td><td>Reseller cover on first and last page</td></tr></tbody></table>

### Re-branded trip link example

* Your logo <sub>(see</sub> <sub></sub><sub>*Travel King*</sub> <sub></sub><sub>logo below)</sub>
* Your main color <sub>(see</sub> <sub></sub><sub>*Travel King*</sub> <sub></sub><sub>color below)</sub>
* None-branded GUIBO app or your white-label app <sub>(depends on reseller plan)</sub>

<figure><img src="/files/zr0ofD4vO0hV3uUdT3lH" alt="" width="375"><figcaption><p>Re-branded trip link for Travel King as a reseller</p></figcaption></figure>

### Re-branded tour guide app example

* Shows your logo <sub>(see</sub> <sub></sub><sub>*Travel King*</sub> <sub></sub><sub>logo below)</sub>
* Shows tour operator who is operating the trip <sub>(see</sub> <sub></sub><sub>*Hiking Holidays*</sub> <sub></sub><sub>as operator below)</sub>

<figure><img src="/files/RzlZkY4HnLyEALrAZ225" alt="" width="375"><figcaption><p>Re-branded app for Travel Kin as a reseller</p></figcaption></figure>

### Re-branded roadbook pdf example

* Applies the your logo to the roadbook pdf cover <sub>(see</sub> <sub></sub><sub>*Travel King*</sub> <sub></sub><sub>logo below)</sub>

<figure><img src="/files/KkwRQgNXpnVF71koitQP" alt="" width="375"><figcaption><p>Re-branded roadbook cover page</p></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://docs.guibo.travel/publishing/b2b-network/for-resellers/setup-and-configuration/configure-your-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.