Set Chrome user policies

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

Not available for Chrome devices enrolled with a single-app kiosk license.

As a Chrome Enterprise admin, you can make user-level settings to enforce Chrome policies that apply when users sign in to a managed Google Account on any device. You can also sync users' work apps and preferences with their personal devices.

Before you begin

For Chrome user-level policies that you set in the Admin console to work on Windows®, Mac®, and Linux® computers, you need to turn on Managed Chrome Browser.​

Note: You don't need to turn on Managed Chrome Browser to apply policies to Chromebooks or other Chrome devices managed from your Admin console. User-level policies apply to Chrome devices, even if Chrome Management is turned off.

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

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

At the bottom, click Save.

Settings typically take effect in minutes. But they might take up to an hour to apply for everyone.

Learn about each setting

Settings apply when users sign in to a managed Google Account on Chrome Browser or a Chrome device.

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.

Mobile

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

If you're a Google Play for Education customer, the 'Apply supported user settings to Chrome on Android' box will be checked by default.

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 user 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.

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+.

Enrollment Controls

Selecting Keep Chrome device in current location means that when you enroll the Chrome device, it will stay in the top-level organization 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.

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 (default), 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.

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 a license. 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 license 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 a license 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.

Allows you to specify which URLs are allowed to install extensions, apps, and themes. For example, if a URL where you have a .crx file matches the list, a Chrome installation prompt will appear if the user clicks on the URL. Put one URL pattern on each line. For examples, see the Chrome developer site.

This policy has no effect on Android apps running on Chrome OS. To set policies for Android apps on Chrome devices that support them, see Manage Android apps on Chrome.

Choose which apps and extensions to automatically install on the users’ Chrome Browsers or devices that run Chrome OS. The apps appear when users sign in to their managed account. Users can’t remove force-installed apps. The items also bypass any list of blocked apps and extensions.

Most of the apps and extensions you need are in the Chrome Web Store, but you can also install third-party apps and extensions. To select items to force install, you must have the Chrome Web Store service turned on for your organization.

Force installing an app or extension gives it permission to access information on the device it's installed on. For example, an app might access a user's bookmarks or use their location. It can also access a device’s Directory API ID through an extension API, and use the Chrome enterprise.platformKey API without requesting permission. To change the Directory API ID for a device and stay enrolled in your domain, contact support.

This policy has no effect on Android apps running on Chrome OS. To set policies for Android apps on Chrome devices that support them, see Manage Android apps on Chrome.

Select whether you want to allow or block users from installing all apps and extensions. Based on the setting you choose, you can then make exceptions using the Allowed Apps and Extensions setting (below).

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

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

Site isolation not enabled—Users can choose whether to turn on site isolation.

Turn on site isolation for all websites (SitePerProcess)—Every site runs in a dedicated rendering process. All sites are isolated from each other.

Optionally 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.

Turn on site isolation for specific websites, set below (IsolateOrigins). Sites you specify run in a separate process. Enter the list of websites, separated by commas, that you want to isolate. Each entry runs in a dedicated rendering process. You can include sites that users sign in to as well as other sites that contain sensitive information, such as productivity sites or intranet sites.

Chrome Web Store

You can change the Chrome Web Store Homepage to a custom homepage for your users when they're signed in. You can also recommend apps and extensions for your domain in a custom collection named after your domain in the Chrome Web Store.

Checking Allow users to skip verification for websites not owned, allows user to publish apps restricted to your domain without requiring them to verify that they own the domain they're linking to. This feature is useful for creating private bookmark apps for your organization. Note that this only applies to private apps restricted to your domain.

Android applications

By default, users in this organization are not allowed to install Google Play and Android Apps on devices. Selecting Allow will give users access to the approved apps in the Google Play Store on their Chrome devices.

This setting is for older Chromebooks that you want to run Android apps. You need to complete the file system migration before you can enable Android applications for older Chrome devices. Before enabling this setting, read the article Use Android apps on older Chromebooks.

This setting only works on Chrome devices running Chrome OS version 61 and later.

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.

Security

Corresponds to the paired radio button optionsOffer to save passwords and Never save passwords, on the Personal Stuff page of the Chrome Settings.

When you enable Password Manager, users can have Google Chrome remember passwords and provide them automatically the next time they log in to a site. If you disable Password Manager, users cannot save new passwords but they can still use passwords that were previously saved. You can allow the user to configure the option, or you can specify that it is always enabled or disabled.

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.

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.

Ephemeral mode enables your employees to work from their personal laptop or a shared device that they trust, while reducing the 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.

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.

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.

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.

Session Settings

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

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.

Advanced feature: 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.

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

Startup

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. 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 Home page is always the Homepage 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.

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.

Warning for domains with devices running previous versions of Chrome

Selecting Always use Safe Search for Google Web Search queries will also turn on YouTube Restricted Mode for Chrome devices running Chrome version 40 and prior.

The Enforce at least Moderate Restricted Mode on YouTube setting will not work on devices running Chrome version 40 and prior.

The Enforce Strict Restricted Mode for YouTube setting will not work on devices running Chrome version 55 and prior.

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

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.

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.

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.

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.

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.

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.

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.

"Allow users to decide whether to allow third-party cookies" 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.

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.

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

List the plugins as a list of quoted names separated by commas. 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 plug-ins in the Plug-ins setting.

Disabled Plug-ins specifies a list of plugins to block from running.

Exceptions to Disabled Plug-ins 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 Plug-ins list.

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.

"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.

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

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.

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.

Allow users to cast from Chrome

Show Cast icon in the toolbar

This controls whether 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.

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.

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.

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.

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 printers.

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.

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.

User Experience

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.

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.

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.

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 optionUse 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.

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 is to Always allow use of built-in developer tools. If you disable the Developer tools, all keyboard shortcuts, menu entries, and context menu entries that open the Developer tools or JavaScript Console are disabled.

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 true, users can’t access Developer Options. If you set this policy to false, or leave it unset, users can access Developer Options by tapping seven times on the build number in the Android settings app.

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.

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.

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 user to configure, this turns the setting on for Chrome. Users can then change their own prediction service settings.

In the case of Android apps running on Chrome, even if you set this policy to Unrestricted user access, 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.

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

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 optionUse a prediction service to help complete searches and URLs typed in the address bar, in their Chrome Settings.

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}"

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.

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

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.

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

This policy does not affect input from external audio input devices, such as microphones that users connect to the USB port. When a user connects an external audio input device, the audio on the Chrome device unmutes immediately.

Changing the capture channel in the Google Talk settings unmutes the audio input of the built-in microphone regardless of this policy.

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.

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 settings to block the following extension: hfhhnacclhffhdffklopdkcgdhifgngh

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.

Verified Access

Enable for Enterprise extensions–Controls whether Verified Access is enabled for the user. If enabled, Chrome extensions in the user sessions can interact with the Trusted Platform Module.

Disable for Enterprise extensions–Verified Access won't work for these users, not even when the device policy applies. This is because it's not possible to run a Chrome extension outside of the user session (Verified Access in public sessions is explicitly disabled by design). If the user policy is enabled but the device policy is not, Verified Access will work, but only for the user verification.

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.

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 let your EMM Partner set device policies. If you only have Single app Chrome kiosk device management licenses in your domain, you can only set device policies.

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