> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/design/brand-kit.md).

# Brand kit

Set one look for your whole dCal workspace with the brand kit: logo, accent, background, font and shapes. Team pages wear it right away, and each person can apply it to their own page and revert it on

The brand kit is one look for your workspace: a logo, an accent color, a background and four shape settings. Team pages wear it automatically, and each person can copy it onto their own booking page with one click.

Everyone in the workspace can open the brand kit. Only owners and admins can change it. Everyone else sees the settings locked, with the note **Only an admin or owner can change the brand kit.**

***

**Step 1:** Click **Settings** in the left menu, then the **Booking Page** tab, then the **Brand kit** tab. Under the tabs, a chip shows **Not set yet** or **Saved**, with the date of the last update.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-6c14d9cf966d3a850e4db71a81a09877aa1e9758%2Fdcal-brand-kit-01-brand-kit-tab.png?alt=media" alt="The Brand kit tab with the Not set yet chip boxed, the Logo, Accent, Canvas, Font, Corners, Buttons and Card style rows on the left, each list on Keep each page&#x27;s own, the Save kit button and the Preview of a sample booking page on the right"><figcaption><p>The <strong>Brand kit</strong> tab, before anything is set.</p></figcaption></figure>

***

**Step 2:** Fill in the parts you want to standardize. Anything left on **Keep each page's own** is not part of the kit, and never changes anyone's page.

| Setting        | Options                                                                                                                | What it does                                                                                                                           |
| -------------- | ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Logo**       | **Upload image**, **…or paste an image URL**, **Clear**                                                                | Shown at the top of the event panel and over the profile cover, exactly as uploaded. Use a version that reads well on your background. |
| **Accent**     | Seven colors (a near-black first, then the six studio colors), a color box for any color, and **Keep each page's own** | Colors buttons, the selected day and time, and links.                                                                                  |
| **Canvas**     | **Keep each page's own**, **Light**, **Dark**                                                                          | The background the page sits on.                                                                                                       |
| **Font**       | **Keep each page's own**, Sans, Rounded, Serif                                                                         | The typeface.                                                                                                                          |
| **Corners**    | **Keep each page's own**, Sharp, Soft, Round                                                                           | How rounded cards are, and the shape of the initials shown when there is no photo.                                                     |
| **Buttons**    | **Keep each page's own**, Rounded, Pill, Square                                                                        | The shape of buttons and time buttons.                                                                                                 |
| **Card style** | **Keep each page's own**, Outline, Elevated, Filled                                                                    | Border, shadow or tint on cards.                                                                                                       |

The template, density and the way times are listed are not part of the kit: they stay each page's own. The options mean the same as in the studio; see [Colors, fonts and presets](https://docs.dapta.ai/dcal/design/look-and-presets.md).

The **Preview** on the right shows a booking page wearing only the kit, which is exactly how your team pages look. Switch between **Booking flow** and **Profile**, and between **desktop** and **mobile**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-2b1864a6b02eb5a0ff5b30fc6f511e67719541c2%2Fdcal-brand-kit-02-kit-filled.png?alt=media" alt="The brand kit with an Acme Corp logo uploaded and an orange accent picked, the Preview showing the logo above the event panel in orange, and the Save kit button boxed"><figcaption><p>A logo and an accent set. The preview shows the result on a booking page.</p></figcaption></figure>

***

**Step 3:** Click **Save kit**. You see **Brand kit saved.** Team pages change right away. Each person's own page keeps its look until they apply the kit.

***

**Step 4:** Apply the kit to your own page. Go to the **Your page** tab and click **Apply brand kit** at the top of the **Appearance** section. It applies right away, with no **Save** needed, and you see **Brand kit applied to your page.**

* The button only shows once the workspace has a kit.
* It is disabled while you have unsaved changes in the studio. Click **Save** or **Reset** first.
* Only what the kit sets is copied. A kit with just a logo and an accent leaves your template, fonts and other settings alone.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-d2e070fd92bc0992da6dead6c61d0777ab06b245%2Fdcal-brand-kit-03-apply-brand-kit.png?alt=media" alt="The Appearance section of the studio with the Apply brand kit button boxed and its hint below"><figcaption><p><strong>Apply brand kit</strong> copies the workspace look onto your page.</p></figcaption></figure>

> **⚠️ Note:** Each person applies the kit to their own page. An admin cannot apply it to a teammate's page, so ask each host to open their studio and click **Apply brand kit**.

***

**Step 5 (optional):** Revert. After you apply the kit, the top of **Appearance** shows **Brand kit applied on** with the date, and a **Revert** button. **Revert** brings back the look your page had before you first applied a look, including removing the kit's logo. It works once. Your bio, event order and what your link opens stay as they are.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-79178b9e9ae71af96dd9fe68cc26f9f01c75544d%2Fdcal-brand-kit-04-kit-applied-revert.png?alt=media" alt="The Appearance section with the line Brand kit applied on Oct 19, 2026. and the Revert button boxed"><figcaption><p>Applied a kit by mistake? <strong>Revert</strong> puts your previous look back.</p></figcaption></figure>

***

## Where the kit applies

| Place                                     | Uses the kit?                                                                                                                                                                       |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Team pages**                            | Yes, always the current kit. Saving the kit changes every team page right away.                                                                                                     |
| **Your profile and personal event pages** | Only after you click **Apply brand kit**. It is a copy: later kit changes do not reach your page until you apply it again.                                                          |
| **Emails**                                | No. Emails to guests and hosts use dCal's standard layout.                                                                                                                          |
| **Link previews**                         | No. Preview cards for your profile and events use your own page's look. Team link previews do not use the kit either.                                                               |
| **Website embeds**                        | The embedded page shows the page's own look. An embed code can set its own accent and style for that embed. See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md). |

If you apply the kit again before reverting, **Revert** still takes you back to your own look from before the first apply.

## Related

* [Colors, fonts and presets](https://docs.dapta.ai/dcal/design/look-and-presets.md): what each setting changes.
* [Profile and layout](https://docs.dapta.ai/dcal/design/booking-page-studio.md): your own page in the studio.
* [Your team page](https://docs.dapta.ai/dcal/teams/team-page.md): team pages wear the kit.
* [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md): who is an owner or admin.


---

# 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://docs.dapta.ai/dcal/design/brand-kit.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 `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.
