Disconnect CRM after connecting to OutboundSync?
When to use this guide: Use this guide when expected sync behavior is missing, delayed, or incorrect.
The behavior differs between HubSpot and Salesforce, because each platform handles integration permissions differently.
Quick Summary
Section titled “Quick Summary”| CRM | Can the connecting user be removed after setup? |
|---|---|
| HubSpot | ✅ Yes — the sync will continue working |
| Salesforce | ❌ No — removing the user will break the integration |
HubSpot
Section titled “HubSpot”When connecting HubSpot to OutboundSync, Super Admin permissions are required to authorize the integration. After the connection is established, those permissions do not need to remain in place.
If the user who originally authorized the connection loses Super Admin access or leaves the organization, the integration will continue working normally because it operates at the HubSpot account level, not the individual user level.
To remove the HubSpot connection, the OutboundSync app itself must be uninstalled from your HubSpot account.
Agencies handing a HubSpot portal to a client after setup should follow Agency and consultant access handoff.
Salesforce
Section titled “Salesforce”The OutboundSync connection is tied to the specific Salesforce user account that authorized the integration, which must have System Administrator permissions. If that user is deactivated or removed, the integration will stop working.
Because of this, the Salesforce user who created the integration must remain active. This is especially important when an agency sets up the integration on behalf of a client, since removing the agency user later will break the connection.
You can create a dedicated Integration User in Salesforce to “own” the integration for better long-term account access/stability.
If your Salesforce connection has stopped working and you need to reconnect, see Re-authorize your Salesforce account.
For the full agency and consultant handoff checklist (OutboundSync permissioning plus Salesforce integration-user ownership), see Agency and consultant access handoff.
