Admin settings - Google authentication

The Google Authentication page in the Authentication section of the Admin menu lets you set up Google OAuth on the Looker side.

Feature overview

If desired, Looker can perform authentication via Google OAuth, for users that have accounts registered with Google Workspace.

  • Organizations using Google Workspace can authenticate Looker users via Google accounts.
  • Users log in to Looker by authenticating with their Google account.
  • New Google accounts automatically get access to Looker. No need to separately invite users to Looker. You set the default role for new users, which can limit their access to functionality and data.
  • When enabled, Looker authenticates users only with Google OAuth unless the "alternate login" option is selected (see further instructions below).
  • A user's Google avatar appears in the navigation bar instead of the standard user symbol.

The following behaviors might affect your decision to use Google OAuth:

  • When enabling Google OAuth, the Looker instance can merge existing user accounts with the Google-registered domain, but only for accounts whose email address matches the domain. All other non-admin accounts will lose the ability to log in.
  • All users in the specified domain get access to the Looker instance.
  • Permissions for new Google users defaults to basic access for a specified list of models (which could, optionally, be access to zero models). Permissions can be updated by an admin after account creation.
  • New Looker accounts that authenticate via Google OAuth cannot switch to password authentication, even if OAuth is disabled for the Looker instance.

Preliminary requirements

Using Google OAuth requires the following:

  • A Google Workspace account for the organization.
  • A domain controlled by the organization and registered to the Google Workspace account.
  • Users with email addresses in the domain associated with the Google account.
  • Each user must have a managed user account in Google Workspace. To find and migrate any users with unmanaged user accounts, use the Transfer tool for unmanaged users.

Enabling authentication with Google OAuth

Enabling authentication with Google OAuth requires an administrator to perform steps both on the Google side, and on the Looker side, as described in the following sections.

Setup on the Google side

The steps for enabling Google OAuth on the Google side are described below. The generic description of these steps is on the Google support page on setting up OAuth 2.0. You can find documentation on the Google Dev console from the Google Cloud console Help page.

  1. Go to the Google Cloud console.

  2. Click the down arrow in the Select a project drop-down. You may see the name of an existing project in the drop-down; click the down arrow regardless, and it will take you to the option to create a new project.

  3. In the Select a project page, click New Project.

    Google displays the New Project page.

  4. Fill out the information on the New Project page and click Create.

    When Google is done creating your new project, Google returns you to the Google Cloud console and shows your new project.

  5. In the left menu, select APIs & Services > Credentials.

  6. On the Credentials page, click the Create credentials button, and select OAuth client ID from the drop-down menu.

    Google displays the Create OAuth client ID page.

  7. Google requires that you configure an OAuth consent screen, which lets your users choose how to grant access to their private data and provides a link to your organization's terms of service and privacy policy. Click Configure consent screen. (If you have configured OAuth consent for a previous project, you will not see this option, and you can skip to step 13.)

    Google displays the OAuth consent screen page.

  8. Enter the domain of your Looker instance in the Authorized domains field. For example, if Looker hosts your instance at, the domain is For customer-hosted Looker deployments, enter the domain on which you host Looker.

  9. Configure your OAuth consent screen and click Save and Continue.

    For information about configuring the Google OAuth consent screen, see the Setting up OAuth 2.0 Google support page.

  10. On the Scopes page, click Save and Continue. No additional scope configuration is required.

  11. On the Summary page, click Back to Dashboard.

    Google returns you to the Create OAuth client ID page.

  12. Under Application type, select Web application.

  13. In the Name field, enter a name for your OAuth client ID.

  14. In the Authorized JavaScript origins field, enter the URL to your Looker instance, including the https://. For example:

    • If Looker hosts your instance:
    • If you have a customer-hosted Looker instance:
    • If your Looker instance requires a port number:
  15. In the Authorized redirect URIs field, enter the URL to your Looker instance, followed by /oauth2callback. For example: or

  16. Click Create.

  17. Copy your client ID and your client secret values — you will need them to configure Looker.

Setup on the Looker side

