> 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/manage-booking-links.md).

# Manage links

Workspace admins can manage personal booking links for other members from **Booking links → All Members Links**.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FL4du690qGryxCbQM8vu2%2FCleanShot%202026-09-10%20at%2020.57.12%402x.png?alt=media&amp;token=0efa1337-b2a5-43cd-83d7-4591bbe277d2" alt=""><figcaption></figcaption></figure>

Click **Create Booking Link**, select the **Owner**, choose the **Event type**, and enter the link name. Choose a theme in **Appearance & review**, then review the public URL before creating it. The selected owner is the person guests book with.

Use search and **Add filter** to find an existing link. Open it to review its owner, event type, and link settings. Preview the guest experience before copying the URL for a teammate.

For links with several participants, use **Manage Group Links**. Choose two or three participants and an organizer when [creating a group link](https://help.distro.so/booking-links/create-a-group-link.md).

## Decide where to make a change

| Change                                                     | Where to make it                                                                                      |
| ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| URL, questions, redirect, selected theme, or CRM sync mode | The personal or group link.                                                                           |
| Duration, availability, invitations, or reminders          | The shared [event type](https://help.distro.so/event-types/create-an-event-type.md).                  |
| Layout, colors, logos, or host visibility                  | The [booking theme](https://help.distro.so/settings/workspace-settings/branding.md), then publish it. |
| Defaults for inheriting links' CRM actions                 | **Settings → CRM → Booking links**. See [CRM sync](https://help.distro.so/booking-links/crm-sync.md). |
| Which personal links appear together on your profile       | [My booking page](https://help.distro.so/booking-links/my-booking-page.md).                           |

Check other uses before changing a shared event type, theme, or workspace default.

For an older link with private event settings, continue editing those settings in the link. These links cannot switch to a reusable event type through the event-type selector. Create a new link if you need that shared setup.

A link's star in the Chrome extension controls whether it appears with your favorites. It does not change the link's owner, participants, or availability.

## Duplicate a link

Use **Duplicate** from a link’s action menu when you want a similar link with a different URL. The copy keeps the selected event type; it does not create an independent event type. Review its questions, participants for a group link, and public URL before sharing it.

A duplicated link keeps an available selected theme and copies its questions and CRM settings independently. Review its CRM mode and mappings before sharing it. Use [QR codes](https://help.distro.so/booking-links/qr-codes.md) when a personal or member link needs a printed sharing option.


---

# 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/manage-booking-links.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.
