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

# CRM settings

Connect your CRM, choose how booking links sync, and review delivery results from **Settings → CRM**. These pages are available to workspace admins.

Distro supports one connected CRM at a time. Follow the [HubSpot](/crm/hubspot.md) or [Salesforce](/crm/salesforce.md) guide to connect the intended account.

## Find the right settings

| Tab                     | Use it to                                                                               |
| ----------------------- | --------------------------------------------------------------------------------------- |
| **Overview**            | Check the connection, CRM user matches, field counts, and deliveries needing attention. |
| **Booking links**       | Configure defaults for personal and group links that inherit them.                      |
| **Fields**              | Browse, search, and filter the saved CRM field catalog.                                 |
| **Enrichment mappings** | Choose destinations for enriched person and company data.                               |

When **Overview** shows deliveries needing attention, choose **Review delivery issues** to open [CRM activity](/crm/activity.md).

**Settings → Integrations** also leads to this CRM area. **Booking links → Links CRM settings** opens the booking defaults.

## Choose which flow writes to the CRM

Connecting a CRM enables Distro to use it. The actions you configure decide what is written and when.

* **Personal and group links:** configure [CRM sync](/booking-links/crm-sync.md) on the link or through workspace defaults. Delivery begins after a confirmed booking.
* **Form and Click Routers:** configure CRM actions in the router and owner updates in the relevant routing settings. Review when each action runs.
* **Outbound Routers:** configure booking-side CRM actions in the router. Starting a handoff or sharing a link does not create a CRM meeting.
* **Enrichment:** configure [enrichment mappings](/integrations/enrichment.md) separately.

The booking-link defaults do not change router actions or enrichment mappings. Turning one link Off does not disconnect the CRM for the rest of the workspace.

## Check host matching

Review saved CRM user matches from Overview, and manage them through [Members](/settings/workspace-settings/members.md). Logging a booking-link meeting needs the organizer to match an active user in the connected CRM.

Meeting ownership and prospect ownership are separate. **Update owner** in workspace defaults, or **Assign prospect ownership** in a link’s Custom settings, additionally changes the Contact or Lead owner when enabled. For a group booking, the designated organizer supplies that ownership; the other hosts are not separate prospects.

Use [Fields & mappings](/crm/fields-and-mappings.md) for missing destinations and [CRM activity](/crm/activity.md) for delivery problems.


---

# 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/crm/overview.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.