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

# Group events (seats)

Let several people book the same time on a dCal event with Seats / slot (group). Learn how to set the number of seats, what guests see on the booking page, how group times are blocked, and who receive

A group event lets several people book the same time, up to the number of seats you set. Use it for a class, a workshop, an open office hour or a group demo. Everyone who books joins the same meeting at the same time.

***

**Step 1:** Open **Events** and click **Edit** on the event (or create a **New event**). In **General**, open **Advanced settings**. In **Seats / slot (group)**, type how many people can book each time, for example `10`. Click **Save changes** (**Create event** on a new event).

| Value               | What it means                            |
| ------------------- | ---------------------------------------- |
| Empty (the default) | A normal event: one booking per time.    |
| `1`                 | The same as empty.                       |
| `2` or more         | That many people can book the same time. |

Seats work on your own events. On a team event, the field has no effect: each time takes one booking.

***

**Step 2:** Open the booking page with **Open booking page** to check what guests see. Each time shows how many seats are still free, for example **8 left**. When the last seat is taken, that time is no longer offered.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-1c1679bd9ad63787b5c14fd6a38506c616a8c475%2Fdcal-group-events-02-seats-left.png?alt=media" alt="The times of Wednesday, October 28 on a booking page, where each time shows the seats left: 10 left on most times and 8 left, boxed, at 10:00 AM"><figcaption><p>Guests see the seats left on every time.</p></figcaption></figure>

If the last seat goes while a guest is still filling in the form, they see **That time was just taken.** and a **Pick another time** button.

***

## How group times are blocked

* Bookings on the group event do not block its time until every seat is taken.
* Everything else still blocks the time as usual: your other bookings and the busy times on the calendars you check for conflicts. A group time also blocks your other events, like any meeting.
* Unlike one-to-one events, a group time is not held for a guest while they fill in their details. Seats go to whoever confirms first.

## Who takes a seat

* Every person on a time takes one seat, counted once by email address: the people who booked it and the guests added to their booking, for example by an AI agent or an integration through the API. The seats left that guests see on the booking page count all of them.
* An email address that already holds a seat on a time never takes a second one there. If everyone in a new booking already has a seat on that time, nothing changes.
* A booking that asks for more seats than are left gets none: either everyone in it gets a seat, or nobody does.
* Adding people to a booking that already exists, through the API, stops at 30 people in all, or at the event's seats when it has more. See [REST API](https://docs.dapta.ai/dcal/developers/rest-api.md).

## Rules that work together with seats

* **One booking per person** stops the same email address from taking two seats on the same event. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md).
* A [one-off invite link](https://docs.dapta.ai/dcal/events/one-off-links.md) books one seat and is then used up.
* **Duration**, **Slot interval**, **Minimum notice** and the buffers work the same as on any event. See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

***

## Emails and the booking record

A group time is a single booking. Everyone who books it is added to that one booking.

|                                             | First person to book a time | People who take the other seats |
| ------------------------------------------- | --------------------------- | ------------------------------- |
| Confirmation screen                         | Yes                         | Yes                             |
| **Add to calendar** button on that screen   | Yes                         | Yes                             |
| Confirmation email with the calendar invite | Yes                         | No                              |
| Reminder emails                             | Yes                         | No                              |
| Link to manage the booking                  | Yes                         | No                              |
| Your **New booking** email                  | Yes, one per time           | No                              |

The first person's booking is also the one written to your calendar and, if you use them, sent to your webhooks and to HubSpot. In **Bookings**, a group time shows as one row.

Once the booking is confirmed, each person who takes a later seat is added as a guest to that one meeting on your calendar, so your calendar app may send them its own invitation. This needs a connected calendar set to **Add events here** for the event.

> **⚠️ Note:** The first person who booked a time holds its manage link, and cancelling or rescheduling from that link applies to the whole time. Put everything attendees need, such as the address or how to join online, in the event's **Description** or **Location**, so everyone sees it on the booking page before they book. Ask attendees to contact you directly if they cannot come.

For **Calendar event title** and **Calendar event description**, use details that apply to the whole group. These fields are in **General** > **In the calendar**. A shared calendar event cannot show one guest's name, email or form answers. See [Calendar text](https://docs.dapta.ai/dcal/events/event-settings.md#calendar-event-text).

## Related

* [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md): every field of the event form.
* [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md): where to put the joining details.
* [See your bookings](https://docs.dapta.ai/dcal/bookings/see-your-bookings.md): how bookings appear in dCal.
* [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md): the emails each booking sends.


---

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