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

# Branding

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/np15w34tek>" %}

Use **Branding** to control how your organization appears to guests across every touchpoint — the Guest Portal, outgoing emails, and email footers. Build one or more visual themes (branding profiles), then assign each to the properties you want.

### Overview

A **branding profile** is a reusable visual theme that bundles your company details, colors, logos, email signature, and social links into a single configuration. Once saved, the profile takes effect everywhere guests interact with you:

* **Guest Portal** — the web app guests open during their stay.
* **Main email communications** — system messages sent from Guestway on your behalf.
* **Email footers** — the signature block at the bottom of every outgoing message.

You can create as many profiles as you need and assign different profiles to different properties — useful if you operate multiple brands or sub-brands from one organization.

### Create a branding profile

Work down the page top to bottom. Each section maps to one part of the profile.

#### 1. General Information

Enter a **name** for the profile. Optionally add a **description** to help your team distinguish it from other profiles internally.

#### 2. Company Information

Fill in the details guests will see in their portal and email communications. All fields are required:

* Company name
* Full address
* Country
* Website URL
* Contact phone
* Contact email

#### 3. Brand Colors

Define the **primary (content)** and **secondary** colors used throughout the Guest Portal and email communications.

#### 4. Brand Logos

Upload your **main logo** for consistent branding across touchpoints. If you have a wide-format version, also upload a **horizontal logo** for specific placements where the main logo doesn't fit cleanly.

#### 5. Footer Information

Enter the **signature** that will appear at the bottom of every email sent from the platform.

#### 6. Social Media Links *(optional)*

Add links to your social media accounts. These links will be accessible to guests across various touchpoints.

#### 7. Assign properties

At the bottom of the page, choose which properties should use this branding profile.

### Tips

#### 💡 Academy Tip

> **One brand per profile.** If you manage properties under multiple names or sub-brands, create a separate branding profile for each one and assign it at the property level. That way every guest sees the right colors, logo, and contact details — no matter which listing they booked.

***

### Related pages

* [Guest Journey](https://docs.guestway.io/settings/organization-settings/guest-journey) — branding will be displayed throughout the guest journey.
* [Email Domains](https://docs.guestway.io/settings/organization-settings/email-domains) — set up your domain so your emails can be branded as well.
* [Guest Portal](https://docs.guestway.io/guestway-platform/guest-portal) — the guest-facing web app where your branding profile is displayed.


---

# 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.guestway.io/settings/organization-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.