> ## Documentation Index > Fetch the complete documentation index at: https://docs.fuseai.com/llms.txt > Use this file to discover all available pages before exploring further. # Connecting GoHighLevel > Connect a GoHighLevel sub-account to Fuse: what to pick on HighLevel's screen, what Fuse sets up in the sub-account, what syncs in each direction, and what happens when you disconnect. Fuse connects to one GoHighLevel **sub-account** (HighLevel also calls it a location). Contacts, businesses, owners, activity and engagement sync with that sub-account, the same way they do with the other CRMs. ## Connect **1. Start in Fuse** Go to **Settings → Integrations**, find **GoHighLevel** and click **Connect**. **2. Pick one sub-account** HighLevel asks which sub-account to connect. The screen may say LeadConnector, HighLevel's white-label name. Pick a single sub-account and allow access. **3. Turn on syncing** You land back in Fuse. In **Settings → Integrations**, choose **GoHighLevel**, open the **Sync** tab, tick **Push contacts and activity** under **Push contact records**, tick the matching **Push company records** setting if you want businesses too, and click **Save**. See [contacts and companies](https://docs.fuseai.com/crm/contacts-and-companies.md). > [!NOTE] > > **One sub-account per Fuse team.** Everyone on your team who connects GoHighLevel must pick the same sub-account. If you choose several sub-accounts, or the whole agency, Fuse asks you to connect again and pick one. To move your team to another sub-account, everyone disconnects first. Connecting the new sub-account starts the sync settings over, so turn syncing back on once it is connected. ## What Fuse sets up in your sub-account GoHighLevel contacts have no LinkedIn or job title field, so Fuse adds two custom contact fields when you connect: | Field | What it holds | | - | - | | **LinkedIn URL** | The person's LinkedIn profile | | **Job Title** | Their current job title | If the sub-account already has a text field with one of those names, such as *LinkedIn*, *LinkedIn Profile* or *Title*, Fuse uses yours instead of adding its own. If one of these fields is deleted later, Fuse adds it again on the next push. Fuse also adds: * The three [engagement fields](https://docs.fuseai.com/crm/engagement.md), the first time engagement sync runs, and the `fuse-opened`, `fuse-clicked`, `fuse-replied` and `fuse-bounced` tags as people engage. * On every contact Fuse creates, the source **FuseAI** and the tag `fuseai`, so you can filter on them and start workflows from them. ## What syncs | | From Fuse to GoHighLevel | From GoHighLevel to Fuse | | - | - | - | | People | Contacts, matched on email (on phone for people without one) | Contacts with a first name: all of them on the first pull, then the ones updated since the last pull | | Companies | Businesses, matched on domain, then on name | Businesses | | Owners | The contact's **Assigned To** user, from your owner mapping | The sub-account's users, for owner mapping | | Activity | A note on the contact for each email, LinkedIn message and call | Emails, calls and calendar appointments, every hour; a contact's notes and tasks on its timeline | | Engagement | Custom fields and tags on the contact | Not synced | When Fuse updates a contact or business that already exists, it only fills fields that are empty, as with every CRM. The exception is pushing selected people or companies, which overwrites their fields (see [contacts and companies](https://docs.fuseai.com/crm/contacts-and-companies.md)). A contact Fuse matches on phone for the first time is still only filled. Phone numbers are written in international format, and a number Fuse cannot read is left out. A phone number can belong to several people, such as a company's main line, so a person with an email is never matched to someone else's contact on phone alone. If your sub-account allows only one contact per phone number and another person's contact already has that number, Fuse does not push that person rather than merge them into the other contact. A business with the same name as one of your companies but a website on another domain is treated as a different company. People are linked to the business their company is synced with, as soon as that business exists; someone you linked to another business keeps your link. If you turn off the company field on the **Fields** tab, Fuse does not link people to businesses either. A website that is a page on a shared platform, such as a Facebook page or a Yelp listing, is not used as a company's domain. Every hour, Fuse reads the emails and calls in the sub-account's conversations and the appointments on its calendars, up to a month ahead. They show on the contact's timeline in Fuse, and a campaign that skips people you have already contacted also skips someone you emailed, called or met through GoHighLevel. A contact's timeline also shows its GoHighLevel notes and tasks. Text messages are left out, and so is an appointment once it is cancelled. Opportunities and pipelines are not synced, and Fuse never writes to conversations or calendars. ## Deleted records stay deleted If you delete a contact or a business in GoHighLevel, Fuse does not create it again, even when the person or company changes in Fuse later. ## Disconnecting Disconnecting GoHighLevel in **Settings → Integrations** also uninstalls the Fuse app from the sub-account, once no one else in Fuse is still connected to it. Uninstalling the app from inside GoHighLevel disconnects Fuse for that sub-account. Either way, everything Fuse already wrote to GoHighLevel stays there, and your contacts stay in Fuse. ## Large sub-accounts HighLevel allows each app 100 requests every 10 seconds per sub-account, shared by every sync Fuse runs for it. Each sync paces itself and slows down when HighLevel asks it to, so the first sync of a large sub-account takes several passes. See [troubleshooting](https://docs.fuseai.com/crm/troubleshooting.md) for timing. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.