> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/booking-links/create-a-group-link.md).

# Group links

Let prospects book a meeting with 2–3 team members, based on overlapping availability.

Use a group booking link when two or three teammates need to attend the same meeting. Guests see times when all selected participants are available.

For example, a discovery call might need both an account executive and a solutions engineer. A group link finds their shared availability. Routing chooses who should receive a meeting.

## Create the link

Workspace admins create and manage group links.

1. Open **Booking links → Manage Group Links** and click **Create Group Link**.
2. Choose two or three **Participants**, then select an **Organizer** from those people. The organizer is the primary host, and their username appears in the public URL.
3. Continue to choose the **Event type**.
4. Enter the link name and review the URL.
5. In **Appearance & review**, choose a published booking theme or use the organization default.
6. Click **Create group link**, then preview it before sharing.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FWMrapqUyS8wAsn5pNmYZ%2Fdistro-group-link-hosts.jpg?alt=media" alt="Group-link setup with Maya Chen and Priya Patel as participants and Maya Chen as organizer"><figcaption><p>Choose two or three participants, then select the organizer from those people.</p></figcaption></figure>

The event type supplies the meeting's scheduling rules, invitations, and reminders. Check [each participant's availability](https://help.distro.so/settings/personal-settings/my-availability.md) if the preview offers fewer times than expected.

## Customize the booking page

Admins can edit the link's slug, **Booking questions**, **After booking** redirect, and [CRM sync](https://help.distro.so/booking-links/crm-sync.md). Name and Email remain required. A redirect needs a full destination URL; the workspace's [Redirect delay](https://help.distro.so/settings/workspace-settings/scheduler-settings.md) controls the wait.

Choose a [booking theme](https://help.distro.so/settings/workspace-settings/branding.md) for layout, colors, logos, and host visibility. There is one appearance for the whole group. The group's organizer can change its appearance without gaining access to the full group configuration or CRM settings.

Changing the slug makes the old direct URL unavailable. Save and preview changes before sharing the new URL.

For CRM sync, the primary external prospect is the person record. The designated organizer supplies meeting ownership, and one group booking creates one CRM meeting.

## Share it from Chrome

Your group links appear in the extension's **Scheduling** tab. Copy a link, save it as a favorite, [offer times](https://help.distro.so/integrations/chrome-extension/offer-times.md), or create a [single-use link](https://help.distro.so/integrations/chrome-extension/single-use-links.md) when those actions are available.

Group members see links they participate in. Workspace admins can see and edit all group links in the extension. If a link is missing, check its participants and your connected workspace.


---

# 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://help.distro.so/booking-links/create-a-group-link.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.
