01Who this is for
- Agency admins, need to secure agency logins and simplify credential management.
- IT managers in larger firms, require a centralized login that respects existing IdP policies.
- Founders of SaaS businesses, want to reduce password fatigue for their internal team.
02Single sign on (sso), explained
HighLevel’s SSO feature works with the OpenID Connect (OIDC) protocol. It lets an agency connect an external identity provider (IdP) and authenticate users without a separate HighLevel password. The configuration lives under Company Settings > Single Sign On (SSO) and is only visible to agency admins.
The setup flow asks for the IdP’s client identifier, secret, and either an automatic discovery URL or the individual OIDC endpoints. You also map IdP fields to HighLevel user attributes such as Remote ID, email, and email verification status. After saving, a test can be run that mimics a login, validates the configuration, and then allows you to turn the SSO toggle on.
Only login is supported; new users must already exist in HighLevel before they can use SSO. The feature is locked to OIDC today, with SAML planned for a future release.
03How businesses use single sign on (sso)
- Marketing agency. The agency adds its Auth0 application details, enables automatic discovery, and maps the IdP sub claim to the Remote ID field. After a successful test, the admin toggles SSO on and hides the email login option.
- Financial services firm. The firm creates an Azure Active Directory app registration, copies the client ID, secret, and metadata URL into HighLevel, and sets the scopes to openid profile email. Once the test passes, they enable SSO for all staff.
- Health care clinic network. The network uses Okta as its IdP, enters the Okta metadata URL, and maps the sub claim, email, and email_verified fields. After testing, they activate SSO and keep the Google login available as a fallback.
04The numbers and rules that matter
- Feature flag must be enabled before 3rd November or it is enabled by default.
- Agency must be on the $497 plan (per HighLevel's help center, checked November 2026).
- Minimum scope: Openid; profile and email are recommended.
05Before you start
- The agency must be on the $497 plan (per HighLevel's help center, checked November 2026).
- A whitelabel domain must already be configured.
- If the date is before 3 November, the SSO feature flag must be enabled on the Labs page.
06How to set up and use single sign on (sso) in HighLevel
Configure SSO
- Enable the Single Sign On feature flag on the Labs page if the date is before 3 November.
- Open Company Settings and select Single Sign On (SSO).
- Click the Enable SSO call to action to start the configuration flow.
- Enter the Client ID and Secret provided by your IdP.
- Choose whether to use the OIDC Config URL for automatic discovery or enter the Authorization URL, Token Endpoint, and User Info Endpoint manually.
- Map the required user fields: Remote ID (required), Email (required), Email Verified (required) and optionally the HighLevel ID field.
- Do not edit the Redirect URL unless correcting its format; it must follow https://<your whitelabel domain>/login/sso and be whitelisted in the IdP.
- Review all entries, save the configuration, and note that editing the configuration later will invalidate test results and disable SSO until a new test is run.
Test and enable SSO
- In the Test Status section, click the Start Test button or select Test Configuration from the three dot menu.
- When redirected to the IdP, complete the login prompt as instructed.
- After the IdP redirects back, verify that the test status shows success.
- If the test succeeded, toggle the SSO switch to enable Single Sign On for the agency.
- The Hide other login options toggle becomes active only after SSO is enabled; enable it if you want to hide email and Google login methods.
07Settings that matter
- Client ID. Identifies the application in the identity provider and tells HighLevel which IdP app to use.
- Secret. Proves to the IdP that the request originates from HighLevel during token exchanges.
- OpenID Config URL. Provides HighLevel with the metadata document that contains all OIDC endpoints automatically.
- Authorization URL. The endpoint used to start the OIDC authentication flow when manual configuration is chosen.
- Token Endpoint. Receives the authorization code and returns access and ID tokens.
- User Info Endpoint. Returns user profile information such as email and verified status after authentication.
- Scopes. Define which pieces of user data HighLevel can request; at minimum openid is required, profile and email are recommended.
- Redirect URL. The URL that the IdP redirects to after authentication; it must match the pattern https://<your whitelabel domain>/login/sso and be whitelisted in the IdP.
- Remote ID Field. The unique identifier from the IdP (e.g., sub or oid) that HighLevel uses to match users across systems.
- ID Field. Optional, HighLevel user ID for direct mapping.
- Email Field. Specifies which IdP attribute contains the user’s email address.
- Email Verified Field. Indicates whether the IdP has confirmed the email address; required for login.
08Things to know before you rely on it
- Only the OpenID Connect (OIDC) protocol is supported; SAML is on the future roadmap.
- The feature currently supports login only; new users cannot sign up via SSO and must be pre created in HighLevel.
- After 3 November, the SSO feature flag is enabled by default and does not need manual activation.
- Editing an existing SSO configuration resets test results and disables SSO until a new test passes.
- The Hide other login options toggle is inactive until SSO is enabled.
09If something goes wrong
- Something went wrong, please try again.. Check the OIDC Config URL and endpoint values, confirm the IdP app is active, and retry later.
- Email is not verified, please contact your admin.. Make sure the IdP includes the email_verified attribute set to true in the ID token.
- remoteIdField is not configured properly, please contact your admin.. Update the configuration with a valid unique identifier field such as sub or oid.
- emailField or idField is not configured properly, please contact your admin.. Provide a correct Email Field (e.g., email or userPrincipalName) or a valid ID Field.
- No user found with this email.. Create the corresponding user in HighLevel and ensure the externalUserId matches the IdP identifier.
- You are not authorized to access this account. Please contact your admin.. Link the user to the appropriate subaccount in HighLevel.
- Failed to initiate SSO test.. Retry the test. If it continues to fail, email support with your relationship number.
10How it connects to the rest of HighLevel
- Manage agency users, roles, and email security. User access settings
- Understand role permissions for admins and users. Role management
- View pricing details to confirm the $497 plan requirement (per HighLevel's help center, checked November 2026). Pricing page
Michael's take

When an agency already has a mature identity provider and a sizable team, SSO can reduce password fatigue and lower help desk tickets. Once the whitelabel domain and $497 plan are in place, the setup mainly consists of copying values from the IdP and confirming the test passes.
If the agency is tiny, uses only a few users, or does not already manage a central IdP, the effort to configure SSO may outweigh the benefits. In those cases, sticking with the native Email or Google login methods keeps things simple and avoids the extra maintenance of mapping fields and handling failed logins.