Set Chrome policies for users or browsers

For administrators who manage Chrome policies from the Google Admin console.

You can enforce Chrome policies from your Admin console that apply to:

  • User accounts, to sync policies and preferences across a user's devices. Settings apply whenever the user signs in to Chrome with their managed account, on any device.  
  • Enrolled browsers, to enforce policies when users open Chrome Browser on managed Windows, Mac, or Linux computers. No sign-in is required.

Not available for Chrome devices enrolled with Chrome Kiosk licenses.

Step 1: Understand when settings apply

Exactly when your Chrome policies  are enforced depends on whether you set them for user accounts or enrolled browsers. 

Policies set for users

Available with G Suite, Chrome Enterprise Support, Chrome Enterprise Upgrades, Chromebook Enterprise devices, and Cloud Identity.

Apply when users sign in with a managed Google Account on any device:

Don't apply when users:

  • Sign in to a Google Account outside your organization, such as a personal Gmail account
  • Sign in to a Chromebook as a guest

Best for work settings and preferences that should sync across devices (work apps, home tabs, themes, etc.)

Policies set for enrolled browsers

  • Apply when users open Chrome Browser on a computer where the browser is enrolled (Windows, Mac, or Linux).
  • No sign-in is required.
  • Best for policies you want to enforce at the device level (security settings, blocked apps, etc.).

Get started: Set up Chrome Browser Cloud Management

Step 2: Make settings in your Admin console

Before you begin: To make settings for a specific group of user accounts or enrolled Chrome Browsers, put the users or browsers in an organizational unit.

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

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

    To see Devices, you might have to click More controls at the bottom.

  3. On the left, click Chrome management.
  4. Click User & browser settings
  5. On the left, select the organization that contains the users or enrolled browsers you want to make settings for.

    For all users and browsers, select the top-level organization. Otherwise, select a child. Learn more

    Important: To apply user-level policies, make sure Chrome Management is turned on for this organization. 

  6. Make the settings you want. Learn about each setting.

    Tip: Quickly find a setting by using the Search bar at the top.

    Some settings don't apply to all devices. Click lightbulb next to a setting for details.

    Settings you make for an organization are inherited by users or browsers in child organizations, unless overridden at a lower level. The Admin console marks whether a setting is Inherited or overridden (marked Locally applied).

  7. At the bottom, click Save.

    Settings typically take effect in minutes. But they might take up to 24 hours to apply for everyone.

Learn about each setting

Many settings provide the option to either enforce a policy user's cannot change, or set a default users can change. For example, you can specify a homepage everyone must use, or let people set their own home page.

Tip: Many admins leave the default settings, and only configure settings such as startup pages, new tab pages, apps and extensions, and themes. See common policy settings.
 

General

Custom avatar
Replaces the default avatar with a custom avatar. You can upload images in JPG format (.jpg or .jpeg files) and no larger than 512 KB. Other file types are not supported.
Custom wallpaper

Replaces the default wallpaper with your own custom wallpaper. You can upload images in JPG format (.jpg or .jpeg files) up to a size of 16 megabytes. Other file types are not supported.

Smart Lock for Chrome

Allows your users to unlock their Chrome device without a password using your Android phone. As long as your users and their Android device are nearby and you've enabled this setting, they no longer need to type a password to unlock their Chrome device. Requirements: Android device with version 5.0+ and a Chrome device with Chrome 40+.

Mobile

Chrome Mobile (BETA)

Warning: This is an experimental feature. Please inform your users before changing this policy. Provide feedback or report issues here.

This setting allows you to select if supported policies should apply to Chrome on mobile devices. Chrome Management needs to be turned on before enabling this setting. Once Chrome Management and this setting are enabled, users who are signed in to Chrome on Android with your organization's account will begin receiving the settings you set. To see if a policy is supported on Android check the lightbulb next to each policy in the Admin console. When a user signs out of a managed account, the policy stops applying, and the local profile of Chrome on the device is deleted.

Enrollment Controls

Device enrollment

Selecting Keep Chrome device in current location means that when you enroll the Chrome device, it will stay in the top-level organizational unit for your domain and will pull device settings from there accordingly.

Selecting Place Chrome device in user organization means that when you enroll the Chrome device, the device will be placed in the organizational unit that the enrolling user is in. The settings you've applied for that user's organizational unit will be applied to the device.

Place Chrome device in user organization is a useful setting if you need to manually enroll many devices. The device settings unique to the user's organization will be automatically added to the device, instead of requiring an additional step of manually moving each device into a specific organization after enrollment.

Note: This policy will only take effect if the device is being enrolled into the domain for the first time or the device was previously deprovisioned.

Asset identifier during enrollment

The Asset identifier during enrollment setting controls whether users can add an asset ID and location for a device when they enroll it:

  • If you select Do not allow for users in this organization, users don't have the option to enter the asset ID and location.
  • If you select Users in this organization can provide asset ID and location during enrollment, users can enter the asset ID and location of the device.

If you choose to allow users to enter the asset ID and location, the Device information screen is shown either with pre-existing data for these fields, or blank if no data already exists. The user can edit or enter the device details before they complete enrollment. This populates the asset ID and location fields in the Admin console and at chrome://policy.

Enrollment permissions

By default, users in this organization are allowed to enroll a new or re-enroll a deprovisioned device. Enrolling a new device or re-enrolling a deprovisioned device consumes an upgrade. Users can also re-enroll a device that was wiped or factory reset. Re-enrolling a device that was wiped or factory reset doesn't consume a new upgrade because the device is still managed.

Selecting Only allow users in this organization to re-enroll existing devices (cannot enroll new or deprovisioned devices) allows users to only re-enroll devices that were wiped or factory reset, but not deprovisioned. They can’t enroll new or re-enroll deprovisioned devices (anytime an upgrade would be consumed).

Selecting Do not allow users in this organization to enroll new or re-enroll existing devices prevents users from enrolling or re-enrolling any device, which includes re-enrolling through forced re-enrollment.

License selection settings

Only available in the legacy Admin console.

Selecting Apply all user policies when users sign into Chrome, and provide a managed Chrome experience turns on Chrome Browser management. Policies set for managed Google Accounts are enforced when users sign in to Chrome with their account, on any device.

