Set Chrome device policies

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

As a Chrome Enterprise admin, you can control settings that apply when people use a managed Chrome device, such as a Chromebook. Device-level settings apply for anyone who uses the device, even if they sign in as a guest or with a personal Gmail account.

Specify device settings

Before you begin: To make settings for a specific group of devices, put the devices 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.

    If you don't see Devices on the Home page, at the bottom, click More controls.

  3. On the left, click Chrome management.
  4. Click Device settings.
  5. To apply the setting to all users and enrolled browsers, leave the top organizational unit selected. Otherwise, select a child organizational unit.
  6. Make the settings you want. Learn about each setting.

    Tip: Quickly find a setting by entering text in Search settings at the top.

    You see Inherited if a setting is inherited from a parent. Or, you see Locally applied if the setting is overridden for the child.

  7. Click Save.

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

Learn about each setting

For managed Chromebooks and other devices that run Chrome OS.

If you see Device-specific setting Device-specific setting, the setting is only available with specific device types​. Some settings aren’t available with single-app kiosks.

Enrollment and Access

Forced re-enrollment
Automatically set to Force device to re-enroll with user credentials into this domain after wiping by default. If the setting is on and you don't want a Chrome device to re-enroll in your domain, you need to deprovision the device. To turn the setting off, select Device is not forced to re-enroll after wiping. For details on forced re-enrollment, see Force wiped Chrome devices to re-enroll.
Verified access

This setting enables a web service to request proof that its client is running an unmodified Chrome OS that’s policy-compliant (running in verified mode if required by the administrator). The setting includes the following controls:

  • Enable for content protection–Ensures that Chrome devices in your organization will verify their identity to content providers using a unique key (Trusted Platform Module). Also ensures that Chromebooks can attest to content providers that they’re running in Verified Boot mode.
  • Disable for content protection–If this control is disabled, some premium content may be unavailable to your users.

For more details for admins, go to Enable Verified Access with Chrome devices. For developers, go to the Google Verified Access API Developer Guide.

Verified mode
  • Require verified mode boot for verified access–Devices must be running in verified boot mode for device verification to succeed. Devices in Dev mode will always fail the verified access check.
  • Skip boot mode check for verified access–Allows devices in Dev mode to pass the verified access check.
  • Service with full access–Lists email addresses of the service accounts that gain full access to the Google Verified Access API. These are the service accounts created in Google Cloud Platform Console.
  • Service with limited access–Lists email addresses of the service accounts that gain limited access to the Google Verified Access API. These are the service accounts created in Google Cloud Platform Console.

For more details for admins, go to Enable Verified Access with Chrome devices. For developers, go to the Google Verified Access API Developer Guide.

Disabled device return instructions

This setting controls the custom text on the screen of a device that’s disabled because it was lost or stolen. We recommend that you include a return address and contact phone number in your message so that users who see this screen are able to return the device to your organization.

Integrated FIDO second factor

Specifies whether users can use 2-Factor Authentication (2FA) on devices with a Titan M security chip.

Sign-in Settings

Guest mode

Controls whether to allow guest browsing on managed Chrome devices. If you select Allow guest mode (the default), the main sign-in screen offers the option for a user to sign in as a guest. If you select Disable guest mode, a user must sign in using a Google Account or G Suite account. When a user signs in using guest mode, your organization's policies are not applied.

Sign-in restriction

Chrome version 28 and later, but users with prior versions of Chrome can still sign in. Intended for devices that use managed guest sessions.

Allows you to control which users can sign in to a managed Chrome device.

Considerations

  • Users can use the device regardless of which restriction setting you use if you have guest browsing or managed guest sessions enabled.
  • If you have enabled Android apps on supported Chrome devices in your organization, this policy alone will not control whether additional accounts may be added within Android settings in a user session. You can control that using Account Management.

Choose an option:

  • Restrict sign-in to list of users—If the text box is left empty, any user with a Google Account or G Suite account can sign in and the +Add user button is available on the sign-in screen.
    If you include users in the text box, only those users can sign in. Other users get an error message. Enter users with their primary email address. Separate the addresses with commas. The names can include the wildcard * (to match any set of characters). The +Add user button will be available as long as not all of the users in your list have been added to the device, or if you use a wildcard such as *@yourdomain.com. If all of your specific users have been added to the device, then the +Add user button will not be available.
  • Do not allow any user to sign in—No one can sign in to the Chrome device with their Google Account or G Suite account. The +Add user button is unavailable.
