en-US chrome computer user

Allow access to sensors on these sites

Verified with Google Chrome — updated on July 10, 2026 Supported on: Microsoft Windows 7 or later

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome\Content settings

Registry

HKLM Software\Policies\Google\Chrome
HKCU Software\Policies\Google\Chrome

Other deployment channels

Intune (ADMX ingestion)
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~ContentSettings/SensorsAllowedForUrls

OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.

macOS / Linux preference SensorsAllowedForUrls
Android restriction SensorsAllowedForUrls
Supported platforms
  • Google Chrome (Linux) — since version 88
  • Google Chrome (Mac) — since version 88
  • Google Chrome (Windows) — since version 88
  • Google ChromeOS (Google ChromeOS) — since version 88
  • Google Chrome (Android) — since version 88

Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page

Options

Allow access to sensors on these sites
List (registry values) list list under Software\Policies\Google\Chrome\SensorsAllowedForUrls

Description

Setting the policy lets you set a list of URL patterns that specify the sites that can access sensors like motion and light sensors. Leaving the policy unset means DefaultSensorsSetting applies for all sites, if it's set. If not, the user's personal setting applies. If the same URL pattern exists in both this policy and the SensorsBlockedForUrls policy, the latter is prioritized and access to motion or light sensors will be blocked. For detailed information on valid url patterns, please see https://chromeenterprise.google/policies/url-patterns. Wildcards, *, are allowed. Example value: https://www.example.com [*.]example.edu

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO. ⓘ

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Allow access to sensors on these sites
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\SensorsAllowedForUrls]
; List values: enter one value per line in the builder UI.
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Allow access to sensors on these sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome\SensorsAllowedForUrls'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI.

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview