Manage Chrome kiosk app settings

This article is for Chrome administrators and developers with experience developing Chrome apps.

As an administrator, you can use the Admin console to customize Chrome kiosk apps. For case, you lot might want your app to control the version of Chrome that's running on a kiosk. Or, you lot can automatically launch a kiosk app on a digital sign.

Autolaunch a kiosk app on Chrome devices

Setting a kiosk app to launch automatically turns devices running Chrome Bone into single-purpose devices. You can deploy multiple kiosk apps to devices, simply you can only configure one app to automatically launch when devices start. For example, you might automatically launch an app on devices where user interaction isn't controlled with a keyboard and mouse.

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

  3. Click Apps & extensions and then Kiosks.
  4. To utilise the setting to everyone, exit the top organizational unit of measurement selected. Otherwise, select a child organizational unit.
  5. Next toMotorcar-launch app, choose the app that yous desire to automatically launch on Chrome devices.
  6. Click Save.

Allow a kiosk app control the Chrome version

Supported on Chrome 52 and afterward.

You tin let a kiosk app control the Chrome version on a device running Chrome OS to improve device stability if the app, or sure app features, aren't compatible with the latest Chrome release.

We recommend that you only allow a kiosk app control the Chrome version if:

  • Your testing procedure doesn't align with the standard vi-calendar week cycle for Chrome OS updates.
  • In that location is significant risk associated with whatever potential stability issues.

Step 1: Set the OS version in the kiosk app'south manifest file

  1. Identify the Chrome Bone version that you want to specify.
    1. Go to CrOS-OmahaProxy CSV Viewer.
    2. For the most common device in your arrangement, take note of the chrome_version value.
  2. In the app's manifest.json file, gear up required_platform_version to the value you noted.
    For example: "required_platform_version": "8350".
  3. To automatically update the app to the latest version, even if the Chrome Os version isn't compliant, set always_update to truthful.

This sample configuration sets the required_platform_version to8350 and ever lets the app update automatically.

Pace 2: Allow the kiosk app command the Chrome version

Step iii : Verify policies are applied

After y'all employ whatever Chrome policies, users need to restart Chrome devices for the settings to take outcome. You tin check the devices to make certain the policy was practical correctly.

  1. On a managed Chrome device, scan to chrome://policy.
  2. Click Reload policies.
  3. For an autolaunched kiosk app:
    • For AllowKioskAppControlChromeVersion, make sure that Status is gear up to OK and Policy value is true.
    • For DeviceAutoUpdateDisable, make sure that Condition is OK and Policy value is true.
  4. For specified kiosk apps:
    • For DeviceTargetVersionPrefix, make sure that Condition is set to OK.
    • For DeviceTargetVersionPrefix, brand sure that Policy value is the same as the value set for required_platform_version in the app's manifest file.

Common scenarios

This table describes different scenarios where kiosk apps are configured to control the Chrome version on a device.

Scenario Outcome

The app's manifest file does not take the required_platform_version manifest central.

Devices autoupdate to the latest Chrome Os version when information technology becomes available.

The app'due south manifest file has an invalid required_platform_version setting.

The app developer sees an error bulletin in chrome://extensions when they try to load the app. The required_platform_version must be valid for the app to get installed or updated from the Chrome Spider web Shop.

The required_platform_version value is lower than the device'southward current platform version.

The app is installed merely the device'southward Bone will not get updated unless the required_platform_version value is updated to a version higher than the current device OS version.

Notation: The first time an app is installed from the Chrome Web Store, the required_platform_version value is verified, but not compared to the device's electric current platform version.

The required_platform_version is updated to a lower value than the device's current platform version.

The app is not installed and the client device continues to run the older version of the app.

Specify URLs kiosk apps tin can access

You tin block and allow upwards to 1,000 URLs so that kiosk apps tin can only access sure websites.

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

  3. Click Settings and then Device.
  4. To apply the setting to everyone, leave the top organizational unit of measurement selected. Otherwise, select a child organizational unit.
  5. Under Kiosk settings, curlicue to URL Blocking and enter URLs as needed:
    • Blocked URLs—URLs that you want to prevent kiosk apps from accessing.
      For syntax and examples, run into Devices > Blocked URLs.
    • Blocked URLs exceptions—URLs that you want to allow kiosk apps to access (URLAllowlist). Access is immune even if the URLs are also defined in Blocked URLs.
      For syntax and examples, see Devices > Blocked URLs exceptions.
  6. Click Relieve.

Related topics

  • Create and deploy Chrome kiosk apps
  • Kiosk apps
  • Kiosk settings

Was this helpful?

How can nosotros improve it?