Autocomplete domain

Lets you choose a domain name to present to users on their sign-in page so that they don't need to enter the @domain.com part of their username during sign-in.

To turn the setting on, from the list, select Use the domain name, set below, for autocomplete at sign-in and enter your domain name.

Sign-in screen

Specifies whether the Chrome device's sign-in screen displays the names and pictures of users who have signed in to the device.

  • Always show user names and photos—Lets users choose their user account on the sign-in screen.
  • Never show user names and photos—Prevents user accounts from being displayed on the sign-in screen. Users must enter their Google Account username and password each time they sign in to their Chrome device. If you have SAML single sign-on (SSO) for Chrome devices and send users directly to the SAML identity provider (IdP) page, Google redirects them to the SSO sign-in page without entering their email address.

If users are enrolled in 2-Step Verification, they’re prompted to perform their second verification step each time they sign in to their Chrome device.

Device off hours

Allows you to set a weekly schedule when the guest browsing and sign-in restriction settings don’t apply to managed devices running Chrome OS. 

For example, school admins can block guest browsing or only allow users with a username ending in @schooldomain.edu to sign in during school hours. Outside of school hours, users can browse in guest mode or sign in to their device using an account other than their @schooldomain.edu account.

Device wallpaper image

Chrome version 61 and later

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

User data

Specifies whether enrolled Chrome devices delete all locally-stored settings and user data every time a user signs out. Data the device synchronizes persists in the cloud but not on the device itself. If you set it to Erase all local user data, the storage available to the users is limited to half the RAM capacity of the device.

Single sign-on IdP redirection

Devices must have SAML SSO. See Configure SAML single sign-on for Chrome devices.

To allow your single sign-on (SSO) users to navigate directly to your SAML identity provider (IdP) page instead of first having to enter their email address, you can enable the Single sign-on IdP redirection setting.

Single sign-on cookie behavior

Devices must have SAML SSO. See Configure SAML single sign-on for Chrome devices.

To allow your single sign-on (SSO) users to sign in to internal websites and cloud services that rely on the same identity provider (IdP) on subsequent sign-ins to their Chrome device, you can enable SAML SSO cookies. 

SAML SSO cookies are always transferred on first sign-in, but if you want to transfer cookies in subsequent sign-ins, you need to enable this policy.

If you have enabled Android apps on supported Chrome devices in your organization and have this policy enabled, cookies are not transferred to Android apps.

Single sign-on camera permissions

Devices must have SAML SSO. See Configure SAML single sign-on for Chrome devices.

Important: If you enable this policy, you grant third parties access to their users' cameras on their users' behalf. Ensure that you have proper consent forms in place for users—the system does not show end users any consent forms if permission is granted using this policy.

To give third-party apps or services direct access to the user’s camera during a SAML single sign-on (SSO) flow, on behalf of your SSO users, you can enable SSO camera permissions. This setting can be used by a third-party identity provider (IdP) to bring new forms of authentication flows to Chrome devices.

To add IdPs to the whitelist, enter the URL for each service on a separate line. 

If you are using this setting to set up Clever Badges™ for your organization, refer to the Clever support site for more information.

Single sign-on client certificates

Devices must have SAML SSO. See Configure SAML single sign-on for Chrome devices.

Allows you to control client certificates for single sign-on (SSO) sites.

You enter a list of URL patterns as a JSON string. Then, if an SSO site matching a pattern requests a client certificate and a valid device-wide client certificate is installed, Chrome automatically selects a certificate for the site.

If the site requesting the certificate doesn’t match any of the patterns, Chrome doesn’t provide a certificate.

How to format the JSON string:

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

The ISSUER/CN parameter (certificate issuer name above) specifies the common name of the Certificate Authority (CA) that client certificates must have as their issuer to be autoselected. If you want Chrome to select a certificate issued by any CA, leave this parameter blank by entering “filter”:{}.

Examples:

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

Accessibility Control

Allows you to control accessibility settings on the sign-in screen. Accessibility settings include large cursor, spoken feedback, and high-contrast mode. 

  • Turn off accessibility settings on the sign-in screen upon sign-out—Restores accessibility settings to the defaults when the sign-in screen is shown or the user remains idle on the sign-in screen for one minute.
  • Allow user to control accessibility settings on the sign-in screen—Restores the accessibility settings that users turned on or off on the sign-in screen, even if the device is restarted.
