HighLevel: Control Google Sign-In on Your Client Portal

HighLevel published a changelog update for Control Google Sign-In on Your Client Portal. HighLevel now lets sub-accounts control whether the "Sign in with Google" option appears on the Client Portal sign-up and login pages.

What changed

HighLevel now lets sub-accounts control whether the "Sign in with Google" option appears on the Client Portal sign-up and login pages.

Admins can enable or disable Google Sign-In directly from the Client Portal app permissions — giving businesses the flexibility to align their sign-up experience with their own compliance and data-handling requirements (for example, GDPR and other European regulatory considerations).

Why it matters for agencies and VAs

Agencies and VAs are usually the first people asked why a screen changed, why a workflow loads differently, or whether a new setting should be adopted. Tracking this early keeps client support, SOPs, and implementation calls cleaner.

How to use it

1. Open the affected HighLevel feature and confirm how the change behaves in a real sub-account.
2. Update any client-facing SOP, Loom, or checklist that mentions the old behavior.
3. Flag the change only for clients whose workflows, calendars, payments, sites, conversations, SaaS, or AI setup are affected.

Certified GHL Admin operator take

As a Certified GHL Admin, my read is simple: do not treat this as trivia. If the feature is part of a client fulfillment path, test it once, document the operational impact, then decide whether it deserves a client note or an internal-only SOP update. Source category: client portal.