The steps for enabling Google OAuth on the Looker side are below.

  1. From the Looker application, while logged in as an administrator, click the Admin drop-down to open the Admin menu.

  2. Under the Authentication group, click Google. Looker displays the Google Authentication page.

  3. Click Enabled to display and edit Google OAuth settings. (This does not immediately enable Google authentication; you must confirm your choice later).

  4. Enter your Google Auth Settings.

    • Client ID and Client Secret - Copy and paste these values from the Google OAuth client page, as discussed in the Google setup instructions above.
    • Domains - Your organization's Google-managed domain name(s). Any Google user in the given domain can log in to your Looker instance. If you control multiple Google domains you can enter them separated by commas.

    WARNING: Only enter Google domains controlled by your organization. Entering any other domain could open access to users of a domain you do not control.

  5. Enter Migration Options, which control behavior of the Looker instance during the transition to Google OAuth.

    • Alternate login for admins - Lets admins continue logging in with email and password, which is a useful fall-back in case of problems setting up Google OAuth. This setting is recommended and is described further below.
    • Merge by email - Converts any existing users with email addresses in the given Domains to use Google OAuth, upon their next login. This setting is recommended.
    • Roles for new users - Specifies the functionality and model access that new, non-admin users have. This list can be updated later. If left blank, new Google-authenticated users will have limited functionality inside the Looker platform until an admin adds a role to their account. Since all users within your Google domain will be able to log in to Looker, consider specifying a default role for new users that limits access appropriately.
  6. Click Test Google Authentication to use the current settings and attempt to authenticate the current browser in a new window. This action does not save the current settings or apply them to the Looker instance.

    If you are not logged into Google, you are prompted to log in and asked for consent to use your Google account information. This flow uses the custom Consent screen settings you used in the Google-side setup.

    Upon success, a User Info section displays with your name, email, domain, etc. Presence of this User Info section shows that this user would be successfully authenticated by Looker.

    Upon failure, error descriptions appear. Below are some common issues:

    • Miscopied Client ID or Client Secret. These must be carefully copied and pasted in full.
    • User is out of domain. If you see a Person Info section, but no User Info, it is probably because the user is not in the domain you specified. This shows that the person has authenticated themselves to Google correctly, but they are not using a Google account that you have chosen to allow into your Looker instance.
    • Looker URL and/or redirect URL not set up correctly in Google for your Looker.
  7. To save and apply changes, check I have confirmed the configuration above and want to enable applying it globally. Click Update.

After you enable Google authentication, users can authenticate only through Google OAuth. If you did not enable the Merge by email setting for existing accounts, every new Google-authenticated login creates a new Looker user. Existing email/password logins are not usable at the same time that Google authentication is enabled.


  • To experiment with the full authentication cycle, you can log out of Google and see that Google prompts you to log in again when you attempt to log in to Looker.

  • In Google you can click on Account in the personal drop-down (next to your email address on the top right of a Google Workspace page) to manage your personal account.

    On that management page there is a Security tab with an Account Permissions section. Clicking on Apps and websites View all lets you (as a user) see and manage the services and apps to which you have granted permissions.

    Clicking on the Looker permissions that you granted in order to log on shows the details that users see in the consent screen that you customized above. You can also click Revoke access so that the next time you log in to Looker (or test authorization) you will be re-prompted with the consent screen. You can use this workflow to help you customize your consent screen and view what users will see.


  • If a user's attempt to log in fails, first make sure the user has both a first name and a last name in their Google account. If the user has deleted either their first name or their last name from their Google account, Looker may be unable to authenticate the user with Google OAuth.

  • If a user's attempt to log in fails, and Looker displays an error such as User not in the authorized domain, check the hd field of the JSON response. If the hd field contains a domain, make sure that the domain is registered to your Google Workspace account. If the hd field is empty, use the Transfer tool for unmanaged users to invite the user to convert their account to a managed account within your domain.

  • If a user's attempt to log in fails, but Looker does not display an error message, the user may have edited their Google Workspace account name and deleted either their first or last name. In this situation, the Google Workspace account name may still look complete in the Admin console, which may not show the user's edits. To prevent this issue, Google Workspace admins can disable the Allow users to customize this setting option.

Enabling email logins while Google Auth is enabled

New Google accounts automatically get access to Looker, so there is no need to add users that are in your Google Domain.

To add a user via e-mail address that is not in your Google Domain:

  1. Enable the Alternate login for admins and specified users option on the Google Auth page
  2. Create or modify an existing user role to add the login_special_email permission
  3. Go to Add Users from the users panel (/admin/users/new)
  4. Add the e-mail address(es) you would like to include, and the roles those users should have, which must include a role with the login_special_email permission
  5. Those users are now able to log in via (hidden URL)

To enable alternate logins using the Looker API, see the Enabling the alternate login option documentation page.

Disabling Google Auth once it has been enabled

If you'd like to disable Google Authentication for your Looker instance after it has already been enabled, there are some things to think about:

  • Users who were created before Google Authentication was added, and already setup a normal email login and password, will still function.
  • Users who were created after Google Authentication was added will no longer be able to log in. While their accounts still exist, they have no way to access them, and their accounts are effectively orphaned.

This is why, currently, we suggest avoiding this route. If you must go down this path there may be a method to fix the orphaned accounts by using the Looker API. Reach out to Looker Support for additional guidance.