Set up Chrome Browser user-level direction

Strength users to sign in to Chrome Browser (user policies only)

For administrators who manage user-level Chrome Browser policies from the Google Admin console.

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

The BrowserSignin policy tin but be set as a cloud policy for Chrome Browsers enrolled in Chrome Browser Cloud Management (CBCM) using the Admin console not as a cloud-based user policy. It tin also be gear up using a platform policies provider like Windows Group Policy. For details, meet Understand Chrome policy management.

As a Chrome Enterprise admin, you can force users to sign in to their managed Google Account before they utilise Chrome Browser on a managed computer. Forcing users to sign in ensures that youruser-level Chrome policies and settings in the Google Admin console are practical on users' computers. You can too control who tin relieve and synchronize Chrome Browser settings and data to their managed Google Account.

You lot tin can force anybody in your organisation to sign in or simply specific users.

Before y'all brainstorm

  • Make certain browser management is turned on for your organisation. For details, meet Plow on Chrome Browser management (user policies only).
  • If you have an existing Chrome deployment, notify users in advance. Tell them that they need to sign in to their managed Google Business relationship on a specific date.

Step 1: Review policies

You lot tin can ready ane or more than of the post-obit policies:

Policy Description and settings
BrowserSignin

Specifies whether users tin sign in to Chrome Browser and sync browser data 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 tin 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 every bit Gmail.
  • 2—Force users to sign-in to use the browser: Forces users to sign in to Chrome Browser before they tin employ it. Chrome Browser does non let secondary users sign in.

Unset: Users can sign in to Chrome Browser. When users sign in to a Google service, such every bit Gmail, Chrome Browser automatically signs them in. Users can alter it.
RestrictSigninToPattern Restricts which Google Accounts tin exist signed in to as chief users in Chrome Browser.

Employ it with BrowserSignin to force users with multiple Chrome profiles to sign in to a specific contour 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.

Stride two: Set up the policies

Annotation: Yous don't have to set these policies to enforce browser-level policies.

Click below for steps, based on how yous desire to manage these policies.

Admin console

Can apply for signed-in users on any device or enrolled browsers on Windows, Mac, or Linux. For details, see Understand when settings apply.

  2. From the Admin console Home page, get to Devices and then Chrome.

  3. Click Settingsand thenUsers & browsers.

  4. To use the setting to all users and enrolled browsers, leave the acme organizational unit selected. Otherwise, select a child organizational unit.

  5. Go to Sign-in settings.

  6. For Browser sign-in settings, select Force users to sign-in to use the browser.

  7. Click Save.

Windows

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

Using Group policies

On your Windows figurer:

  1. Open your Group Policy Direction 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 utilize the browser and click OK.
  5. Enable Restrict which Google accounts are allowed to be set equally browser primary accounts in Google Chrome.
  6. Enter the pattern for the users you desire to specify.
    • To specify all users in your domain, enter:
      ^.*@your-domain\.com$
    • To but allow ane user to sign in, enter:
      ^user-id@your-domain\.com$
    • To allow users from both your-domain1.com and your-domain2.org domains to sign in, enter:
      ^.*@your-domain1\.com$|^.*@your-domain2\.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 together or update the following key. Then deploy the change to your users.

Set the BrowserSignin cardinal to two:

<key>BrowserSignin</key>
<dict>
<integer>ii</integer>
</dict>

Pace 3: Take users sign in to Chrome

Subsequently y'all apply the policy, users are prompted to sign in to their profile the starting time fourth dimension they open up Chrome Browser.

On user devices:

  1. Open Chrome Browser.
  2. In the User Management window, click Y'all.
  3. Sign in to a specific Chrome contour.

The side by side time users open Chrome, the browser automatically opens.

Pace 4: Verify policies accept been applied

After you lot apply any Chrome policies, users need to restart Chrome Browser for the setting to take effect. You can bank 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. Bank check the Show policies with no value set box.
  4. For RestrictSigninToPattern andBrowserSignin, make sure Status is fix to OK.
  5. For RestrictSigninToPattern and BrowserSignin, click Evidence value and brand sure that the value fields are the same equally what you set up in the policy.

Troubleshoot

Users tin can't sign in to Chrome

Some users might already be using Chrome with existing Chrome profiles before you forcefulness them to sign in. If that happens, but users who are signed in when yous turn on the policy can continue to employ 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 certain 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 y'all specify.

Guest mode is no longer available

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

Policies don't immediately bear upon offline users

When users sign in to their Chrome profile for the beginning time, they demand an internet connectedness. Afterward that, they can use Chrome offline. However, any policies you set are but updated when devices are connected to the cyberspace.

Chrome might prompt users to sign in again

When you plough on the BrowserSignin policy, Chrome sometimes prompts existing users to sign in once again considering they need to reauthenticate their Chrome contour. For example, if a user just changed their Google Account password, they might exist prompted to sign in once again. Current policies go along to apply and are updated when the user signs in once again.

Next step

  • Set user-level Chrome policies
  • Set up Chrome Browser Cloud Management
  • Encounter all Cloud-managed Chrome Browser topics

Was this helpful?

How can nosotros meliorate it?