Sign-in Language

Specifies what language the Chrome device’s sign-in screen displays. You can also allow users to choose the language.

Sign-in Keyboard

Specifies which keyboard layouts are allowed on the Chrome device’s sign-in screen.

Device update settings

Important: Before changing any of the auto-update settings below, review Manage updates on Chrome devices.

Auto update settings

Automatic updates

Software support is available only for the latest version of Chrome OS.

Specifies whether Chrome devices automatically update to new versions of Chrome OS as they are released. Allow auto-updates is strongly recommended. The last several versions of Chrome OS are listed.

To stop updates before a device is enrolled and restarted: 

  • On the End User License Agreement screen, press Ctrl+Alt+E. If you don’t, downloaded updates that should have been blocked by a policy might be applied when the user restarts the device.

Restrict Google Chrome version to at most

Software support is available only for the latest version of Chrome OS.

Prevents Chrome devices from updating to versions of Chrome OS beyond the version number specified. Using this setting is recommended only if a later version of Chrome OS causes compatibility issues with tools in your domain that need to be resolved prior to updating the Chrome OS version.

You can configure one or more of your Chrome devices to use the Dev or Beta channel to help identify compatibility issues in upcoming versions of Chrome. For more information, see Chrome release best practices.

Randomly scatter auto-updates over

Specifies the approximate number of days over which managed Chrome devices in your organization download an update following its release. The downloads occur at various times during this period to avoid causing traffic spikes that can impact old or low-bandwidth networks. Devices that are offline during this period download the update when they go back online.

Set this policy to its default (none) or a low number unless you know that your network can't handle traffic spikes. If you do, users benefit from new Chrome enhancements and features quicker. You also minimize the number of concurrent versions in your organization to simplify change management during the update period.

Auto reboot after updates

Automatic restarts work only when the device is configured as a managed guest session kiosk.

  • Allow auto-reboots—After a successful auto-update, the Chrome device restarts when the user next signs out. 
  • Disallow auto-reboots—Disables autorestarts.

Updates over cellular

Specifies the types of connections that Chrome devices can use when they automatically update to new versions of Chrome OS. By default, Chrome devices automatically check for and download updates only when connected to Wi-Fi or Ethernet. Select Allow automatic updates on all connections, including cellular to let Chrome devices automatically update when they’re connected to a mobile network.

App-controlled updates

You can allow a specific app to control the Chrome OS version on a device. This allows you to prevent devices from updating to versions of Chrome beyond the version number specified by the app.

If you click Select an app, you can search for and select apps in the Chrome Web store.

Kiosk-controlled updates

Cannot be used if you’re using an autolaunched kiosk app to control the Chrome OS version on a device

You can allow one specific kiosk app to control the Chrome OS version on a device to prevent devices from updating to versions of Chrome beyond the version number specified by the app. In the manifest file, the app must include "kiosk_enabled": true and specify the required Chrome OS version, required_platform_version. It can take up to 24 hours for updates in the manifest file to take effect on devices. For information on configuring settings in the app’s manifest file, see Let kiosk app control Chrome OS version.

If you click Select an app, you can search for and select kiosk apps in the Chrome Web store.

Release channel

Cannot be set for the top-level organizational unit. You must set by organizational unit.

Lets users test the latest Chrome features by letting them switch the release channel to a more experimental version. You can select a channel for users. To allow users to select a channel themselves, select  Allow user to configure. For users to select the Dev channel, you must set the Developer Tools user policy to Always allow use of built-in developer tools. For details see Chrome Browser release channels and Developer tools.

Kiosk settings

Before you can configure any kiosk settings, you need to enroll the device as a kiosk.

Related topics: Enroll Chrome devices, View Chrome OS device details, View and configure apps and extensions, and Set app and extension policies

Managed guest sessions

Before you can configure a Chrome device as a managed guest session, you need to make sure managed guest session settings exist for the organizational unit that the device is assigned to. Then, to set the kiosk as a managed guest session kiosk, you select Allow managed guest sessions.

For information about creating managed guest session settings, see Managed guest session devices.

To automatically launch a managed guest session on a Chrome device, select Auto-launch managed guest sessions and set Auto-launch delay to 0.

Enable device health monitoring

Only available for managed guest sessions that automatically launch on Chrome devices

Select Enable device health monitoring to allow the health status of the kiosk to be reported. After doing this, you can check if a device is online and working properly.

For more information, see Monitor kiosk health

