> 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/create-a-team.md).

# Create a team

Create a team in dCal, add people from your workspace, set who is a team admin and keep team events in step with the team. Only workspace owners and admins can manage teams.

Create a team, give it a name, a link and a logo, and add the people who will take its bookings. You need to be a workspace **Owner** or **Admin** to do this.

Before you start:

* **Everyone you add must already be in your workspace.** People you invited from **Settings** > **Members** can be added before they join, but until they join and open dCal in your workspace they offer no times and are never assigned a booking. On a **Collective** event, or as a fixed host, that leaves the whole event with no times, so add people once they have joined. Until they have working hours, the team event editor names them under **Hosts**. On a round-robin event set to **Equal distribution**, they never hold the other hosts back. See [Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md).
* **Ask each person to connect their calendar in this workspace.** A calendar connected in another workspace does not carry over. A host without a connected calendar can still take team bookings during their working hours, but dCal only knows about their other dCal bookings, not the rest of their day. For team events that are online meetings, ask them also to turn on **Add new events here** on one calendar: each booking's meeting link comes from the calendar where its host receives new events. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

***

**Step 1:** Click **Teams** in the left menu, then click **New team**. The button sits at the top right once you have teams, and in the middle of the page while you have none.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-118e49a3326af2f88ac2f6528481dce2eb42b33f%2Fdcal-create-a-team-01-new-team-button.png?alt=media" alt="The Teams page with the team Acme Sales already listed and the New team button boxed at the top right"><figcaption><p>Once you have a team, <strong>New team</strong> sits at the top right of the page.</p></figcaption></figure>

***

**Step 2:** Fill in the form.

| Field        | What to enter                                                                                                                                                                                                                                                                                                                |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**     | Shown at the top of the team's public page. Up to 200 characters.                                                                                                                                                                                                                                                            |
| **Slug**     | The team's part of the public address. It fills itself from the name (lowercase, with dashes) until you type in it yourself. Use lowercase letters, numbers and dashes, up to 80 characters. The line under the field previews the address, `/{account code}/team/{team slug}`. Each team in a workspace needs its own slug. |
| **Bio**      | Optional. It is saved with the team, but the public team page does not display it. Put anything guests need to read in each team event's description instead.                                                                                                                                                                |
| **Logo**     | Optional. Click **Upload image**, or paste an image address in **…or paste an image URL**. **Clear** removes it. A square image works best. Without a logo, the team shows the first letter of its name.                                                                                                                     |
| **Timezone** | Starts with your own time zone. The team page shows **Times in** this zone, and each team event's booking page names it as the host's time. Guests see the times of team events in their own time zone.                                                                                                                      |

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-186e96bfe86f10267e5ef531f0c032a3097497f6%2Fdcal-create-a-team-02-create-form.png?alt=media" alt="The New team form with the Name Acme Support, the Slug acme-support filled in automatically and boxed with its address preview, the Bio box, the Logo showing the letter A with Upload image, the Timezone America/New York and the Create team button"><figcaption><p>The slug follows the name until you edit it. The line under it previews the team's public address.</p></figcaption></figure>

About the logo:

* Any image file under 25 MB works. Large photos are resized for you, and an animated GIF keeps only its first frame.
* An address you paste is used exactly as it is, without resizing.
* If you want the logo to appear when someone shares the team link in a chat app, paste an image address instead of uploading a file. See [Your team page](https://docs.dapta.ai/dcal/teams/team-page.md).

***

**Step 3:** Click **Create team**. The button stays disabled until **Name** and **Slug** are both filled in. You land on the team's own page, and you are the team's first **Team admin**.

If another team in your workspace already uses that slug, you see **That team slug is in use.** Pick a different slug and try again.

> **⚠️ Note:** Check the name, slug, logo and time zone before you click **Create team**. The dashboard has no screen to change them once the team exists.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-98dc8bb491bbe84323e932bfc27f4591a4d7a8ca%2Fdcal-create-a-team-03-team-detail.png?alt=media" alt="The page of the team Acme Sales in the dashboard with the View public team page button, the Members (1) list with Jane Doe as Team admin and the Add member button boxed, and the Team events list with Sales demo and Discovery call and the New team event button boxed"><figcaption><p>The team's page: members at the top, team events below.</p></figcaption></figure>

***

## Add members

**Step 4:** On the team's page, click **Add member**. In the **Add a member** dialog, type the person's **Email**, choose a **Role** (**Member** or **Team admin**, Member by default) and click **Add member**. You see **Member added.**

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-df6673f1fb321e3fa354d296ff662cad384f0876%2Fdcal-create-a-team-04-add-member-dialog.png?alt=media" alt="The Add a member dialog with the email docs-test+1@example.com typed, the Role set to Member and the Add member button boxed"><figcaption><p>Type the email the person uses in your workspace and pick their team role.</p></figcaption></figure>

If nobody in your workspace has that email, the dialog says so and shows **Invite them from Members settings**. Invite the person there first, then come back and add them to the team.

Each member row shows the person's initial, name and email (or **Pending** when there is no email on file yet), their role, a role picker and **Remove**.

***

## Team roles

| Role           | What it means                                                                                                                                                                                                                                      |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Team admin** | Marks the people in charge of the team. A team always keeps at least one Team admin: the last one cannot be switched to Member. A Team admin shows a lock instead of **Remove**; change their role to **Member** first if you need to remove them. |
| **Member**     | A host of the team's events. **Remove** takes them off the team after you confirm.                                                                                                                                                                 |

To change a role, use the role picker on the person's row. You see **Role updated.** To remove someone, click **Remove** and confirm in the **Remove this member?** dialog. You see **Member removed.**, and you can add them again later.

> **💡 Tip:** The team role does not change what someone can do in dCal. Managing a team, its members and its events always needs a workspace owner or admin, whatever their role inside the team.

***

## Keep team events in step with the team

Every member of the team is a host of every team event. A team event takes its host list from the team at the moment you save the event. After you add or remove people, open each team event (click it under **Team events**) and click **Save changes**. That way new people start taking bookings and people who left stop. The event editor reminds you too: under **Hosts** it reads, for example, "Every member of Acme Sales hosts this event once you save it.", with a link to the team page.

> **⚠️ Note:** Someone you remove from the team stays a host of the team events you saved earlier, until you save those events again.

There is no per-event host picker. To offer a different group of people, create a separate team for them.

***

## Delete a team

On the **Teams** page, click **Delete** on the team's card and confirm in the **Delete this team?** dialog. Deleting is permanent.

A team can only be deleted while it has no team events. If it has some, you see **Delete the team’s event types first.** The dashboard does not delete team events, so once a team has events, keep the team and turn its events off instead: switch off **Visible on the booking page** on each one. See [Your team page](https://docs.dapta.ai/dcal/teams/team-page.md).

## Related

* [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md): create a team event, choose how hosts are picked and how bookings are distributed.
* [Your team page](https://docs.dapta.ai/dcal/teams/team-page.md): the public page guests book from.
* [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md): invite people to your workspace.
* [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md): so each host's busy times are respected.


---

# 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/create-a-team.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.
