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

# Events (booking links)

Events are the meetings people can book with you in dCal, and each one has its own booking link. Learn what the Events page shows, what each quick action on a row does, how team events are listed, and

An event is one kind of meeting you offer, for example a 30-minute "Intro call" or a 45-minute "Demo". Each event has its own booking link, length, location, questions and reminders, so you can send every person straight to the right meeting. This page walks you through the **Events** page, where you create, share, hide and edit them.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-43fe72e408c1330bebbf07bce729002fb16adc2c%2Fdcal-events-01-list.png?alt=media" alt="The Events page with five personal events, 30-minute meeting, Intro call, Demo marked hidden, Consultation marked needs confirmation and Workshop, and below them Team events, with the team Acme Sales, its New event for Acme Sales button and its events Sales demo and Discovery call"><figcaption><p>The Events page: your own events first, then the events of your teams.</p></figcaption></figure>

Open **Edit** for the tabbed editor: **General**, **Booking form**, **Reminders**, **CRM Connection** when available, and **AI Agents**. Use **Preview booking page** to try unsaved changes without making a booking. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md).

***

## Events and their links

Every event gets its own address, made of three parts:

`book.dcal.ai/{account code}/{handle}/{event slug}`

| Part             | What it is                                                                                           | Where it comes from                                                               |
| ---------------- | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| `{account code}` | Your workspace's short code, or its custom link when your workspace has one.                         | [Custom link](https://docs.dapta.ai/dcal/share/custom-link.md)                    |
| `{handle}`       | Your public handle. dCal makes one from your name the first time you sign in (Jane Doe gets `jdoe`). | [Your name and time zone](https://docs.dapta.ai/dcal/account/general-settings.md) |
| `{event slug}`   | The event's **Event link**, which you set when you create the event.                                 | [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md)           |

A second link lists all your visible events on one page: your profile page, `book.dcal.ai/{account code}/{handle}`. The Home page calls that one **Your booking link**. See [Your links and profile page](https://docs.dapta.ai/dcal/share/your-booking-page.md).

***

## The Events page

Sign in at [app.dcal.ai](https://app.dcal.ai) and open **Events** in the left menu. The list shows your own events, one row per event. Owners and admins also see only their own personal events here.

Each row shows:

* The event title, followed by **(hidden)** when the event is hidden.
* A second line with the slug and the length, for example `/intro-call · 30 min`, plus **needs confirmation** when the event uses [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md).

The **New event** button sits at the top right. When you have no events yet, the page shows an empty state with **New event** in the middle instead.

***

## Quick actions on each row

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-14fc3e003926f920fb31448dd106f85c18e4b88b%2Fdcal-events-02-row-actions.png?alt=media" alt="The Intro call row with the visibility switch, the Open booking page, Copy link and Embed on your site icons, and the Edit and Delete buttons, each boxed"><figcaption><p>From left to right: visibility, open, copy, embed, edit and delete.</p></figcaption></figure>

| Control                                  | What it does                                                                                                                                                                                                          |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Switch (**Visible on the booking page**) | On: the event is listed on your profile page and can be booked at its link. Off: the event is hidden. The change saves at once and confirms with **Event is now visible.** or **Event hidden from the booking page.** |
| **Open booking page** (arrow icon)       | Opens the event's public page in a new tab, so you can check what guests see.                                                                                                                                         |
| **Copy link** (chain icon)               | Copies the event's full link and shows **Link copied.**                                                                                                                                                               |
| **Embed on your site** (code icon)       | Opens the embed code for this event. See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md).                                                                                                          |
| **Edit**                                 | Opens the event form. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md).                                                                                                                    |
| **Delete**                               | Asks once more on the row, then deletes the event. See [Delete an event](https://docs.dapta.ai/dcal/events/create-an-event.md#delete-an-event).                                                                       |

Hold the pointer over an icon to see its name.

> **💡 Tip:** To offer a variation of an event, such as a longer version of the same call, create a new event with its own slug. Each event keeps one length.

***

## Team events

Below your own list, **Team events** lists every team in your workspace, each with its events. A team with no events yet reads **No team events yet.** Owners and admins see a **New event for** button next to each team name, for example **New event for Acme Sales**, which opens a new event for that team.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-fd1ed3edc3da6124895a51b19f92414a1aa3cbc7%2Fdcal-events-03-team-events.png?alt=media" alt="The Team events group with the team Acme Sales, its New event for Acme Sales button boxed, and its two events, Sales demo and Discovery call, each with a switch, three icons and Edit"><figcaption><p>Every team is listed with its own button for a new team event. Team events have the same quick actions as your own events, except Delete.</p></figcaption></figure>

* Team event rows have the visibility switch, the open, copy and embed icons, and **Edit**. They have no **Delete** button: to stop offering a team event, switch it off.
* You create a team event here, with **New event for** and the team's name, or from the team's own page, with **New team event**.
* How a team event picks who hosts each booking is explained in [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md).

***

## Who can do what

| Role                   | Your own events                     | Team events                                                      |
| ---------------------- | ----------------------------------- | ---------------------------------------------------------------- |
| **Member**             | Create, edit, hide and delete them. | Cannot create or edit them.                                      |
| **Owner** or **Admin** | Create, edit, hide and delete them. | Create them from this page or the team page, edit and hide them. |

Roles are set in Settings. See [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md).

***

## In this section

| Page                                                                               | What you will learn                                                                                                                                                                             |
| ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md)            | Every field of the event form in order, then how to edit, hide, rename and delete an event.                                                                                                     |
| [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md) | Length, location types, the online meeting link, slot interval, minimum notice, buffers, schedules, the booking window, the redirect after booking and tracking pixels, with a reference table. |
| [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md)        | The fields every booking asks, how to add your own questions, and where the answers reach you.                                                                                                  |
| [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md)  | Turn bookings into requests you confirm or decline.                                                                                                                                             |
| [Group events (seats)](https://docs.dapta.ai/dcal/events/group-events.md)          | Let several people book the same time.                                                                                                                                                          |
| [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md)         | Links that book an event once, for one person.                                                                                                                                                  |

## Related

* [Quickstart: your first booking link in 5 minutes](https://docs.dapta.ai/dcal/getting-started/quickstart.md): create and share an event from scratch.
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md): the booking page, step by step.
* [Your links and profile page](https://docs.dapta.ai/dcal/share/your-booking-page.md): the page that lists all your events.
* [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md): the schedules your events use.


---

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