> 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/booking-themes.md).

# Create and publish a booking theme

A booking theme controls the appearance of public booking pages. Admins manage themes from **Settings → Branding**.

## Create a theme

Choose an available starter theme or create a theme, then edit its colors, fonts, logos, layout and light/dark appearance. Use the preview while making changes.

Save the draft when you want to keep working. Draft changes are private and do not update booking pages.

## Publish the appearance

1. Preview the theme with representative meeting details.
2. Review **Theme usage** to see where it will apply.
3. Select **Publish**.
4. Open a link that selects the theme and refresh it.

Published pages use the theme on their next load. Set a published available theme as the organization default when inheriting links should use it.

A link that explicitly chooses another published theme keeps that selection. Changing the default does not override every link's explicit choice.

## Make a theme unavailable

Review its usage before making it unavailable. Pages selecting an unavailable theme can fall back to the organization default. Publishing it again restores availability for those selections.

A theme affects appearance. It does not change queue membership, scheduling hours, CRM ownership or event duration.

See [Workspace branding](/settings/branding.md) and [Booking links](/scheduling/booking-links.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/booking-themes.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.