Enable device system log upload

Only available for managed guest sessions that automatically launch on Chrome devices

Important: Before using this setting, you must inform the users of managed kiosk devices that their activity might be monitored and data might be inadvertently captured and shared. Without notification to your users, you are in violation of the terms of your agreement with Google.

Select Enable device system log upload to automatically capture system logs for kiosk devices. Logs are captured every 12 hours and uploaded to your Admin console, where they’re stored for a maximum of 60 days. At any one time, 7 logs are available to download—one for each day for the past 5 days, one for 30 days ago, and one for 45 days ago.

For more information, see Monitor kiosk health.

Screen rotation (clockwise)

Only available for managed guest sessions that automatically launch on Chrome devices

To configure screen rotation for your kiosk devices, select your desired screen orientation. For example, to rotate the screen for a portrait layout, select 90 Degrees. This policy can be overridden by manually configuring the device to a different screen orientation.

Kiosk device status alerting delivery

To get alerts when a Chrome kiosk device is turned off, check the Receive alerts via email box or the Receive alerts via SMS box, or both boxes.

Kiosk device status alerting contact info

Get status updates about your Chrome kiosk devices. 

  • Get updates by email—Next to Alerting emails, enter one email per line.
  • Get updates by SMS—Next to Alerting mobile phones, enter one phone number per line.

User and device reporting

Device reporting

Device state reporting

This setting is on by default. Specifies whether Chrome devices enrolled in your domain report their current device state, including firmware, Chrome and platform version, and boot mode. 

If you enabled Android apps on supported Chrome devices in your organization, this policy has no effect on logging or reporting done by Android.

Related topics: View Chrome OS device details, Use Android apps on Chrome devices

Device user tracking

This setting is on by default, but does not take effect if the User data setting, which erases all user info on a device when a user signs out, is enabled.

Related topic: View Chrome OS device details

Inactive device notifications

Inactive device notification reports

Get email reports about inactive devices in your domain. The reports contain:

  • Information on all inactive devices in your domain (devices that haven’t synced since the time specified in Inactive Range)
  • The total number of inactive devices, including how many are recently inactive, for each organizational unit.
  • A link to detailed information on each device, such as the organizational unit, serial number, asset ID, and last sync date if there are less than 30 devices that are newly inactive.

Note: Some information in the reports might be delayed up to one day. For example, if a device synced in the last 24 hours but was previously inactive, it might still appear on the inactive list, even though it is now active.

Inactive Range (days)

If a device doesn't check in to the management server for longer than the number of days you specify, then that device is considered inactive. You can set the number of days to any integer greater than one.

For example, if you want to mark all devices that haven’t synced in the last week as inactive, next to Inactive Range (days), enter 7.

Notification Cadence (days)

To specify how often inactive notification reports are sent, enter the number of days in the Notification Cadence field.

Email addresses to receive notification reports

To specify email addresses that get notification reports, enter the addresses (one per line).

Anonymous metric reporting

Specifies whether the Chrome device sends Google usage statistics and crash reports whenever a system or browser process fails.

Usage statistics contain aggregated information, such as preferences, button clicks, and memory usage. They don't include web page URLs or any personal information. Crash reports contain system information at the time of the crash and might contain webpage URLs or personal information, depending on what was happening at the time of the crash.

If you have enabled Android apps on supported Chrome devices in your organization, this policy also controls Android usage and diagnostic data collection.

Power and shutdown

Power management

Controls whether a Chrome device that is showing a sign-in screen (no user is signed-in) should go to sleep or shut down after some time or if it should continuously stay awake. This setting is useful for Chrome devices that are used as kiosks to make sure they never shut down.

Scheduled Reboot

Currently only works with kiosk devices with a sign-in screen showing

Allows you to specify the number of days after which a device restarts. Sometimes, the device might not restart at the same time of day or the restart might be postponed until the next time a user signs out. If a session is running, then a grace period of up to 24 hours applies.

Google recommends that you configure kiosk apps to shut down at regular intervals to allow the app or device to restart. For example, you can schedule the app to shut down every day at 2 AM.

Allow shutdown

You can select:

  • Allow users to turn off the device using either the shut down icon or the physical power button (Default)—Users can turn off the device using the button on the device, keyboard, mouse, or screen.
  • Only allow users to turn off the device using the physical power button—Users turn off the device using the button on the device and cannot turn off the device using the keyboard, mouse, or screen.

