1. Overview
  2. Troubleshooting & Help
  3. OAuth Configuration

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 agencies using the 297/497 HighLevel plans, managing multiple sub-accounts, or operating AI automation agencies.

 

Required Resources:

  1. HighLevel Login Credentials (Agency & Sub-Accounts)
  2. Incognito Browser/Standard Browser
  3. Access to Agency Settings and Sub-Account Marketplace
  4. Stable Internet Connection

Steps to Connect OAuth in HighLevel

1. Agency-Level OAuth Integration

  1. Navigate to Agency-Level Settings:
    • Go to Home or Settings > Integrations.
  2. Initiate OAuth Connection:
    • Click on the relevant OAuth option.
    • Log in when prompted (ensure credentials are correct).
  3. Confirm Connection:
    • If successful, a green link icon will appear next to the sub-account.
  4. 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

  1. Identify Sub-Account Status:
    • Log into the sub-account under the agency.
    • Look for a red banner indicating “No Active CRM Connection.”
  2. 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.
  3. 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

  1. Direct Login:
    • Go to app.gohighlevel.com and log into the external sub-account.
  2. Initiate Direct Connection:
    • Navigate to Settings > Integrations.
    • Click ‘Connect GHL (Direct Connection)’.
  3. Select the Sub-Account:
    • From the OAuth pop-up, select the specific sub-account name.
  4. Confirm Connection:
    • Ensure a green link icon appears.

4. Troubleshooting Complex OAuth Issues

  1. Accounts Refusing Connection:
    • Check if the sub-account is owned by your agency.
    • Use Direct Connection instead of Agency-Level Integration.
  2. Sub-Accounts Outside Agency Scope:
    • Log in directly to the external account and follow Step 3.
  3. ‘You Don’t Own This Account’ Error:
    • May occur with transferred accounts. Use Direct Connection.
  4. 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

  1. What should I do if my OAuth fails repeatedly?
    • Use the Direct Connection method and check for account ownership.
  2. 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.
  3. What if I see “You Don’t Own This Account”?
    • This may occur for transferred accounts. Use the Direct Connection process.
  4. 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.

Was this article helpful?