> 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/general-settings.md).

# Your name and time zone

Set the name your guests see, the handle in your booking links and the time zone dCal shows you times in, from Settings > General. Learn the handle rules and what each field changes.

The **General** tab holds your own profile: the name guests see, the handle in your links and the time zone dCal uses to show you times. Every person in the workspace has their own, and any role can change theirs.

***

**Step 1:** Click **Settings** in the left menu. It opens on **General**, at [app.dcal.ai/admin/settings/general](https://app.dcal.ai/admin/settings/general).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-4c988dd94cd2ff4892392a63dcd040c21c966339%2Fdcal-general-settings-01-profile-form.png?alt=media" alt="The profile form of the General tab with the Display name Jane Doe, the Public handle jdoe after the account code, and the Timezone America/Bogota, boxed, and the Save button boxed"><figcaption><p>Your profile: three fields and one <strong>Save</strong> button.</p></figcaption></figure>

***

**Step 2:** Type your **Display name**. It is the name guests see on your booking pages and in the booking emails, for example `Jane Doe`.

**Step 3:** Check your **Public handle**. It is the part of your links that comes after your account code, shown in front of the field. With the handle `jdoe`, your page is `book.dcal.ai/k7m2xq/jdoe` and each event adds its own name after it.

A handle uses 3 to 40 characters: lowercase letters, numbers and single hyphens between them. It must be free inside your workspace, and a few words are reserved. If it cannot be used, you see a message such as **Handle unavailable (taken).** under the form.

> **⚠️ Note:** Changing your handle changes every link you have shared, and links with the old handle stop opening. Update your email signature, website and any message you sent with the old link.

***

**Step 4:** Pick your **Timezone**. Type a city or region to filter the list.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-a2e0aa5c1e164a6c71f30dca73f38190034df3c9%2Fdcal-general-settings-02-timezone-list.png?alt=media" alt="The Timezone field open with San typed in the search box and six matching zones with their GMT offsets, from America/Argentina/San Juan to Europe/San Marino"><figcaption><p>Type part of a city to find your zone.</p></figcaption></figure>

Your time zone decides how dCal shows times to you: on the **Bookings** page, which reads "Times shown in" followed by your zone, and in the emails dCal sends you. dCal fills it from your browser the first time you open the dashboard, and once you pick one here it never changes it by itself.

The hours your guests can book come from each availability schedule and its time zone, which you set on the **Availability** page. A personal event can instead use its own weekly hours and time zone in **General** > **Availability** > **Custom hours for this event**. See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md). The booking page then shows those times in each guest's own time zone, taken from their browser. See [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md).

***

**Step 5:** Click **Save**. You see **Saved.** under the fields.

> **💡 Tip:** **Display name** and **Public handle** are also in **Settings** > **Booking Page**, in the **Profile** section. Both places change the same values.

***

## Also on this tab

| Section            | What it does                                                                                                                                                                                                                                                                                                    |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dapta branding** | One switch for the whole workspace: show or hide the "Made with dCal.ai by Dapta" badge and the free-calendar invitation on your public pages. Admins and owners change it, and hiding it is included with a Dapta AI subscription. See [The Dapta badge](https://docs.dapta.ai/dcal/design/dapta-branding.md). |
| **Language**       | The language of your dashboard, English or Español. See [Language and appearance](https://docs.dapta.ai/dcal/account/language-and-appearance.md).                                                                                                                                                               |

Your photo, cover image and the look of your booking page are not here: they live in **Settings** > **Booking Page**. See [Profile and layout](https://docs.dapta.ai/dcal/design/booking-page-studio.md).

## Related

* [Your links and profile page](https://docs.dapta.ai/dcal/share/your-booking-page.md): where your handle shows up.
* [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md): how your schedules and your guests' zones work together.
* [Language and appearance](https://docs.dapta.ai/dcal/account/language-and-appearance.md): dashboard language and light or dark mode.
* [Settings and members](https://docs.dapta.ai/dcal/account.md): every Settings tab.


---

# 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/general-settings.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.
