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

# Teams

Teams in dCal let several hosts share one booking page. Create a team, add people from your workspace and choose how each booking is assigned: round-robin, collective or fixed round-robin. Team schedu

A team is a group of hosts from your workspace who share a booking page. Guests book with "Acme Sales" instead of one person, and dCal picks who takes the meeting, or books everyone at once, depending on the scheduling method you choose. Team scheduling is free, with all three methods included.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-f4bea69e8fbb5143ef54a8d30f1f44cb74d8fdfe%2Fdcal-teams-01-teams-list.png?alt=media" alt="The Teams page with one team card, Acme Sales, showing the initials AS in place of a logo, its slug and member count (1 member), its public address and the Manage and Delete buttons"><figcaption><p>The <strong>Teams</strong> page. Each card shows the team's slug, its member count and its public address.</p></figcaption></figure>

***

## How a team works

| Part            | What it is                                                                                                           |
| --------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Team**        | A name, a slug for the link, an optional logo and a time zone. You find your teams under **Teams** in the left menu. |
| **Members**     | People from your workspace. Every member of the team is a host of the team's events.                                 |
| **Team events** | Events that belong to the team instead of to one person. Each one has its own **Scheduling method**.                 |
| **Team page**   | The public page `book.dcal.ai/{account code}/team/{team slug}` that lists the team's events.                         |

Each team event uses one of three scheduling methods:

| Method                | In one line                                                                                                                                                                                                                              |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Round-robin**       | One host per booking: among the hosts free in their own working hours, the one with the highest priority, with bookings shared by weight among hosts at the same level. With **Equal distribution**, bookings are shared evenly instead. |
| **Collective**        | Every host attends. Guests only see times when all hosts are free in their own working hours.                                                                                                                                            |
| **Fixed round-robin** | One or more fixed hosts attend every booking, plus one rotating host who is free in their own working hours.                                                                                                                             |

***

## Who can manage teams

Only people with the workspace role **Owner** or **Admin** can create and delete teams, add and remove team members, change team roles and create team events. Everyone else in the workspace can open the **Teams** page and see the teams, but their changes are refused. See [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md) to check or change someone's workspace role.

> **💡 Tip:** Ask every host to [connect their calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md) before you share a team link. dCal then skips the times they are already busy, for every scheduling method. For online meetings, each host also needs **Add new events here** on one of their calendars: the meeting link comes from the calendar where the booking's host receives new events.

***

## In this section

{% content-ref url="/pages/lroRoWbKQxTctb6XVWPT" %}
[Create a team](https://docs.dapta.ai/dcal/teams/create-a-team.md)
{% endcontent-ref %}

{% content-ref url="/pages/moUTb0r3y31UERhcKT1S" %}
[Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md)
{% endcontent-ref %}

{% content-ref url="/pages/h1i0n1oQ2VXhVG3GZVW3" %}
[Your team page](https://docs.dapta.ai/dcal/teams/team-page.md)
{% endcontent-ref %}

## Related

* [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md): invite people to your workspace before you add them to a team.
* [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md): each host's default schedule decides when they can take team bookings.
* [Brand kit](https://docs.dapta.ai/dcal/design/brand-kit.md): team pages wear the workspace brand kit.


---

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