> 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/account/language-and-appearance.md).

# Language and appearance

Read the dCal dashboard in English or Spanish and switch it between light and dark. Learn where each choice is saved, what it does not change (your booking pages and the emails your guests receive), a

You can read dCal in English or Spanish and switch the dashboard between light and dark. Both choices are yours alone: they change what you see, not what your guests see.

***

## Change the dashboard language

**Step 1:** Go to **Settings** > **General** and scroll to the bottom. Under **Language**, pick **English** or **Español**. The whole dashboard switches right away.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-4a37328551ab2f5a212e9061cfae1f83aa1ba0e4%2Fdcal-language-and-appearance-01-language-selector.png?alt=media" alt="The Language selector open, with English selected and boxed, showing the English and Español options"><figcaption><p>Each language is named in its own words, so you can find yours whichever one is showing.</p></figcaption></figure>

* This browser remembers your choice. Another browser or computer keeps its own, so pick it again there.
* Until you pick one, the dashboard follows your browser: Spanish if your browser prefers Spanish to English, English otherwise.

### What the dashboard language does not change

|                           | How its language is chosen                                                                                                                                                                                                                                                                                                                                                  |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Your booking pages**    | Each visitor sees your pages in English or Spanish, following their own browser. To choose for them, add `?lang=es` or `?lang=en` to any public link, for example `book.dcal.ai/k7m2xq/jdoe/intro-call?lang=es`. Profile pages, events, team pages, team events and one-off links all accept it. See [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md). |
| **Emails to your guests** | A guest who books on your page gets their emails in the language the page showed them. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md) for the other cases.                                                                                                                                                                           |

***

## Switch between light and dark

**Step 2:** At the bottom of the left menu, just above your profile button, click the theme switch. Its icon shows the theme you are in (a moon for dark, a sun for light), and its tooltip names the other one: **Switch to light theme** or **Switch to dark theme**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-13a6d13b7be05fcaf2e7aacb57cd79c3e484cb04%2Fdcal-dashboard-tour-05-theme-toggle.png?alt=media" alt="The bottom of the left menu with the theme switch boxed, showing the moon of the dark theme, above Jane Doe&#x27;s profile button"><figcaption><p>One click flips the dashboard between dark and light.</p></figcaption></figure>

The dashboard starts dark. This device remembers your choice.

> **💡 Tip:** Light or dark here never changes your public booking page. Your page has its own **Theme**, light or dark, in **Settings** > **Booking Page**. See [Colors, fonts and presets](https://docs.dapta.ai/dcal/design/look-and-presets.md).

***

## Sign out

**Sign out** is not next to the theme switch. Click your profile button at the bottom of the left menu (your initial, name and email): its menu holds **View public page** and **Sign out**. See [Sign in and set up](https://docs.dapta.ai/dcal/getting-started/sign-in.md).

## Related

* [Your name and time zone](https://docs.dapta.ai/dcal/account/general-settings.md): the rest of the **General** tab.
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md): the booking page from your guest's side.
* [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md): languages and time zones in emails.
* [Colors, fonts and presets](https://docs.dapta.ai/dcal/design/look-and-presets.md): your booking page's own theme.


---

# 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/account/language-and-appearance.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.
