Set up Chrome Browser user-level management

Forcefulness 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 lxx or subsequently).

The BrowserSignin policy can only exist set as a cloud policy for Chrome Browsers enrolled in Chrome Browser Cloud Management (CBCM) using the Admin console not as a deject-based user policy. It can also be set up using a platform policies provider like Windows Group Policy. For details, see Sympathize Chrome policy management.

As a Chrome Enterprise admin, you tin force users to sign in to their managed Google Account before they use 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 applied on users' computers. Y'all can too control who can salve and synchronize Chrome Browser settings and data to their managed Google Account.

You can force everyone in your arrangement to sign in or just specific users.

Earlier you begin

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

Stride 1: Review policies

Yous can prepare one or more of the following 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 tin't sign in to Chrome Browser or sync browser information to their Google Account.
  • 1—Enable browser sign-in: Users tin 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 users to sign-in to apply the browser: Forces users to sign in to Chrome Browser before they tin can utilise information technology. Chrome Browser does not let secondary users sign in.

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 information technology.
RestrictSigninToPattern Restricts which Google Accounts can exist signed in to as primary users in Chrome Browser.

Employ it with BrowserSignin to force users with multiple Chrome profiles to sign in to a specific profile before using Chrome. Users can just sign in with profiles that lucifer the patterns you lot specify.

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

Step 2: Set the policies

Note: You don't have to set these policies to enforce browser-level policies.

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

Admin panel

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

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

  3. Click Settingsand thenUsers & browsers.

  4. To use the setting to all users and enrolled browsers, leave the top organizational unit of measurement 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 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 Strength users to sign-in to employ the browser and click OK.
  5. Enable Restrict which Google accounts are allowed to be prepare 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:
      ^.*@your-domain\.com$
    • To just allow 1 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 business relationship on Chrome browser.

In your Chrome configuration profile, add or update the following key. Then deploy the change to your users.

Fix the BrowserSignin key to two:

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

Step three: Take users sign in to Chrome

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

On user devices:

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

The next fourth dimension users open Chrome, the browser automatically opens.

Step 4: Verify policies have been applied

Subsequently you apply any Chrome policies, users need to restart Chrome Browser for the setting to accept upshot. Y'all tin 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. Check the Show policies with no value set box.
  4. For RestrictSigninToPattern andBrowserSignin, make certain Status is set to OK.
  5. For RestrictSigninToPattern and BrowserSignin, click Bear witness value and make sure that the value fields are the same every bit what y'all set in the policy.

Troubleshoot

Users can't sign in to Chrome

Some users might already be using Chrome with existing Chrome profiles before yous strength them to sign in. If that happens, merely users who are signed in when y'all 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 lot'll need to turn off the BrowserSignin policy. And so, make sure all users are signed in and follow the steps to enable the policy once 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 blueprint you specify.

Guest mode is no longer available

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

Policies don't immediately affect offline users

When users sign in to their Chrome contour for the first time, they need an internet connection. Later that, they tin employ Chrome offline. However, any policies you set are but updated when devices are connected to the internet.

Chrome might prompt users to sign in over again

When you turn on the BrowserSignin policy, Chrome sometimes prompts existing users to sign in once again because they need to reauthenticate their Chrome contour. For instance, if a user just inverse their Google Business relationship password, they might be prompted to sign in again. Electric current policies continue to utilize and are updated when the user signs in again.

Next step

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

Was this helpful?

How can we meliorate it?