OAuth Configuration
Connecting OAuth in HighLevel and Troubleshooting Complex Scenarios
Background and Purpose
This SOP provides a step-by-step guide to connect OAuth in HighLevel at both the agency and sub-account levels, including solutions for common troubleshooting issues. This applies to outside agencies using the 297/497 HighLevel plans, managing multiple sub-accounts, or operating AI automation agencies.
Required Resources:
HighLevel Login Credentials (Agency & Sub-Accounts)
Incognito Browser/Standard Browser
Access to Agency Settings and Sub-Account Marketplace
Stable Internet Connection
Steps to Connect OAuth in HighLevel
1. Agency-Level OAuth Integration
Navigate to Agency-Level Settings:
Go to Home or Settings > Integrations.
Initiate OAuth Connection:
Click on the relevant OAuth option.
Log in when prompted (ensure credentials are correct).
Confirm Connection:
If successful, a green link icon will appear next to the sub-account.
Troubleshooting Missing Connection:
Use an incognito browser to log in.
Access the platform directly through
app.gohighlevel.com
(not your white-labeled domain).
2. Sub-Account OAuth Integration
Identify Sub-Account Status:
Log into the sub-account under the agency.
Look for a red banner indicating “No Active CRM Connection.”
Connect via Agency-Level Integration:
Go to the agency workspace and click ‘Connect Accounts’.
The sub-account will sync automatically if it belongs to the agency.
If Not Working (Stubborn Accounts):
Log in directly to the sub-account.
Select Connect to GHL (Direct Connection).
3. Connecting Sub-Accounts Outside the Agency
Direct Login:
Go to
app.gohighlevel.com
and log into the external sub-account.
Initiate Direct Connection:
Navigate to Settings > Integrations.
Click ‘Connect GHL (Direct Connection)’.
Select the Sub-Account:
From the OAuth pop-up, select the specific sub-account name.
Confirm Connection:
Ensure a green link icon appears.
4. Troubleshooting Complex OAuth Issues
Accounts Refusing Connection:
Check if the sub-account is owned by your agency.
Use Direct Connection instead of Agency-Level Integration.
Sub-Accounts Outside Agency Scope:
Log in directly to the external account and follow Step 3.
‘You Don’t Own This Account’ Error:
May occur with transferred accounts. Use Direct Connection.
Refresh OAuth Tokens:
Reset the integration in Agency-Level Settings > Reset Connection.
Definition of Done
All relevant sub-accounts (agency and external) display a green link icon.
The “No Active CRM Connection” banner is removed.
Accounts are successfully connected via Agency or Direct OAuth Integration.
FAQs
What should I do if my OAuth fails repeatedly?
Use the Direct Connection method and check for account ownership.
Can I connect a sub-account that is not owned by my agency?
Yes, use Direct Connection and log in directly to the sub-account.
What if I see “You Don’t Own This Account”?
This may occur for transferred accounts. Use the Direct Connection process.
How do I confirm a successful connection?
Look for the green link icon next to the sub-account.
Summary
This SOP explains how to connect OAuth in HighLevel at the agency and sub-account levels, including external sub-accounts and troubleshooting common connection errors. The process includes logging in directly, using Agency-Level Integration, and utilizing Direct Connection for stubborn or external accounts. A successful connection removes red banners and displays a green link icon, ensuring seamless CRM functionality.