> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/settings/workspace-settings/branding.md).
# Booking themes
Use a booking theme to give guest pages your workspace's look. Themes control layout, colors, logos, header media, and the visibility of host details. Workspace admins manage themes in **Settings → Branding**.
## Create and publish a theme
1. Open **Settings → Branding**. Choose **Customize** on the built-in default, **Add theme**, or an existing theme to edit.
2. Enter a **Theme name** and choose the **Default layout**, **Appearance preset**, and **Color mode**.
3. Set the accent color. Open **Backgrounds, text, and borders** for the rest of the palette.
4. Choose logos, optional header media, and whether to show the organization logo and host details.
5. Check desktop and mobile previews, including availability, booking details, and confirmation.
6. Use **Save draft** to keep working, or **Publish** when the appearance is ready for guests.
Review the theme in the preview before publishing it to guest pages.
| Layout | Booking experience |
| ----------- | ------------------------------------------------------------------------- |
| **Classic** | A date strip with available times. |
| **Focus** | Meeting details, a month calendar, and times in adjacent desktop columns. |
| **Studio** | Meeting details above the month calendar, with times alongside. |
Each layout supports **Clean**, **Angular**, **Frost**, **Soft**, **Offset**, and **Outline** appearance presets. Layouts adapt to mobile screens and embedded booking pages.
Choose **Light**, **Dark**, or **Follow visitor's device** for color mode. Device mode follows the guest's device, separately from your Distro app appearance. Review both palettes and logos when using it. Preview controls let you inspect a mode without changing the saved choice.
## Add logos and media
Upload an image or reuse one from the [Asset library](/settings/workspace-settings/asset-library.md). Supported images are PNG, JPG, WebP, and GIF, up to 5 MB each.
A theme can have separate light and dark logos. Leaving a logo on the organization default uses the matching library default, then the workspace logo from **General**, then the workspace name. Review both modes before publishing.
Header media can be an image or a supported HTTPS YouTube, Vimeo, or Loom link. To hide the logo, turn off **Show organization logo** in the theme.
## Choose where the theme is used
Use **Use as default** from a published theme's actions to make it the workspace default. The default card appears first in the gallery.
| Page | Appearance used |
| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Personal or group booking link | Its selected published theme, or the workspace default. |
| Single-use link or offered times from a personal or group link | The source link's appearance. |
| Form, Click, or public Outbound Router scheduling | The workspace default. |
| My booking page | The workspace default, with the profile's own page style and optional color-mode choice. |
Choose a link's theme in **Appearance & review** during creation, or in its editor later. Link owners and admins can choose an available theme for personal links. A group organizer can change the group's appearance; admins manage the group's full configuration. There is one appearance for the whole group.
Open **Theme usage** in the editor to review affected pages. Changing the workspace default affects pages that inherit it. Links explicitly using another available theme keep their selection.
## Understand drafts and live changes
**Save draft** keeps appearance changes private. **Publish** replaces the theme's current published appearance for pages using it on their next load. There is no theme version history or restore action. Duplicate a theme before experimenting if you want to keep an independent copy.
**Make unavailable** removes a theme from new selections. Links already using it temporarily follow the workspace default; publishing the theme again restores their selection. **Delete** removes it and makes those links inherit the default instead. Choose a replacement before removing the current default.
Changing defaults in the **Asset library** updates pages that use those images immediately. Those changes do not wait for a theme to be published.
Themes change presentation. Use [event types](/event-types/create-an-event-type.md) for duration and availability, and the link editor for booking questions and [CRM sync](/booking-links/crm-sync.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.distro.so/settings/workspace-settings/branding.md?ask=&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.
