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

# Your team page

Every dCal team has a public page that lists its events. Find its address, see what guests see on the team page and on a team event, share one team event, hide an event, and learn how the page looks a

Every team has a public page that lists its events. Share the team page, or the link to one team event, and guests book with the team instead of with one person.

| Page               | Address                                                     |
| ------------------ | ----------------------------------------------------------- |
| **Team page**      | `book.dcal.ai/{account code}/team/{team slug}`              |
| **One team event** | `book.dcal.ai/{account code}/team/{team slug}/{event slug}` |

`{account code}` is the code of your workspace, or your custom link when your workspace has one. Addresses that use an older code keep working and send guests to the current address. See [Custom link](https://docs.dapta.ai/dcal/share/custom-link.md). Team links you shared earlier with `app.dcal.ai` in them keep working too: they send guests to the same address on `book.dcal.ai`, with everything after it kept, UTM tags included. See [Track where bookings come from](https://docs.dapta.ai/dcal/share/your-booking-page.md#track-where-bookings-come-from).

***

**Step 1:** Open the page. Click **Teams** in the left menu, click **Manage** on the team, then click **View public team page**. It opens in a new tab.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-3546afa1d890f6f30716da2204ecad98b4479ccb%2Fdcal-team-page-01-view-public-team-page.png?alt=media" alt="The top of the Acme Sales page in the dashboard with the View public team page button boxed"><figcaption><p><strong>View public team page</strong> opens what your guests see.</p></figcaption></figure>

***

**Step 2:** Check what guests see on the team page:

* Your workspace name in a small line above the team name, shown only when it differs from the team name.
* The team name and logo. Without a logo, the team's initials.
* The line **Times in** followed by the team's time zone.
* The team's visible events, shortest first, each with its title, description and length. A guest clicks one to book it.
* **No bookable team events yet.** when the team has no visible events.
* At the bottom, the Dapta badge and the free calendar invitation, unless your workspace hides them. See [The Dapta badge](https://docs.dapta.ai/dcal/design/dapta-branding.md).

***

**Step 3:** Open a team event as a guest would. The booking page works like any other dCal booking page, with these differences:

* The team name and logo (or its initials) appear where a host's name and photo would be.
* The event details include the scheduling method, for example **Round-robin**.
* Times open in the guest's own time zone. The event panel shows the team's time zone as the host's time, and guests can switch to any zone.
* Guests do not see which person they will meet before they book.

***

## Share one team event

Each team event row, on the team's page and on the **Events** page under **Team events**, has these controls:

| Control                                  | What it does                                                                                                                         |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Visible on the booking page** (switch) | Shows or hides the event on the team page.                                                                                           |
| **Open booking page**                    | Opens the team event in a new tab.                                                                                                   |
| **Copy link**                            | Copies the team event's address. You see **Link copied.**                                                                            |
| **Embed on your site**                   | Gives you a code snippet to place the event on your website. See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md). |

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-db0d7c88bd08c251649fc5f41e77bf1440fddcc4%2Fdcal-team-page-04-team-event-row-actions.png?alt=media" alt="The Sales demo team event row with the visibility switch and the Open booking page, Copy link and Embed on your site icons boxed"><figcaption><p>The row controls: visibility, open, copy link and embed.</p></figcaption></figure>

***

## Hide a team event

Switch off **Visible on the booking page** on the event's row (or tick **Hidden** in the event editor). A hidden team event is not listed on the team page, and its own address no longer opens it. A [one-off invite link](https://docs.dapta.ai/dcal/events/one-off-links.md) can still open it for one person.

Hiding is also how you retire a team event: the dashboard does not delete team events.

***

## How the team page looks

* **The workspace brand kit.** Team pages have no design settings of their own. They wear the workspace [brand kit](https://docs.dapta.ai/dcal/design/brand-kit.md) and change as soon as an owner or admin saves it. Settings the kit does not include (template, density and how times are listed) stay at their defaults.
* **Without a brand kit.** The page shows a dark background with a lime accent.
* **On your website.** An embed code can set its own accent color and style for that embed only. See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md).
* **Language.** The team page shows its buttons and messages in Spanish when the visitor's browser prefers Spanish, and in English otherwise. Add `?lang=es` or `?lang=en` to the team link to choose for them.

## When the team link is shared

When someone pastes the team page link in a chat app or a social post, the preview shows:

* **Title:** the team name, followed by your workspace name when it differs, for example "Acme Sales · Acme Corp".
* **Description:** a line such as "Book time with Acme Sales online."
* **Image:** the team logo, only when you added it by pasting an image address. An uploaded logo is not used in previews, and team pages have no generated preview card.

## Related

* [Create a team](https://docs.dapta.ai/dcal/teams/create-a-team.md): the team's name, slug, logo and time zone.
* [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md): how hosts are picked.
* [Brand kit](https://docs.dapta.ai/dcal/design/brand-kit.md): the look team pages wear.
* [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md): put a team event on your site.
* [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md): a link that books once.


---

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