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

# Workspace branding

Open **Settings → Branding** as an admin to set the workspace's visual identity.

## Update the brand kit

Review the logo, browser tab icon, brand colors and font settings in **Brand kit**. Upload the appropriate assets and save your changes.

Use a recognizable logo that stays legible at small sizes. Check its appearance against both light and dark backgrounds when your booking theme uses both modes.

## Set the email appearance

Use **Email look** for colors, workspace name/logo header and footer choices. Preview the email at Desktop and Mobile widths before saving. A preview does not send a message.

Meeting templates can use Styled or Plain text appearance. Their wording and recipients are configured separately from workspace branding.

## Theme booking pages

Open the booking-theme gallery for colors, layouts, media and light/dark appearance. Theme drafts remain private until published. See [Booking themes](/settings/booking-themes.md).

Changing the brand kit is not the same as publishing a draft booking theme. Preview the actual link your team shares and check which theme it selects or inherits.

## Review the result

Check a public booking page, an email preview and any workflow scheduler your team uses. Different surfaces may use their configured theme rather than immediately adopting every draft change.

See [Event types](/scheduling/event-types.md) and [Email templates](/scheduling/email-templates.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/settings/branding.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 `build a script that syncs our docs to a CMS` 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.