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

# Key concepts

Plain definitions of the words the dCal dashboard and docs use, from event, booking link and availability schedule to requests, holds, teams, roles and one-off invite links. Read this page once and th

This page defines the words the rest of the dCal docs use. Read it once and the dashboard, your booking page and your emails will make more sense.

***

## Event

An event is a kind of meeting people can book with you, such as "Intro call", "Demo" or "Consultation". The dashboard lists them under **Events**. Each event has a title, a slug (the last part of its address), one length in minutes, an optional location, an availability schedule, booking questions, reminders and a few rules: minimum notice, how far ahead guests can book, buffers before and after, slot interval, seats, and whether you confirm each booking yourself.

An event is either **personal** (you are the host) or a **team event** (it belongs to a team and books one or more of its members). New events start with a minimum notice of 2 hours, so nobody can book a time that starts sooner than that.

Each event has one length. To offer a 30-minute and a 60-minute version, create two events.

An event is visible on your profile page unless you mark it **Hidden**. A hidden event has no public page: its address shows "Page not found", and only a [one-off invite link](#one-off-invite-link) can book it.

See [Events](https://docs.dapta.ai/dcal/events.md). An assistant can also use [create\_event](https://docs.dapta.ai/dcal/developers/mcp-tools.md#create_event) to put an event directly on your own calendar with any title, time and length. That event has no booking link or event type.

## Booking link and profile page

In the dashboard, **Your booking link** means your **profile page**: one address that lists all your visible events. Each event also has its own page, which opens straight on the calendar for that event.

Booking pages live on `book.dcal.ai`, apart from your dashboard at `app.dcal.ai`. Every link dCal gives you uses `book.dcal.ai`. Older links that start with `app.dcal.ai` keep working and send guests to the same page on `book.dcal.ai`.

| Page                                    | Address                                             |
| --------------------------------------- | --------------------------------------------------- |
| Your profile page ("Your booking link") | `book.dcal.ai/{account code}/{handle}`              |
| One event's page                        | `book.dcal.ai/{account code}/{handle}/{event slug}` |
| A team page                             | `book.dcal.ai/{account code}/team/{team slug}`      |

| Part of the address | What it is                                                                                                                   | Where you change it                                                       |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Account code**    | Six characters that identify your workspace, created automatically. With a custom link, the name you choose takes its place. | **Settings** > **Booking Page** (custom link, for paying Dapta customers) |
| **Handle**          | You, inside the workspace. dCal creates it from your name the first time you sign in: Jane Doe gets `jdoe`.                  | **Settings** > **General** > **Public handle**                            |
| **Event slug**      | The event, filled in from its title when you create it.                                                                      | The event's **Event link** field                                          |

When you have exactly one visible event, your profile link opens that event directly. To show the profile even then, turn on **Always show my profile, even with one event type** in **Settings** > **Booking Page**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-cfc319372356baa593c1413f890e2ed273fa8c98%2Fdcal-key-concepts-01-profile-page.png?alt=media" alt="Jane Doe&#x27;s profile page with the initials JD, her name and bio, and three events: 30-minute meeting and Intro call (30 min) and Consultation (60 min)"><figcaption><p>A profile page lists every visible event. Each row opens that event's own page.</p></figcaption></figure>

> **⚠️ Note:** Changing your handle or an event's slug changes the address. Links you already shared with the old handle or slug stop opening, so share the new link afterwards. A custom link works differently: your old code keeps working and sends visitors to the new address.

## Availability schedule

A schedule is a set of weekly hours, date overrides and a time zone. Weekly hours can have several ranges per day, for example 09:00 to 12:00 and 14:00 to 18:00. A date override replaces the weekly hours on one specific date. You manage schedules in **Availability**.

Every host gets a schedule called **Working hours**, Monday to Friday 09:00 to 17:00, the first time they open the dashboard, set to the time zone of their browser. It is your default schedule. In **General** > **Bookable hours**, a personal event can follow **My working hours**, use **A saved schedule**, or keep **Custom hours for this event**. Custom hours are weekly ranges and a time zone for this event only, and do not appear as another schedule in **Availability**.

See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md).

## Connected calendar

A connected calendar is a whole Google Calendar or Outlook / Microsoft 365 account that you link in **Calendars**. You can connect several accounts, and each one has two settings:

| Setting                 | What it does                                                                                                                         |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Check for conflicts** | Busy times on this calendar block new bookings. On by default for every account you connect.                                         |
| **Add new events here** | Booked meetings are written to this calendar. Only one calendar can receive events; the first account you connect gets this setting. |

Without a connected calendar dCal still takes bookings, but it only sees your dCal bookings, not your other meetings, and it cannot create online meeting links.

See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

## Booking and its statuses

A booking is one meeting someone booked on one of your events. The **Bookings** page shows each booking with one of four statuses:

| Status        | What it means                                                            |
| ------------- | ------------------------------------------------------------------------ |
| **accepted**  | The meeting is on, either right away or after you confirmed the request. |
| **pending**   | A request waiting for you to confirm or decline it.                      |
| **cancelled** | You or the guest cancelled it.                                           |
| **rejected**  | You declined the request.                                                |

Rescheduling is not a status: a moved booking stays **accepted** with its new time.

See [Bookings](https://docs.dapta.ai/dcal/bookings.md).

## Request

A request is a booking on a personal event where **Requires confirmation** is on. The guest sees **Booking requested**, and the booking waits as **pending** until you click **Confirm** or **Decline** on the **Bookings** page. An AI agent you connect to dCal can also confirm or decline it for you. Nothing is written to your calendar until you confirm.

While a request waits, its time stays blocked for everyone else. A request does not expire on its own, so answer it soon.

See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).

## Hold

When a guest picks a time on a personal event with one seat, dCal holds that time for 10 minutes while they fill in their details, so nobody else can take it. The form shows **Held until** and the time. Going back or picking another time releases the hold, and closing the page lets it lapse after 10 minutes. Team events and group events do not place holds.

An AI agent you connect to dCal can hold a time on a one-host event the same way, for about 10 minutes, while it checks the details with the person, then book it. See [MCP tools reference](https://docs.dapta.ai/dcal/developers/mcp-tools.md).

## Team and scheduling methods

A team is a group of people in your workspace who share bookings. It has its own public page and its own team events. When you save a team event, every member of the team becomes one of its hosts, and each team event uses one scheduling method:

| Method                | Who attends                                                                                                                                                                                                                   | Which times are offered                                                                                                                                                                       |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Round-robin**       | One host per booking: among the hosts free in their own working hours, the one with the highest priority, then by weight. With **Distribution** set to **Equal distribution**, the one with the fewest bookings of that event | Times when any host is free in their own working hours. With **Equal distribution**, a host with 3 or more bookings more than the least-booked host offers no times until the others catch up |
| **Collective**        | Every host                                                                                                                                                                                                                    | Only times when all hosts are free in their own working hours                                                                                                                                 |
| **Fixed round-robin** | The fixed hosts plus one rotating host                                                                                                                                                                                        | Times when every fixed host and at least one other host are free in their own working hours                                                                                                   |

Only owners and admins create teams and team events. See [Teams](https://docs.dapta.ai/dcal/teams.md).

## Workspace

Your dCal workspace starts from your Dapta workspace. Everyone who signs in to dCal from the same Dapta workspace shares one dCal workspace and the same account code in their links. People you invite by email can join it too, and keep their own workspace; anyone in several workspaces moves between them with the workspace switcher.

| Shared by the whole workspace                                                                                                                                     | Personal to each host                                                                                  |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Members and roles, teams and team events, the brand kit, the Dapta branding setting, the custom link, email notification settings, HubSpot, webhooks and API keys | Your events, your availability schedules, your connected calendars and the design of your booking page |

See [Workspaces](https://docs.dapta.ai/dcal/account/workspaces.md).

## Member roles

Each person in the workspace has one role:

| Role       | What they can do                                                                                                                                                                                                                                                                                                                                          |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owner**  | Everything an admin can do, plus transfer ownership. The first person who signs in to dCal from a workspace becomes its owner.                                                                                                                                                                                                                            |
| **Admin**  | Manages members (except owners), everyone's events, schedules and bookings, teams and team events, the brand kit and the workspace settings: **Notifications**, **Members** and **Integrations**, plus **Connect your agent**, **Tools** and **API and webhooks** in the left menu, where an AI agent is connected and API keys and webhooks are managed. |
| **Member** | Manages their own events, schedules, bookings, calendars and booking page.                                                                                                                                                                                                                                                                                |

People from your Dapta workspace who sign in after the owner join as members. People you invite get an invitation email, join when they accept it, and get the role you chose. See [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md) and [Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md).

## Brand kit

The brand kit is one look for the whole workspace: logo, accent color, light or dark canvas, font, corners, buttons and card style. Owners and admins save it under **Settings** > **Booking Page** > **Brand kit**.

Team pages always wear the current brand kit. Your own pages take it only when you click **Apply brand kit** in your booking page studio. That copies the kit onto your page once; later changes to the kit do not change your page until you apply it again.

See [Brand kit](https://docs.dapta.ai/dcal/design/brand-kit.md).

## Manage link

The manage link is a private link dCal gives your guest in their emails and on the confirmation screen (**Manage your booking**). It opens a page where the guest can reschedule to a time in the next three weeks, or cancel, any time before the meeting starts. A request that is still pending can only be cancelled from it.

Each reschedule creates a new manage link, so the link in an older email stops working. The most recent email always carries the current one.

> **💡 Tip:** On an event that requires confirmation, the manage link arrives in the guest's "Request received" email. When you confirm, the guest's confirmation email does not repeat it, so the link in the "Request received" email is the one to keep for rescheduling or cancelling.

See [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md).

## One-off invite link

A one-off invite link books one event once, then stops working. You create them in the event's **One-off invite links** section with **Create invite link**. A link stays live until it is used or you revoke it, and cancelling the booking does not bring it back.

On a visible event an invite link limits nothing, because anyone with the normal link can still book. Mark the event **Hidden** to make invite links the only way in.

See [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md).

## Group event

A group event is an event whose **Seats / slot (group)** is 2 or more. Several people can book the same time until its seats are full. On the booking page each time shows how many seats are left, or **Full**.

See [Group events](https://docs.dapta.ai/dcal/events/group-events.md).

## Related

* [Start here](https://docs.dapta.ai/dcal/dcal.md)
* [Getting started](https://docs.dapta.ai/dcal/getting-started.md)
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md)
* [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.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 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/key-concepts.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.