This setting might be useful in specific deployment scenarios, such as if the Chrome device is being run as a kiosk or digital sign.

Peak shift power management

Device-specific setting  Currently available with Dell Latitude 5400 and 5300 2-in-1 Chromebook Enterprise devices

Allows you to reduce the power consumption by automatically switching the Chromebook to battery power. 

If you enable Peak shift power management:

  1. Under Peak Shift Battery Threshold, enter a percentage value between 15 and 100. If the battery percentage is above the value that you specify, the device runs from the battery.
  2. To set a daily start and end time to run Peak shift power management:

    1. Under Peak shift day configuration, select a start and end time. During the times, unless the device reaches the threshold set above, the AC power will not be used.
    2. Under Charge start time, select a time to start charging the battery.
Primary battery charge configuration

Device-specific setting Currently available with Dell Latitude 5400 and 5300 2-in-1 Chromebook Enterprise devices without a Dell Long Cycle Life battery

Allows you to configure the primary battery charge mode. Choose from:

  • Standard—Fully charges the battery at a standard rate
  • Adaptive—Battery adaptively optimized based on typical usage pattern
  • Express Charge—Battery charges over a shorter period
  • Primarily AC—Extends battery life by charging mainly from AC
  • Custom—Lets you enter a time to start and stop charging based on battery percentage

Note: You cannot use this setting at the same time as the Advanced Charge battery mode setting.

Advanced Charge battery mode

Device-specific setting  Currently available with Dell Latitude 5400 and 5300 2-in-1 Chromebook Enterprise devices

Allows you to prolong the usable life of a battery by charging to full capacity only once per day.  For the remainder of the day, batteries are in a lower charge state that’s better for storage, even when the system is plugged in to a direct power source. 

If you enable Advanced Charge battery mode, enter a daily start and end time.

Boot on AC
Device-specific setting  Currently available with Dell Latitude 5400 and 5300 2-in-1 Chromebook Enterprise devices
If you enable Boot on AC and a device shuts down, it will turn on when plugged in to an AC adapter. 

Note: If the device is connected to a Dell WD19 docking station that’s connected to power, the Chromebook will turn on even if the setting is disabled.

USB Powershare
Device-specific setting  Currently available with Dell Latitude 5400 and 5300 2-in-1 Chromebook Enterprise devices

Allows users to charge other devices, such as a mobile phone, through a special USB port if the Chromebook is turned off and connected to power. All USB ports charge devices when the Chromebook is in Sleep mode. 

Other

Google Cloud Print

Allows any user of the Chrome device to print using Google Cloud Print. This setting is popular for Chrome devices configured for managed guest sessions.

  1. Next to Choose which Cloud printers to enable, click Manage.
  2. In the Cloud Print dialog that appears, search for and Add cloud printers for the devices in the organizational unit you selected.
  3. Click Save.

It can take up to 24 hours for printers to be shared with every Chrome device you select. Any user on the device, including users using guest browsing or managed guest sessions, will be able to print from the cloud printers you share.

If there are printers that you don't own, which are shared with your domain, they will appear under an additional Other printers heading. If a printer is no longer working or if there's no longer an owner in your domain, you can remove it from Other printers.

Deployment notes:

  • You need to be the owner of the printer in Google Cloud Print to add it using the Admin console. If you have several printers, create a role account specifically to manage printers with Google Cloud Print. If you do, sign in with the role account to share the printers with your Chrome devices. If you don't want to create a role account with super admin access, you can give the role account permission to only Manage Device Settings using delegated admin roles. For details, see Delegate administrator roles in Chrome.
  • Depending on your environment and printers, you might be able to use native printing.

Known issues:

  • Because printer ownership is tied to each G Suite account, if your organization has multiple admins, they might each have a different set of printers available.
  • An admin can delete or remove the printer shared by another admin. For example, if the printer owned by admin2 has been deleted by admin1, then admin1, cannot re-add it.
  • Currently, there isn't a way to tell if a printer in the Other printers section is active or deleted because of these known issues we're working to fix:
    • If an an admin deletes a printer at https://www.google.com/cloudprint/#printers, even though it's no longer is available, it will appear under Other printers.
    • If the printer owner has been deleted, the printer will appear under Other printers.
Device network hostname template

Supported on Chrome version 65 and later

Allows you to specify the host name that is passed to the DHCP server with DHCP requests.

If this policy is set to a nonempty string, that string will be used as the device host name during the DHCP request.