For information about how to set up Chrome Browser user-level management, see Manage user profiles on Chrome Browser.

Apps and extensions

The new apps & extensions page centralizes all app & extension provisioning:

  • Allow and block apps
  • Force-install apps
  • Pin apps to the taskbar

The application settings page includes additional app & extension settings:
  • Install sources
  • Allowed app types
  • Block extensions by permission
  • Chrome Web Store homepage and permissions
Task manager

This setting allows you to block users from ending processes with the Chrome task manager. By default, users can end processes using the task manager.

Select Allow users to end processes with the Chrome task manager to allow users to end processes using the task manager.

If you select Block users from ending processes with the Chrome task manager it means users can't end processes using the task manager. If you choose this setting, users can still open the task manager, but can’t use it to end a process because the End process button is disabled (greyed out).

Site isolation

Site isolation

Turn on site isolation for managed Chrome Browser users on Chrome devices. Isolate websites and origins that you specify.

  • Turn on site isolation for all websites—Every site runs in a dedicated rendering process. All sites are isolated from each other. (Default setting if you don't specify anything)
  • Turn off site isolation for all websites, except those set below—Only the sites you specify run in a separate process. Each entry runs in a dedicated rendering process. 

You can also enter a list of origins, separated by commas, to isolate them from their respective websites. For example, you could enter https://login.example.com to isolate it from the rest of the https://example.com website.

For details, see Protect your data with site isolation.

Site isolation (Chrome on Android)

Turn on site isolation for managed Chrome Browser users on Android devices. Isolate websites and origins that you specify.

Note: Enabling site isolation on Android devices can reduce Chrome Browser performance, so it's disabled by default on Android.

  • Turn on site isolation for all websites—Every site runs in a dedicated rendering process. All sites are isolated from each other. 
  • Turn off site isolation for all websites, except those set below—Only the sites you specify run in a separate process. Each entry runs in a dedicated rendering process.
  • Allow user to choose to enable site isolation—User can choose whether to turn on site isolation.

You can also enter a list of origins, separated by commas, to isolate them from their respective websites. For example, you could enter https://login.example.com to isolate it from the rest of the https://example.com website.

Security

Password manager

When you choose Always allow use of password manager, users can have Google Chrome remember passwords and provide them automatically the next time they log in to a site. If you choose Never allow use of password manager, users cannot save new passwords but they can still use passwords that were previously saved. You can allow the user to configure password manager, or you can specify that it is always allowed or disallowed

Lock screen

Select to turn on or off the lock screen on a user’s device. If you disable the lock screen (Do not allow locking screen), the system logs out the user in cases where the lock screen would normally have activated. Idle settings that lead to the lock screen (for example, Lock screen on sleep) will also log the user out.

Quick unlock

Specifies whether users can use quick unlock modes, including PIN and fingerprint, to unlock the lock screen on their device.

Idle settings

Only available in the legacy Admin console (Idle Settings).

Idle time in minutes

To specify the amount of idle time before a user’s device goes to sleep or signs them out, enter a value in minutes. To use the system default, which varies by device, leave the box empty.

Action on idle

Select what you want the device to do after the idle time expires:

  • Sleep—if you want the device to go into sleep mode
  • Logout—if you want to sign out the current user
  • Lock Screen—if you want to lock the screen on the users device without signing them out

Action on lid close

Select if you want a user's device to go to sleep or sign them out when they close the device lid.

Lock screen on sleep

Select to lock a user’s screen when the device goes to sleep or let the user decide. If you select Allow user to configure, users configure the option in their device settings.

Incognito mode

Specifies whether users can browse in incognito mode.

Setting this policy to Disallow incognito mode prevents users from opening new incognito windows. But it does not close incognito windows that are already open, nor does it prevent users from opening new tabs in those windows.

Browser history

Controls whether the browser saves the user's browsing history.

Clear browser history

Specifies whether users can clear browser data, including their browsing and download history.

Note: Preventing users from clearing browser data doesn't guarantee that browser and download history will be kept. For example, if a user deletes their profile, their browsing history is cleared.

Force ephemeral mode

Specifies whether users browse in ephemeral mode or not.

Ephemeral mode enables your employees to work from their personal laptop or a shared device that they trust, while reducing the chances of any browsing information being left behind on their device.

Note: If you use this setting, we recommend that you do not disable Google Chrome Sync in the Admin console.

Online revocation checks

Selecting Perform online OCSP/CRL checks, Chrome devices will perform online revocation checks of HTTPS certificates.

Geolocation

Sets whether websites are allowed to track the user's physical location.

In the case of Chrome, this policy corresponds to the user options in the user's Chrome Settings under Privacy and security > Content settings > Location. Tracking the physical location can be allowed by default, denied by default, or the user can be asked each time a website requests the physical location.

In the case of Android apps running on Chrome, if this policy is set to denied by default, Android apps cannot access location information. If you set this policy to any other value or leave it unset, the user is asked to consent when an Android app wants to access location information.

Single sign-on online login frequency

Sets the frequency of forced online login flows for SAML-based single sign-on accounts. 

When you apply this policy, each time users sign out after the set frequency period, they must go through the online login flow for SAML-based single sign-on accounts.

Sign-on frequency options:

  • Every day
  • Every 3 days
  • Every week
  • Every 2 weeks
  • Every 3 weeks
  • Every 4 weeks
  • Never

Important: Before using this policy, see all requirements in Set up SAML SSO for Chrome devices.

Single sign-on

Allows you to enable or disable SAML-based single sign-on for Chrome Devices.

Important: Before using this policy, see all requirements in Set up SAML SSO for Chrome devices.

RC4 cipher suite in TLS

Allows you to temporarily enable or disable RC4 (Rivest Cipher 4) cipher suite in TLS if certain legacy servers need it.

Note: RC4 is insecure. We recommend that you reconfigure servers to support AES encryption.

Remote access clients

Configures the required domain name for remote access clients, and prevents users from changing this setting. Only clients from the specified domain can connect to the host device. If this setting is disabled, or not set, the host allows connections from authorized users from any domain.

Local trust anchor certificates

Local anchors SHA-1

Controls whether SHA-1 signed certificates issued by local trust anchors are allowed. When this setting is enabled, Chrome allows SHA-1 signed certificates as long as they successfully validate and chain to a locally-installed CA certificates.

Local anchors common name fallback

Controls whether to allow or block certificates issued by local trust anchors that are missing the subjectAlternativeName extension. When this setting is enabled, Chrome will use the commonName of a server certificate to match a hostname if the certificate is missing a subjectAlternativeName extension, as long as it successfully validates and chains to a locally-installed CA certificates. Note that this is not recommended, as this may allow bypassing the nameConstraints extension that restricts the hostnames that a given certificate can be authorized for.

Symantec Corporation's legacy PKI infrastructure

Allow certificates issued by Symantec Corporation's Legacy PKI operations to be trusted if they otherwise successfully validate and chain to a recognized CA certificate. Note, for non-Chrome OS systems, this policy depends on the operating system still recognizing certificates from Symantec's legacy infrastructure. If an OS update changes the OS handling of such certificates, this policy no longer has effect. This policy is intended as a temporary workaround to give enterprises more time to transition away from legacy Symantec certificates.

Certificate transparency URL whitelist

Specifies URLs where Certificate Transparency requirements are not enforced on certificates. So, Chrome Browser can use certificates that were issued by the Certificate Authority (CA) and are not publicly disclosed. If the CA issues illegitimate certificates for a specified URL, Chrome Browser might not detect them.

For URL syntax, see URL Blacklist filter format. Only the host name portion of the URL is matched. Wildcard host names are not supported.

Certificate transparency CA whitelist

If a certificate chain contains certificates with a specified subjectPublicKeyInfo hash, Certificate Transparency requirements are not enforced on certificates. So, Chrome Browser can use certificates that were issued by the Certificate Authority (CA) to an organization but were not publicly disclosed.

For details about how to specify a subjectPublicKeyInfo hash, see the CertificateTransparencyEnforcementDisabledForCas policy.

Certificate transparency legacy CA whitelist

If a certificate chain contains certificates issued by a legacy Certificate Authority (CA) with a specified subjectPublicKeyInfo hash, Certificate Transparency requirements are not enforced on certificates. Legacy CAs are trusted by some operating systems that run Chrome Browser, but not Chrome OS or Android. Chrome Browser can use certificates that were issued to an organization but were not publicly disclosed.

For details about how to specify subjectPublicKeyInfo hashes, see the CertificateTransparencyEnforcementDisabledForLegacyCas policy.

CPU task scheduler

Specifies whether Intel® Hyper-Threading Technology is optimized for stability or performance. Intel Hyper-Threading Technology uses processor resources more efficiently and increases processor throughput.

Session settings

Show logout button in tray

Select to show the sign out button explicitly in the shelf. This is useful for users where the sign out button needs to be emphasized for easier and faster signing out from a Chrome device. By default, the sign out button will remain accessible only from within the tray menu.

Network

Proxy mode

Specifies how Google Chrome connects to the Internet.

If you leave the setting at its default Allow user to configure, the user can change the proxy configuration in their Chrome Settings. If you choose any of the other Proxy Mode options, the user can't change the configuration.

Never use a proxy means that the Chrome device always establishes a direct connection to the Internet without passing through a proxy server. A direct connection is also the default configuration for Chrome devices, if you do not set a policy and the user doesn't change the configuration.

Always auto detect the proxy instructs the Chrome device to to determine which proxy server to connect to using the Web Proxy Autodiscovery Protocol (WPAD).

Always use the proxy specified below sets a specific proxy server for handling requests from this user. If you select this option, you need to enter the URL of the proxy server in the Proxy Server URL text box below. Format the Proxy Server URL as 'IP address:port', such as '192.168.1.1:3128'. Leave it empty for any other Proxy Mode setting.

If there are any URLs that should bypass the proxy server that handles other user requests, enter them in the Proxy Bypass List text box. If you include multiple URLs, separate them by putting one URL per line.

Always use the proxy auto-config specified below. For the Proxy Server Auto Configuration File URL, insert the URL of the .pac file that should be used for network connections.

Android apps running on Chrome OS

If you have Enabled Android Apps on supported Chrome devices, a subset of proxy settings is made available to Android apps, which they may voluntarily choose to honor (typically apps using Android System WebView or the in-built network stack will do so):

If you choose never use a proxy server, Android apps are informed that no proxy is configured.

If you choose use system proxy settings or fixed server proxy, Android apps are provided with the http proxy server address and port.

If you choose auto detect proxy server, the script URL "http://wpad/wpad.dat" is provided to Android apps. No other part of the proxy auto-detection protocol is used.

If you choose .pac proxy script, the script URL is provided to Android apps.

Supported authentication schemes

Specifies which HTTP authentication schemes are supported by Google Chrome. When a server or proxy accepts multiple authentication schemes, Google Chrome selects the supported authentication scheme with the highest security. You can override the default behavior by disabling specific authentication schemes.

  • Basic—Most insecure method with authentication handled without any encryption.
  • Digest—A challenge-response scheme that is more secure than basic authentication.
  • Negotiate—The most secure option. Use if available. Otherwise, use NTLM (NT LAN Manager).
  • NTLM—A more advanced challenge-response scheme that is more secure than digest.
SSL record splitting

Enabling this setting will allow SSL record splitting in Chrome. Record splitting is a workaround for a weakness in SSL 3.0 and TLS 1.0 but can cause compatibility issues with some HTTPS servers and proxies. This is supported only on Chrome devices.

Data compression proxy

Data Compression Proxy can reduce cellular data usage and speed up mobile web browsing by using proxy servers hosted at Google to optimize website content.

You can choose to Always enable data compression proxy or Always disable data compression proxy. The default setting is to Allow user to decide whether to use data compression proxy.

WebRTC UDP Ports

This setting allows you to specify a UDP port range to use for WebRTC connections from the user. The port range is (1024-65535) and the maximum should be greater than or equal to the minimum.

QUIC protocol

This setting allows Quick UDP Internet Connections (QUIC) protocol to be used in Chrome. QUIC is a transport protocol that reduces latency compared to Transmission Control Protocol (TCP). Learn more about QUIC protocol.

Android applications

Control Android backup and restore service

You can allow users to back up content, data, and settings from Android apps to their Google Account. This way, when users sign in to another Chrome device, they can restore their Android app data.

Google location services

Sets whether Android apps are allowed to track the user's physical location.

If this policy is set to Disable location services for Android apps in Chrome OS, Android apps cannot access location information. If set to Allow the user to decide whether an Android app in Chrome OS can use location services, the user is asked to consent when an Android app wants to access location information.

Account Management

Chrome OS version 75 and earlier

By default, users can add a secondary account (for example, their personal gmail account) to get access to more Android apps than just the ones you explicitly approved for managed Google Play. To stop users adding a second Google account, select the Google account checkbox.

Certificate Synchronization

By default, Google Chrome OS CA certificates are not synchronized to Android apps. To make Google Chrome OS CA certificates available to Android apps, select Enable usage of Chrome OS CA certificates in Android apps.

Startup

Home button

Specifies whether a home button appears in the toolbar. For Chrome, this policy corresponds to the user setting Show Home button under Appearance in the user's Chrome Settings .

Homepage

Controls whether the homepage is the new tab page, or if your users can configure this for themselves. The homepage is the URL that your users see when they click the home button mentioned above.

The default is to Allow user to configure their new homepage in their Chrome menu Menu. If you don't want to allow the user to change the homepage, you can specify that the Homepage is always the new tab page or that the Homepage is always the URL set below.

If you select Homepage is always the Homepage URL set below, enter the URL for the homepage in the text box. With this option, users can't change their homepage in Chrome.

Pages to load on startup

Enables you to specify URLs for pages that should load when users start their Chrome devices. The specified homepage appears on the active tab; any pages you list here appear on additional tabs.

Content

Safe Search and Restricted Mode

Google Safe Search for Google Web Search queries

  • Do not enforce Safe Search for Google Web Search queries - Default setting.
  • Always use Safe Search for Google Web Search queries - Selecting this option will make your selected users use SafeSearch.

Restricted Mode for YouTube

  • Do not enforce Restricted Mode on YouTube - Default setting.
  • Enforce at least Moderate Restricted Mode on YouTube - Selecting this option will make your selected users use Restricted Mode. It algorithmically limits which videos are viewable based on their content.

  • Enforce Strict Restricted Mode for YouTube - Selecting this option will make your selected users use Strict Restricted Mode. This further limits available videos.

We recommend you update your devices to the latest stable version of Chrome to be able to set restrictions on YouTube.

Screenshot

Controls whether users in your organization can take screenshots on Chrome devices. The policy applies to screenshots taken by any means, including the keyboard shortcut, and apps and extensions that use the Chrome API to capture screenshots.

If you have enabled Android apps on supported Chrome devices in your organization, screenshot policies also apply to those devices.

Client certificates

This setting allows you to specify a list of URL patterns (as a JSON string) for which sites Chrome should automatically select client certificates. If this is configured, Chrome will skip the client certificate selection prompt for matching sites if a valid client certificate is installed. If this policy isn’t set, auto-selection won’t be done for websites that request certificates.

The ISSUER/CN parameter specifies the common name of the certification authority that client certificates to be auto-selected must have as their issuer.

How to format JSON string:

{"pattern":"https://www.example.com","filter":{"ISSUER":{"CN":"certificate issuer name"}}}

Example JSON string:

{"pattern": "https://[*.]ext.example.com", "filter": {}},
{"pattern": "https://[*.]corp.example.com", "filter": {}},
{"pattern": "https://[*.]intranet.usercontent.com", "filter": {}}

Security key attestation

Specifies URLs and domains for which no prompt will be shown when attestation certificates from security keys are requested.

3D content

Controls whether the browser allows web pages to use the WebGL API and plugins. WebGL (Web-based Graphics Library) is a software library that enables JavaScript to allow it to generate interactive 3D graphics.

Cookies

Default cookie setting

Sets whether websites are allowed to store browsing information, such as your site preferences or profile information.

This setting corresponds to the user options in the Cookies section of Chrome Settings. You can allow the user to configure the option, or you can specify that cookies are always allowed, never allowed, or kept only for the duration of a user's session.

Allow cookies for URL patterns

Allows you to specify a list of URL patterns of sites that are allowed to set cookies. For example, you can put URLs in either of the following formats on separate lines: "http://www.example.com" and "[*.]example.edu". If this policy is not set, what you specify under Default cookie setting will be the global default, or a user can set their own configuration.

Block cookies for URL patterns

Allows you to specify a list of URL patterns of sites that are not allowed to set cookies. For example, you can put URLs in either of the following formats on separate lines: "http://www.example.com" and "[*.]example.edu". If this policy is not set, what you specify under Default cookie setting will be the global default, or a user can set their own configuration.

Allow session-only Cookies for URL patterns

Allows you to specify a list of URL patterns of sites that are allowed to set session-only cookies. For example, you can put URLs in either of the following formats on separate lines: "http://www.example.com" and "[*.]example.edu". The cookies after these sessions will be deleted. If this policy is not set, what you specify under Default cookie setting will be the global default, or a user can set their own configuration.

Third-party cookie blocking

Allow the user to decide is the default. If you select Allow third-party cookies, third-party cookies will be allowed on Chrome. If you disable this setting, they will be blocked.

Images

Sets whether websites are allowed to display images. For Show images on these sites and Block images on these sites, put one URL pattern on each line.

JavaScript

Sets whether websites are allowed to run JavaScript. JavaScript is commonly used by web developers to make their sites more interactive. If you disable JavaScript, some sites won't work properly.

Notifications

To enable Google Calendar notifications, follow these instructions.

Sets whether websites are allowed to display desktop notifications. Desktop notifications can be allowed by default, denied by default, or the user can be asked each time a website wants to show desktop notifications.

Note: With Chrome 64 and later, Javascript alerts are no longer allowed to interrupt users. Apps that previously used alerts, such as Google Calendar, can send notifications instead. To allow this, add the URL "calendar.google.com" into the text box Allow These Sites to Show Desktop Notifications.

Plugins

Sets whether websites are allowed to run plugins. Plugins are used by websites to enable certain types of web content that Chrome can't inherently process.

Adobe® has announced that Flash® Player® will be deprecated in December 2020. In Chrome 76 and later, Flash Player is turned off by default. For information, see Manage Flash in your users' Chrome Browsers

Enabled and disabled plugins

Enabled plugins specifies a list of plugins that are always enabled in Chrome, such as Java, and prevents users from changing this setting. Names of plugins are case-sensitive and put one plugin per line.

The names can include wildcards. The symbol '*' matches an arbitrary number of characters while '?' specifies an optional single character. The escape character is '\', so to match actual '*', '?', or '\' characters, put a '\' in front of them.

For example, enter "Chrome PDF Viewer" "*Gears*" on separate lines to enable the Chrome PDF Viewer plug-in and anything with "Gears" in its name. Note: This setting is ignored if you Block all plugins in the Plugins setting.

Disabled plugins specifies a list of plugins to block from running.

Exceptions to disabled plugins specifies a list of plugins that users can enable or disable in Chrome, even if they also match one or more entries in the Disabled plugins list.

Plugin finder

Enabling this setting allows Chrome to automatically search and install missing plugins on your users’ Chrome devices.

Plugin authorization

The default setting is that users will be asked for permission to run plugins that could compromise security. If you change it to Always run plugins that require authorization, plugins that are not outdated or disabled can run in Chrome without first asking the user for permission.

Outdated Plugins

Ask user for permission to run outdate plugins is the default setting. Selecting Disallow outdated plugins will block them from running in Chrome. Allow outdated plugins to be used as normal plugins means that the outdated plugins will be allowed to run as normal plugins.

Pop-ups

Sets whether websites are allowed to show pop-ups. Whenever the browser blocks pop-ups for a site, the blocked pop-up alert icon appears in the address bar. The user can click the icon to see the pop-ups that have been blocked.

URL blocking

URL blacklist

Prevents Chrome users from accessing specific URLs.

To configure this policy, enter up to 1,000 URLs on separate lines.

URL blacklist exceptions

Specifies exceptions to the URL blacklist.

To configure the policy, enter up to 1,000 URLs on separate lines.

URL syntax

Each URL must have a valid hostname (such as google.com), an IP address, or an asterisk (*) in place of the host. The asterisk functions like a wildcard, representing all hostnames and IP addresses.

URLs can also include:

  • The URL scheme, which is http, https, or ftp, followed by ://
  • A valid port value from 1 to 65,535
  • The path to the resource
  • Query parameters

Note the following:

  • To optionally disable subdomain matching, put an extra period before the host.
  • You cannot use user:pass fields, such as http://user:pass@ftp.example.com/pub/bigfile.iso. Instead, enter http://ftp.example.com/pub/bigfile.iso.
  • When both blacklist and blacklist exception filters apply (with the same path length), the exception filter takes precedence.
  • If an extra period precedes the host, the policy filters exact host matches only.
  • You cannot use a wildcard at the end of a URL, such as https://www.google.com/* and https://google.com/*.
  • The policy searches wildcards (*) last.
  • The optional query is a set of key-value and key-only tokens delimited by '&'.
  • The key-value tokens are separated by '='.
  • A query token can optionally end with a '*' to indicate prefix match. Token order is ignored during matching.

Examples

URL blacklist entry Result
example.com Blocks all requests to example.com, www.example.com, and sub.www.example.com
http://example.com Blocks all HTTP requests to example.com and any of its subdomains, but allows HTTPS and FTP requests.
https://* Blocks all HTTPS requests to any domain.
mail.example.com Blocks requests to mail.example.com but not to www.example.com or example.com
.example.com Blocks example.com but not its subdomains, like example.com/docs.
.www.example.com Blocks www.example.com but not its subdomains.
* Blocks all requests except for those to blacklist exception URLs. This includes any URL scheme, such as http://google.com, https://gmail.com, and chrome://policy.
*:8080 Blocks all requests to port 8080.
*/html/crosh.html Blocks Chrome Secure Shell (Also known as "Crosh Shell")
chrome://settings-frame Blocks all requests to chrome://settings.
example.com/stuff Blocks all requests to example.com/stuff and its subdomains.
192.168.1.2 Blocks requests to 192.168.1.2.
youtube.com/watch?v=V1 Blocks youtube video with id V1

Using blacklists with Android apps

If you enable Android apps on supported Chrome devices in your organization, the URL blacklist and URL blacklist exception are not honored by apps that use Android System WebView. To enforce a blacklist on these apps, define (see below) the blacklisted URLs in a text file. Then, apply the blacklist to the Android apps on an app-by-app basis.

The following example shows how to define a blacklisted URL:

{ "com.android.browser:URLBlacklist": "[\"www.solamora.com\"]" }

For apps that don’t use Android System WebView, consult the app documentation for information on how to restrict access in a similar way.

Google Drive syncing

Lets administrators configure whether or not users can sync with Google Drive on their Chrome device. Administrators can enable or disable Drive syncing, or let users choose in their local Chrome settings.

This policy has no effect on the Google Drive Android app on Chrome OS. To completely disable any syncing to Google Drive, configure this policy and do not allow the Google Drive Android app to be installed on supported Chrome devices.

Google Drive syncing over cellular

Lets administrators configure whether or not users can sync with Google Drive over a cellular connection (like a 3G connection) on their Chrome device. Administrators can enable or disable Drive syncing over cellular connections.

This policy has no effect on the Google Drive Android app on Chrome OS.

Cast

Allow users to cast from Chrome

Decide if users can use a Chromecast device to cast from a Chrome tab.

Show Cast icon in the toolbar

Specify whether Cast Cast appears on the browser toolbar in Chrome. If you select Always show the Cast icon in the toolbar, it always appears on the toolbar or overflow menu and users can't remove it.

If you don't let users cast, you can't configure this policy. The Cast icon doesn't appear on the toolbar.

Printing

Printing

You can enable or disable printing. When printing is disabled, a user won’t be able to print from the Chrome menu, extensions, JavaScript applications, etc. 

This policy has no effect on Android apps running on Chrome OS.

Print preview

Selecting Allow using print preview allows your users to see a print preview with Google Cloud Print. Selecting Always use the system print dialog instead of print preview will use the computer’s print dialog window and not Cloud Print when printing.

Google Cloud Print submission

This setting allows or blocks users from signing in to Cloud Print service to print. On Windows, Mac and Linux, turning this setting off, users will still be able to print using their system print dialog. Users won’t be able to print from Chrome OS if this setting is disabled.

Google Cloud Print proxy

Enabling this setting allows your user’s Chrome browser on their Windows, Mac, or Linux computer to act as a proxy between Google Cloud Print and the printers connected to their device. Your users can set up Google Cloud Print by going to https://www.google.com/cloudprint and signing in with their Google account.

Selecting disallow will block Chrome from sharing your device’s printers with Google Cloud Print.

Print preview default

Note: This policy is also available for managed guest sessions.

Default printer selection

To use the default system printer as the default printer for Chrome, select Use default print behavior.

To define a default printer for users, select Define the default printer. When a user prints, Chrome tries to find a printer that matches the printer type and ID or name you specify. It then selects it as the default printer.

This policy has no effect on Android apps running on Chrome OS.

Printer Types

Select the type of printer to search for and use as the default printer. To search for all types, select Cloud & Local.

Printer Matching

Select if you want to search for printers by name or ID.

Default Printer

Specify a regular expression that matches the name or ID of the printer you want to use as the default printer. The expression is case-sensitive. Printing defaults to the first printer that matches the name. For example:

  • To match a printer named Solarmora Lobby, type Solarmora Lobby.
  • To match a printer in solarmora-lobby-1 or solarmora-lobby-2, type solarmora-lobby-.$.
  • To match a printer in solarmora-lobby-guest or solarmora-partner-guest, type solarmora-.*-guest.

This policy has no effect on Android apps running on Chrome OS.

Native printers

Only available in the legacy Admin console (Native Chrome OS Printing).

Allows you to set up printing to local and network printers so that users can print without setting up Google Cloud Print. When you add a printer, it automatically appears in your users’ list of Chrome printers. For information about setting up native printing, see Manage local and network printers.

Native printers management

This setting lets you allow or block your users from adding native printers to their Chrome devices.

The default is to Allow users to add new printers. To block your users from adding printers, select Do not allow users to add new printers.

This setting works for Chrome devices running Chrome OS version 67 and later. For information about setting up native printing, see Manage local and network printers.

Default color printing mode

Specifies whether to print in color or black and white by default. Users can choose whether to print in color or black and white on individual print jobs.

Restrict color printing mode

Forces users to print in in color or black and white. Set this policy to Do not restrict color printing mode to let users choose whether to print in color or black and white.

Default page sides

Specifies whether users can print on both sides of paper. If you choose choose two-sided printing, select whether to bind pages along their long or short edge. Users can only print double sided on printers with built-in duplex capability. Users can choose whether to print on one or both sides on individual print jobs.

Restrict page sides

Forces users to print in simplex or duplex mode. Set this policy to Do not restrict duplex printing mode to let users choose whether to print on one or both sides on individual print jobs.

User Experience

Managed bookmarks

Allows you to push a list of bookmarks for the convenience of users on Chrome on all platforms including mobile devices. On Chrome Devices and Chrome on Desktop, the bookmarks will appear in a folder on Chrome's bookmark bar. The user cannot modify the contents of this folder, but can choose to hide it from the bookmark bar. On Chrome Mobile, this also appears as a folder within Bookmarks.

Bookmark bar

Allow the user to decide is the default setting. You can enable or disable this setting to determine whether or not Chrome will show a bookmark bar.

Bookmark editing

Bookmark editing allows users to add, edit or remove items from their Chrome bookmarks bar. Administrators can enable or disable this setting.

Download location

Sets the default download location on Chrome devices and specifies whether a user is allowed to modify that location. The download location policy choices are:

  • Set Google Drive as default, but allow user to change
  • Local Downloads folder, but allow user to change
  • Force Google Drive

If the user has already explicitly chosen a download location before you select one of the first two policies - Set Google Drive as default, but allow user to change or Local Downloads folder, but allow user to change, the user's original choice is respected. If the user has not already chosen a download location before you select one of these two policies, the default is set but the user can change it later.

If you select Force Google Drive (regardless of prior user choice), Google Drive is forced to be the download folder and a user is not allowed to change this setting. However, the user can still move files between local folders and Google Drive using the Files app.

This policy has no effect on Android apps running on Chrome OS. Android apps usually download to a download folder mapped to the Chrome OS downloads folder, however they may download to other locations as well.

Spell check service

Lets administrators configure whether or not spell checking web service is enabled on Chrome. Administrators can enable or disable the spell checking web service, or let users choose in their local Chrome settings.

Google Translate

Lets administrators configure whether Chrome uses Google Translate, which offers content translation for web pages in languages not specified in the Language settings on a user's Chrome device. Administrators can configure Chrome to always offer translation, never offer translation, or let users choose in their local Chrome settings.

Alternate error pages

Controls whether Google Chrome shows suggestions for the page you were trying to reach when it is unable to connect to a web address. The user sees suggestions to navigate to other parts of the website or to search for the page with Google.

Corresponds to the user option Use a web service to help resolve navigation errors, in their Chrome Settings. You can allow the user to configure the option, or you can specify that it is always on or always off.

Developer tools

Controls whether the Developer tools option appears on the Tools menu. The Developer tools allow web developers and programmers deep access into the internals of the browser and their web applications. See the Developer Tools Overview for more information about the tools.

The default for G Suite Enterprise customers is to Allow use of built-in developer tools except for force-installed extensions. This means all keyboard shortcuts, menu entries, and context menu entries that open the Developer tools or JavaScript Console are enabled in general, but are disabled within extensions that are force-installed using enterprise policy.

The default for unmanaged users is to Always allow use of built-in developer tools. To disable developer tools in all contexts, select Never allow use of built-in developer tools.

If you have enabled Android apps on supported Chrome devices in your organization, this policy will also control access to Android Developer Options. If you set this policy to Never allow use of built-in developer tools, users can’t access Developer Options. If you set this policy to any other value, or leave it unset, users can access Developer Options by tapping seven times on the build number in the Android settings app.

Form Auto-fill

Specifies whether the user can use the autofill feature to simplify the completion of online forms. The first time a user fills out a form, Google Chrome automatically saves the entered information, like the name, address, phone number, or email address, as an Autofill entry.

Corresponds to the user option Enable Autofill on the Personal Stuff page. You can allow the user to configure the option, or you can specify that it is always enabled or disabled.

DNS pre-fetching

When DNS (Domain Name System) pre-fetching is enabled, Google Chrome looks up the IP addresses of all links on a displayed web page, so links the user clicks will load faster.

Corresponds to the user option Predict network actions to improve page performance, in their Chrome Settings. You can allow the user to configure the option, or you can specify that it is always enabled or disabled.

Network prediction

Decide with this setting whether Chrome predicts network actions. You might want Chrome to use a prediction service so it loads pages faster or helps complete searches and URLs that users type in the address bar.

As an administrator, you can disable or require network prediction. Or, if you select Allow the user to decide, this turns the setting on for Chrome. Users can then change their own prediction service settings.

Multiple sign-in access

Please read Let multiple users sign in at the same time before enabling this feature.

In the case of Android apps running on Chrome, even if you set this policy to Unrestricted user access (allow any user to be added to any other user's session), only the primary user can use Android apps. If the policy has been set to Managed user must be the primary user (secondary users are allowed), then if the device supports Android apps and you have enabled them in your organization, Android apps can be used in the primary user.

Sign-in to secondary accounts

Only available in the legacy Admin console.

After signing in to their device, allows users to switch between accounts in their browser window and Google Play.

  1. Choose an option:
    • To allow users to sign in to any Google Account within the browser, select Allow users to sign-in to any secondary Google Accounts. Learn more about types of Google Accounts.
    • To block users from signing in or out of Google Accounts within the browser, select Block users from signing in to or out of secondary Google Accounts.
    • To allow users to access Google services using an account only from a list of specified G Suite domains, select Allow users to sign-in only to the G Suite domains set below.
  2. If you allow users to sign in only to specific G Suite domains:
    1. Make sure you list all of your organization’s domains. If you don’t, your users might not have access to Google services. To see a list of your domains, click organization’s domains under the domain list box.
    2. To include consumer Google Accounts, such as @gmail.com and @googlemail.com, enter consumer_accounts in the list. You can also allow access to certain accounts and block access to others. Learn more about blocking consumer accounts.
  3. If you allow users to sign in only to specific G Suite domains or block users from signing in or out in the browser, you should also:
    1. Set a sign-in restriction so that only users in your organization can sign in to devices running Chrome OS. For details, see Sign-in Restriction.
    2. Turn off guest browsing on devices. For details, see Guest mode.
    3. Prevent users from browsing in Incognito mode. See Incognito Mode.
Unified Desktop (BETA)

Note: This policy is also available for managed guest sessions and kiosk apps.

To let users span a window across multiple monitors or TVs, you can select Make Unified Desktop mode available to user. By default, this feature is turned off. Users can disable unified desktop and still use 2 external displays, but individual windows will be in one display or the other, even if the desktop is extended across both.

  • Up to 2 external displays are supported.
  • Unified desktop is intended to work across monitors of the same resolution.
  • When enabled, unified desktop is the default mode when a user connects a monitor to their device.

Omnibox search provider

Search suggest

When the user types in the address bar, Google Chrome can use a prediction service to help complete the web addresses or search terms. For example, typing new york in the address bar could bring up http://www.nytimes.com as a predicted site or [ new york city ] as a predicted search. You can allow the user to configure the option, or you can specify that it is always enabled or disabled.

Corresponds to the user option Use a prediction service to help complete searches and URLs typed in the address bar, in their Chrome Settings.

Omnibox search provider

This setting specifies the name of the default search provider. If you select Lock the Omnibox Search Provider settings to the values below, a series of text boxes will appear below that you can customize.

Omnibox search provider name

Enter a name you want to use for the Omnibox. If you don't provide one, Chrome uses the host name from the Omnibox search provider search URL.

Omnibox search provider keyword

Specifies the keyword used as the shortcut to trigger the search.

Omnibox search provider search URL

Specifies the URL of the search engine.

The URL must contain the string '{searchTerms}', which will be replaced at query time by the terms the user is searching for; for example, "http://search.my.company/search?q={searchTerms}"

To use Google as your search engine, enter:

{google:baseURL}search?q={searchTerms}&{google:RLZ}{google:originalQueryForSuggestion}{google:assistedQueryStats}{google:searchFieldtrialParameter}{google:searchClient}{google:sourceId}ie={inputEncoding}

Omnibox search provider suggest URL

Specifies the URL of the search engine used to provide search suggestions.

The URL should contain the string '{searchTerms}', which will be replaced at query time by the text the user has entered so far.

To use Google as the search engine that provides search suggestions, enter:

{google:baseURL}complete/search?output=chrome&q={searchTerms}

Omnibox search provider instant URL

Specifies the URL of the search engine used to provide instant results.

The URL should contain the string '{searchTerms}', which will be replaced at query time by the text the user has entered so far.

Omnibox search provider icon URL

Specifies the icon URL of the search provider. Note: You need to access your search provider site at least once so that the icon file will be retrieved and cached before you enable Lock the Omnibox Search Provider settings to the values below.

Omnibox search provider encodings

Specifies the character encodings supported by the search provider.

Encodings are code page names like UTF-8, GB2312, and ISO-8859-1. They are tried in the order provided. The default is UTF-8.

Hardware

External storage devices

Controls whether users in your organization can use Chrome devices to mount external drives, including USB flash drives, external hard drives, optical storage, Secure Digital (SD) cards, and other memory cards. If you set this policy to disallow external storage and a user attempts to mount an external drive, Chrome notifies the user that the policy is in effect.

When the device administrator configures the policy to Allow external storage devices (read-only), users can read files from external devices but cannot write to them. Formatting of devices is also disallowed.

This policy does not affect Google Drive or internal storage, such as files saved in the Download folder.

Audio input

Controls whether users in your organization can let websites access audio input from the built-in microphone on a Chrome device.

When a user connects an external audio input device, the audio on the Chrome device unmutes immediately.

If you have enabled Android apps on supported Chrome devices in your organization, and have this policy disabled, the microphone input is disabled for all Android apps without exceptions.

Audio output

Controls whether users in your organization can play sound on their Chrome devices. The policy applies to all audio outputs on Chrome devices, including built-in speakers, headphone jacks, and external devices attached to HDMI and USB ports.

If you configure the policy to disable audio, Chrome still shows its audio controls but users can't change them. Also, a mute icon appears.

This policy has no effect on the Google Drive Android app on Chrome OS.

Video input

Specifies whether websites can access the built-in Chrome device web cam.

Disabling video input does not disable the web cam for Google voice and video chat. To disable the web cam for Google voice and video chat, use the Allowed Apps and Extensions setting in User & browser settings to block the following extension: hfhhnacclhffhdffklopdkcgdhifgngh

If you have enabled Android apps on supported Chrome devices in your organization, this policy affects the built-in camera and can be disabled so that no Android app can access the built-in camera.

Keyboard

Determines the behavior of the top row of keys on the keyboard. If this policy is unset or set to media keys, the keyboard's top row of keys will act as media keys. If the policy is set for function keys, then the keys will act as function keys (e.g. F1, F2). In both scenarios, users will be able to change the behavior. Also, users can turn a media key to a function key (and vice versa) by holding down the search key.

User verification

Verified Mode

Require verified mode boot for Verified Access–User sessions on the devices in dev mode will always fail the Verified Access check.

Skip boot mode check for Verified Access–Allows user sessions on the devices in dev mode to work.

Service accounts which are allowed to receive user data–List email addresses of the service accounts that gain full access to the Google Verified Access API. These are the service accounts created in Google Developer Console.

Service accounts which can verify users but do not receive user data–List email addresses of the service accounts that gain limited access to the Google Verified Access API. These are the service accounts created in Google Developer Console.

For instructions on using these settings with Verified Access, admins should see Enable Verified Access with Chrome devices. Developers should see the Google Verified Access API Developer Guide.

Managed browsers

Chrome management for signed-in users

Only available in the legacy Admin console.

Selecting Apply all user policies when users sign into Chrome, and provide a managed Chrome experience turns on Chrome Browser management. Policies set for managed Google Accounts are enforced when users sign in to Chrome with their account, on any device.

For information about how to set up Chrome Browser user-level management, see Manage user profiles on Chrome Browser.

Cloud reporting

This policy controls Chrome Browser cloud reporting, which is available to admins using Chrome Browser Cloud Management. For more information, see Steps to enable browser reporting.

Once this setting is enabled, admins using Chrome Browser Cloud Management can get a detailed view in the Admin console of Chrome Browsers and extensions used in their organization.

Chrome Safe Browsing

Safe Browsing

Specifies whether Google Safe Browsing is turned on for users.

Safe Browsing in Chrome helps protect users from websites that may contain malware or phishing content. The default setting is Allow user to decide whether to use Safe Browsing. Alternatively, you can choose to Always enable Safe Browsing or Always disable Safe Browsing.

Help improve Safe Browsing

Specifies whether extended reporting is turned on and sends some system information and page content to Google to help detect dangerous apps and sites.

Safe Browsing whitelisted domains

Specifies URLs that Safe Browsing should trust. Safe Browsing will not not check for phishing, malware, unwanted software, or password reuse for listed URLs. Safe Browsing's download protection service does not check downloads hosted on these domains.

Download restrictions

Prevents users from downloading dangerous files, such as malware or infected files. You can prevent users from downloading all files or those that Google Safe Browsing identifies as dangerous. If users try downloading dangerous files, Safe Browsing shows them a security warning.

Set this policy with one of the following values:

No special restrictions—All downloads are allowed. Users still receive warnings about sites identified as dangerous by Safe Browsing. But, they can bypass the warning and download the file.

Block dangerous downloads—All downloads are allowed, except those marked with Safe Browsing warnings of dangerous downloads.

Block potentially dangerous downloads—All downloads are allowed, except those marked with Safe Browsing warnings of potentially dangerous downloads. Users cannot bypass the warnings and download the file.

Block all downloads—No downloads are allowed.

Disable bypassing Safe Browsing warnings

Specifies whether users can bypass Safe Browsing warnings and access deceptive or dangerous sites or download potentially harmful files.

Password alert

Specifies whether you can prevent users from reusing their password on dangerous websites or on websites that aren’t whitelisted by your organization. Preventing password reuse across multiple websites can protect your organization from compromised accounts.

Specify the domains that are exceptions to the URLs that appear on Google’s Safe Browsing list. Whitelisted domains are not checked for:

  • Password reuse
  • Phishing and deceptive social engineering sites
  • Sites that host malware or unwanted software
  • Harmful downloads

Specify the URLs of webpages where users usually enter their password to sign in to their account. If a sign-in process is split across 2 pages, add the URL of the webpage where users enter their password. When users enter their password, a non-reversible hash is stored locally and used to detect password reuse. Make sure that the change password URL that you specify follows these guidelines.

Chrome Management—Partner Access

Chrome Management—Partner Access

The Chrome Management—Partner Access user setting gives EMM partners programmatic access to manage user policies for Chrome and Chrome devices. Partners can use this access feature to integrate Google Admin console functionality into their EMM console.

When partner access is turned on, your EMM partner can manage individual user policies that determine your users' experience on Chrome and Chrome devices. This means that EMM partners no longer have to manage user policies by Admin console organization structure. Instead, they can use the structure configured in their EMM console. You can’t simultaneously set the same policy for the same user using partner access and the Admin Console. User level policies configured using partner access controls take precedence over organization level policies set in Admin console. To enforce policies on users at organization level, you need to uncheck the Enable Chrome Management—Partner access box.

You can also use your EMM console to set device policies. If you subscribe only to the Chrome Kiosk service, you can only set device policies.

Note: Currently, this setting is not available for G Suite for Education domains.

Related topics

Was this helpful?
How can we improve it?