Force users to sign in to Chrome Browser

Applies to managed Chrome Browsers on Windows and Mac (version 70 or later).

As a Chrome Enterprise administrator, you can force users to sign in to their Chrome profiles before they use Chrome Browser on a managed computer. Forcing users to sign in ensures that the Chrome policies and settings that you set in the Google Admin console are applied on users’ computers.

And, you can control who can save and synchronize Chrome Browser settings and data to their managed Google Account. You can force everyone in your organization to sign in or just specific users.

Before you begin

If you have an existing Chrome deployment, notify users in advance. Tell them that they need to sign in to their Chrome profile on a specific date.

Step 1: Review policies

You can set one or more of the following policies:

Policy Description and settings
BrowserSignin

Specifies whether users can sign in to Chrome Browser and sync browser information to their Google Account.

Choose one of these options:

  • 0—Disable browser sign-in: Users can’t sign in to Chrome Browser or sync browser information to their Google Account.
  • 1—Enable browser sign-in: Users can sign in to Chrome Browser and sync browser information to their Google Account. Chrome Browser automatically signs in users when they sign in to a Google service, such as Gmail.
  • 2—Force browser sign-in: Forces users to sign in to Chrome Browser before they can use it. Chrome Browser does not let secondary users sign in. Sync is turned on by default and users can’t change it. To turn off sync, use the SyncDisabled policy.

Unset: Users can sign in to Chrome Browser. When users sign in to a Google service, such as Gmail, Chrome Browser automatically signs them in. Users can change it.

RestrictSigninToPattern Restricts which Google Accounts can be signed in to as primary users in Chrome Browser.

Use it with BrowserSignin to force users with multiple Chrome profiles to sign in to a specific profile before using Chrome. Users can only sign in with profiles that match the patterns you specify.

Unset: Users can sign in to any Google Account as a primary user in Chrome Browser.

Step 2: Set the policies

Click below for steps, based on how you want to manage these policies.

Windows

Applies to Windows users who sign in to a managed account on Chrome Browser.

Using Group policies

On your Windows computer:

  1. Open your Group Policy Management Console.
  2. Go to User Configuration and then Policies and then Administrative Templates and then Google and then Google Chrome.
  3. Enable Browser sign in settings.
  4. Select Force users to sign-in to use the browser and click OK.
  5. Enable Restrict which Google accounts are allowed to be set as browser primary accounts in Google Chrome.
  6. Enter the pattern for the users you want to specify.
    • To specify all users in your domain, enter:
      ^.*@yourdomain\.com$
    • To only allow one user to sign in, enter:
      ^user-id@yourdomain\.com$
    • To allow users from both yourdomain1.com and yourdomain2.org domains to sign in, enter:
      ^.*@yourdomain1\.com$|^.*@yourdomain2\.org$
  7. Click OK.
Mac
Applies to Mac users who sign in to a managed account on Chrome Browser.
In your Chrome configuration profile, add or update the following key. Then deploy the change to your users. 

Set the BrowserSignin key to 2:

<key>BrowserSignin</key>
<dict>
<integer>2</integer>
</dict>

Step 3: Have users sign in to Chrome

After you apply the policy, users are prompted to sign in to their profile the first time they open Chrome Browser.

On user devices:

  1. Open Chrome Browser.
  2. In the User Management window, click You.
  3. Sign in to a specific Chrome profile.

The next time users open Chrome, the browser automatically opens.

Step 4: Verify policies have been applied

After you apply any Chrome policies, users need to restart Chrome Browser for the setting to take effect. You can check users’ devices to make sure the policy was applied correctly.

  1. On a managed Chrome device, browse to chrome://policy.
  2. Click Reload policies.
  3. Check the Show policies with no value set box.
  4. For RestrictSigninToPattern and BrowserSignin, make sure Status is set to OK.
  5. For RestrictSigninToPattern and BrowserSignin, click Show value and make sure that the value fields are the same as what you set in the policy.

Troubleshoot

Users can’t sign in to Chrome

Some users might already be using Chrome with existing Chrome profiles before you force them to sign in. If that happens, only users who are signed in when you turn on the policy can continue to use Chrome. All other Chrome profiles are locked. To let users sign in to their Chrome profile again, you’ll need to turn off the BrowserSignin policy. Then, make sure all users are signed in and follow the steps to enable the policy again.

Users are unexpectedly signed out of Chrome

Users are automatically signed out of Chrome if they signed in to a profile that doesn’t match the pattern you specify.

Guest mode is no longer available

When you turn on the BrowserSignin policy, users can no longer open Guest mode in Chrome. They must sign in to their Chrome profile.

Policies don't immediately affect offline users

When users sign in to their Chrome profile for the first time, they need an internet connection. After that, they can use Chrome offline. However, any policies you set are only updated when devices are connected to the internet.

Chrome might prompt users to sign in again

When you turn on the BrowserSignin policy, Chrome sometimes prompts existing users to sign in again because they need to reauthenticate their Chrome profile. For example, if a user just changed their Google Account password, they might be prompted to sign in again. Current policies continue to apply and are updated when the user signs in again.
Was this article helpful?
How can we improve it?