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

# Workspaces

dCal uses the same workspaces as the Dapta app. Learn how a dCal workspace starts, who becomes its owner, what the whole workspace shares and what stays personal, how your workspace shows up in your b

dCal uses the same workspaces as the Dapta app. Everyone who signs in to dCal from the same Dapta workspace shares one dCal workspace: its members, teams, brand kit, emails and integrations. People you invite by email join it too, and keep their own workspace. There is nothing to create or link by hand.

***

## How a workspace starts

* **It appears on its own.** The first time someone from your Dapta workspace signs in at [app.dcal.ai](https://app.dcal.ai), dCal creates the matching workspace.
* **The first person in becomes the Owner.** Everyone from your Dapta workspace who signs in after joins as a **Member**, unless an admin invited them first with another role. People from outside it join when they accept an invitation. See [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md).
* **Each person gets a handle.** dCal builds it from their name, for example `jdoe` for Jane Doe, and adds a number if it is taken. They can change it in [Your name and time zone](https://docs.dapta.ai/dcal/account/general-settings.md).

When you sign in, dCal opens the workspace your Dapta sign-in belongs to: your own. To add someone to it, invite them by email from **Settings** > **Members** (see [Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md)), or add them to your workspace in the Dapta app (see [Add team members](https://docs.dapta.ai/my-account/account/add-team-members.md)) and ask them to sign in to dCal with the same email.

***

## What the workspace shares and what stays yours

| Shared by the whole workspace           | Each person's own                                      |
| --------------------------------------- | ------------------------------------------------------ |
| Members and their roles                 | Display name, public handle and time zone              |
| Teams and team events                   | Personal events (booking links)                        |
| Brand kit and the Dapta branding switch | Availability schedules                                 |
| The custom link                         | Connected calendars                                    |
| Notification emails and their wording   | Booking page design                                    |
| The HubSpot connection                  | The bookings they host                                 |
| API keys and webhooks                   | Dashboard language and light or dark mode, per browser |

Webhooks, HubSpot and API keys cover every booking in the workspace, whoever hosts it. See [Integrations](https://docs.dapta.ai/dcal/integrations.md).

If you belong to several workspaces, everything in the right column is separate in each one: your name, schedules, events and connected calendars in one workspace do not carry over to another. The exception is the dashboard language and mode, which follow your browser.

***

## Your workspace in your links

Every public link starts with your account code: six letters and numbers chosen by dCal, such as `k7m2xq`. A personal event link reads `book.dcal.ai/k7m2xq/jdoe/intro-call`, and a team page `book.dcal.ai/k7m2xq/team/sales`.

With a Dapta AI subscription, an admin or owner can replace that code with a custom link, such as `book.dcal.ai/acme/jdoe/intro-call`. The old code keeps working and sends visitors to the new address. See [Custom link](https://docs.dapta.ai/dcal/share/custom-link.md).

***

## One workspace for your agents too

Text Agents and Voice Agents in the same Dapta workspace book on this dCal workspace, against the same open times as your booking pages. See [Let your Dapta agent book](https://docs.dapta.ai/dcal/dapta-agents.md).

***

## If you belong to several workspaces

In the dashboard you work in one workspace at a time. When you sign in, dCal opens your own workspace, the one your Dapta sign-in belongs to. If you joined or were invited to other workspaces, a workspace switcher appears at the top of the left menu: pick a workspace under **Your workspaces**. Your role can be different in each. See [Work in several workspaces](https://docs.dapta.ai/dcal/account/invite-teammates.md#work-in-several-workspaces). If you land in the wrong account, see [Signing in fails](https://docs.dapta.ai/dcal/troubleshooting.md#signing-in-fails).

An AI agent you connect by signing in, such as Claude or ChatGPT, can reach more than one. It reaches every dCal workspace where you are an active owner or admin, including workspaces you joined by invitation, and where you have opened dCal on the web within the last 30 days. A workspace you were invited to counts only once you have joined it and opened it. When it reaches several, the agent gets the list from dCal and must name the workspace in each call; a call that names none is refused and asks the agent to say which one. Tell your agent which workspace you mean.

An API key always works in the one workspace where it was created. See [Connect Claude or ChatGPT by signing in](https://docs.dapta.ai/dcal/developers/connect-with-sign-in.md).

***

## Good to know

* dCal is free. Teams, members and every scheduling method cost nothing. Only the custom link and hiding the Dapta branding come with a Dapta AI subscription.
* The workspace starts with the people of your Dapta workspace, plus anyone you invite, and roles are set in dCal. Being an admin in the Dapta app does not make you an admin in dCal: an admin or owner sets your role in **Settings** > **Members**.

## Related

* [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md): who can do what, and how people get in.
* [Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md): invite people by email and move between workspaces.
* [Custom link](https://docs.dapta.ai/dcal/share/custom-link.md): replace the account code in your links.
* [Connect Claude or ChatGPT by signing in](https://docs.dapta.ai/dcal/developers/connect-with-sign-in.md): connect an AI agent with your Dapta account.
* [Key concepts](https://docs.dapta.ai/dcal/key-concepts.md): workspace, host, event and booking in one page.


---

# 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/workspaces.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.
