en-US chrome computer user

Default sensors setting

Verified with Google Chrome — updated on September 2, 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/DefaultSensorsSetting

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

macOS / Linux preference DefaultSensorsSetting
Android restriction DefaultSensorsSetting
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

Default sensors setting
DefaultSensorsSetting enum
  • 1 Allow sites to access sensors
  • 2 Do not allow any site to access sensors
  • 3 Ask whenever a site wants to access sensors

Description

Setting the policy to 1 lets websites access and use sensors such as motion and light. Setting the policy to 2 denies access to sensors. When the policy is set to 3 it will ask the user when a site requests access to sensors if the tri-state feature flag is enabled, otherwise it will default to allowing access to sensors. Leaving it unset means AllowSensors applies, but users can change this setting.

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: Default sensors setting
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
"DefaultSensorsSetting"=dword:00000001
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Default sensors setting
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'DefaultSensorsSetting' -Value 1 -Type DWord

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