> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/faqs-troubleshooting/why-is-the-sync-to-crm-button-greyed-out.md).

# Why Is the 'Sync to CRM' Button Greyed Out?

If you are unable to sync segments to your CRM because the button is greyed out, this is likely due to insufficient permissions. Only users with **CRM sync permissions enabled** in their Reo.Dev account can send segments to their CRM.

***

#### **Solution: Enable CRM Sync Permissions**

To resolve this, ask an **admin user** in your team to grant you CRM sync permissions by following these steps:

#### **How to Enable CRM Sync Permissions:**

1. Go to **Integrations** in Reo.Dev.
2. Find the Hubspot/Salesforce/Attio CRM card and Click on the **Gear Icon**

<figure><img src="/files/UcM3kC9Nk7Sf6lAqiaot" alt=""><figcaption></figcaption></figure>

3. Click on 'Configure' in the User Settings section. You will be redirected to Users Section.&#x20;

<figure><img src="/files/Bs2NYAxIWQkDwWpSuRaT" alt=""><figcaption></figcaption></figure>

4. Turn on the toggle button in the CRM access column to allow specific users to send data to CRM. Toggle **CRM permissions "On"** for the required user

<figure><img src="/files/nZ36HmHJI5f0nli0OoV6" alt=""><figcaption></figcaption></figure>

Once permissions are enabled, you can sync **Account/Developer segments** and manually send account/developer profiles data to your CRM.

***

### **Related Guides:**

For step-by-step instructions on integrating your CRM, refer to the following guides:

* [How to Connect and Configure HubSpot in Reo.Dev](broken://pages/qIlng8yz565Wfi80f2uC)
* [How to Connect and Configure Salesforce in Reo.Dev](/integrations/output-integrations/crm/salesforce.md)
* [How to Sync a Segment to your CRM in Reo.Dev](/faqs-troubleshooting/how-to-sync-a-segment-to-crm.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.reo.dev/faqs-troubleshooting/why-is-the-sync-to-crm-button-greyed-out.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.