The string can contain the ${ASSET_ID}, ${SERIAL_NUM}, and ${MAC_ADDR} variables. These variables will be replaced with values found on the device. The resulting substitution should be a valid host name per RFC 1035, section 3.1.

If this policy is not set or if the value after substitution is not a valid host name, no host name will be used in the DHCP request.

Timezone

System timezone

Specifies the time zone to set for your users' devices.

System timezone automatic detection

Choose one of the options to specify how a device detects and sets the current time zone:

  • Let users decide—Users control the time zone using the standard Chrome date and time settings.
  • Never auto-detect timezone—Users must manually pick a time zone.
  • Always use coarse timezone detection—Uses device IP address to set the time zone.
  • Always send WiFi access-points to server while resolving timezone—Uses location of the WiFi access-point that the device connects to to set the time zone (most accurate).
  • Send all location information—Uses location information, such as WiFi access-points and GPS, to set the time zone.
Mobile data roaming

Specifies whether users on the Chrome device can go online using a mobile network maintained by a different carrier (charge may apply). With this setting, users need to allow mobile data roaming on the device.

Related topic: Connect to a mobile data network

USB detachable whitelist

Allows you to specify a list of USB devices that can be accessed directly by applications, such as Citrix Receiver. You can list devices, such as keyboards, signature pads, printers and scanners, as well as other USB devices. If this policy is not configured, the list of a detachable USB devices is empty.

To add devices to the list, enter the USB vendor identifier (VID) and product identifier (PID) as a colon separated hexadecimal pair (VID:PID). Put each device on a separate line. For example, to list a mouse with a VID of 046E and a PID of D626 and a signature pad with a VID of 0404 and PID of 6002, you enter:

046E:D626
0404:6002

Bluetooth

Allows you to enable or disable Bluetooth® on a device.

  • To enable Bluetooth, select Do not disable bluetooth.
  • To disable Bluetooth, select Disable bluetooth.

If you change the policy from Disable bluetooth to Do not disable bluetooth, you must restart the device for the change to take effect.

If you change the policy from Do not disable bluetooth to Disable bluetooth, the change is immediate and you do not need to restart the device.

Throttle device bandwidth

Devices in kiosk, managed guest session, or user mode with Chrome version 56 and later

Controls device-level bandwidth consumption. All network interfaces on a device are throttled, including WiFi, Ethernet, USB Ethernet adapter, USB cellular dongle, and USB wireless card. All network traffic is throttled, including OS updates.

To enable the setting:

  1. Select Enable network throttling.
  2. Specify the download and upload speed in kbps. The minimum speed that you can specify is 513 kbps.
TPM firmware update

Installing TPM firmware updates might erase a device and reset it to factory settings and repeated failed update attempts might make a device unusable.

To let users install a Trusted Platform Module (TPM) firmware update on devices, select Allow users to perform TPM firmware updates. For information about how users can install a firmware update, see Update your Chromebook’s security.

Virtual machines

Specifies whether users can run virtual machines on their devices running Chrome OS. To let users install Linux apps and run Linux tools, editors, and integrated development environments (IDEs), select Allow usage for virtual machines needed to support Linux apps. For information about how users turn on Linux app support, see Set up Linux (Beta) on your Chromebook.

MAC address pass through

Device-specific setting  Currently available with Dell Latitude 5400 and 5300 2-in-1 Chromebook Enterprise devices

Allows you to choose the same MAC address that the docking station uses when it’s connected to the Chromebook. After you set the address, you need to restart the Chromebook for the address to take effect.

Dell SupportAssist

Device-specific setting  Currently available with Dell Latitude 5400 and 5300 2-in-1 Chromebook Enterprise devices

Allows you to turn on and configure the Dell SupportAssist program. For information on Dell Support Assist, go to Dell support.

Chrome Management—Partner Access

Chrome Management—Partner Access

Currently not available with G Suite for Education

Gives EMM partners programmatic access to manage device policies, get device information, and issue remote commands. 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 Chrome devices, which means they no longer have to manage devices by Admin console organizational-unit structure. Instead, they can use the structure configured in their EMM console. You can’t simultaneously set the same policy for the same device using partner access and the Admin console. Device-level policies configured using partner access controls take precedence over policies set in the Admin console. To enforce policies on devices at organizational-unit level, you need to uncheck the Enable Chrome Management—Partner access box.

Related topic: Manage Chrome devices with EMM console

Was this helpful?
How can we improve it?