Skip to main content
Verified Login is a security setting in GoGuardian Org Management that reduces security risks by validating user identities during sign-in on Google Chrome. It requires GoGuardian extensions 4.1.238 or later installed in Chrome.

​
Explore How Verified Login Works

Verified Login enhances security by requiring users to sign in to Google Chrome and checking their user identities. IT administrators can enable Verified Login in one of the following ways:
  • With domain-wide delegation: When domain-wide delegation is enabled in the Google Admin console, identities are checked when users sign in to Google Chrome. If their identity is verified, they can access the internet
  • Without domain-wide delegation: Without domain-wide delegation enabled, users sign in to Chrome and then must sign in to GoGuardian with Google, Clever, or ClassLink single sign-on (SSO) to verify their identities
For users on managed Chromebooks or Macs, domain-wide delegation allows for non-interactive verified authentication. For Windows devices, domain-wide delegation allows for this type of authentication in Chrome when users are signing into the Chrome browser. Please note that non-interactive verified authentication is not supported for extensions in Microsoft Edge or for extensions in Chrome when users are not signing into Chrome.

​
Enable Verified Login in Org Management

  1. Sign in to Org Management as a Super User.
  2. Click Product Settings > General.
  3. Toggle on Verified Login.
  4. Determine your environment’s need for domain-wide delegation. If you’re enabling it, please open a new tab and follow the instructions in the next section.
  5. Select “I’ve enabled domain-wide delegation in the Google Admin console.” (recommended)
  6. Click Enable Verified Login.

​
Configure Domain-Wide Delegation in Google Admin

  1. Sign in to Google Admin as an administrator.
  2. In the navigation menu, visit Security > Access and data control > API controls.
  3. Click Manage domain-wide delegation.
  4. Click Add new.
Google Admin console Domain-wide Delegation panel under Security > API Controls, with "Add new" and "Download client info" links
  1. Paste the following for Client ID: 1022294148666-ecrhf33feoo7cp7vtccfh616ol6cq1m5.apps.googleusercontent.com
  2. Paste each of the following for OAuth scopes: https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile
  3. Click Authorize.
Google Admin console "Add a new client ID" form with the Client ID and two OAuth scopes fields filled in

​
FAQ

What authentication methods does Verified Login support? Verified Login supports Google, Clever, and ClassLink SSO. Does Verified Login affect filtering or Beacon alerts? No. Verified Login controls sign-in behavior only. Filtering policies, GoGuardian Beacon alert configurations, and other product settings are not affected. What environments are supported? Verified Login is not available for GoGuardian extensions prior to version 4.1.238, in the following configurations, and with GoGuardian Gateway or The GoGuardian App deployments:
  • Windows: Microsoft Edge environments
  • Windows: Chrome environments where user identity comes from Active Directory or Microsoft Entra ID rather than browser sign-in
What happens to users in unsupported environments when Verified Login is enabled? Users who cannot authenticate through Google OAuth will see a standard sign-in prompt and must sign in to access the internet. Please confirm all users have access to a supported SSO method (Google, Clever, or ClassLink) before enabling the setting.
Last modified on August 19, 2026