Extension management settings
Explanation
Setting the policy controls extension management settings for Google Chrome, including any controlled by existing extension-related policies.
This policy maps an extension ID or an update URL to its specific setting only. A default configuration can be set for the special ID "*", which applies to all extensions without a custom configuration in this policy.
This policy can override per-extension config from legacy policies.
Note that any per-ID extension setting from either ExtensionInstallForcelist, ExtensionInstallAllowlist, ExtensionInstallBlocklist, or ExtensionSettings will only inherit 'installation_mode' and 'update_url' from the "*" defaults. It will not inherit any other properties. With an update URL, configuration applies to extensions with the exact update URL stated in the extension manifest ( http://support.google.com/chrome/a?p=Configure_ExtensionSettings_policy ). If the 'override_update_url' flag is set to true, the extension is installed and updated using the "update" URL specified in the ExtensionInstallForcelist policy or in 'update_url' field in this policy. The flag 'override_update_url' is ignored if the 'update_url' is a Chrome Web Store url.
As of Google Chrome version 154, applying 'runtime_blocked_hosts' to an extension with the 'debugger' permission will completely disable 'chrome.debugger.attach()' on all targets.
On Microsoft® Windows® instances, apps and extensions from outside the Chrome Web Store can only be forced installed if the instance is joined to a Microsoft® Active Directory® domain, joined to Microsoft® Azure® Active Directory® or enrolled in Chrome Enterprise Core.
On macOS instances, apps and extensions from outside the Chrome Web Store can only be force installed if the instance is managed via MDM, joined to a domain via MCX or enrolled in Chrome Enterprise Core.
Note: This policy only applies to platforms that support extensions.
See https://chromeenterprise.google/policies/?policy=ExtensionSettings for more information about schema and formatting.
Example value:
{
"*": {
"allowed_types": [
"hosted_app"
],
"blocked_install_message": "Custom error message.",
"blocked_permissions": [
"downloads",
"bookmarks"
],
"install_sources": [
"https://company-intranet/chromeapps"
],
"installation_mode": "blocked",
"runtime_allowed_hosts": [
"*://good.example.com"
],
"runtime_blocked_hosts": [
"*://*.example.com"
]
},
"abcdefghijklmnopabcdefghijklmnop": {
"blocked_permissions": [
"history"
],
"installation_mode": "allowed",
"minimum_version_required": "1.0.1",
"toolbar_pin": "force_pinned",
"file_url_navigation_allowed": true
},
"bcdefghijklmnopabcdefghijklmnopa": {
"allowed_permissions": [
"downloads"
],
"installation_mode": "force_installed",
"runtime_allowed_hosts": [
"*://good.example.com"
],
"runtime_blocked_hosts": [
"*://*.example.com"
],
"update_url": "https://example.com/update_url"
},
"cdefghijklmnopabcdefghijklmnopab": {
"blocked_install_message": "Custom error message.",
"installation_mode": "blocked"
},
"defghijklmnopabcdefghijklmnopabc,efghijklmnopabcdefghijklmnopabcd": {
"blocked_install_message": "Custom error message.",
"installation_mode": "blocked"
},
"fghijklmnopabcdefghijklmnopabcde": {
"blocked_install_message": "Custom removal message.",
"installation_mode": "removed"
},
"ghijklmnopabcdefghijklmnopabcdef": {
"installation_mode": "force_installed",
"override_update_url": true,
"update_url": "https://example.com/update_url"
},
"update_url:https://www.example.com/update.xml": {
"allowed_permissions": [
"downloads"
],
"blocked_permissions": [
"wallpaper"
],
"installation_mode": "allowed"
}
}
Use cases
Manages Chrome extensions centrally and in detail: per-extension install mode (allowed, blocked, force-installed, etc.), blocked API permissions, update URL. One entry per ID or update URL, plus a default configuration through the special ID *. This policy takes precedence over the older extension policies if they are also set, which makes it a good fit when the fleet has different rules per extension.
Google's guide details the available fields.
Microsoft sources: ExtensionSettings: Extension management settings (Chrome Enterprise) · Configure ExtensionSettings policy (Chrome Enterprise and Education Help)
Registry
HKEY_LOCAL_MACHINE\Software\Policies\Google\ChromeHKEY_CURRENT_USER\Software\Policies\Google\Chrome- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Computer (HKLM)
Enable
# Enable: chrome/ExtensionSettings
$k = 'HKLM:\Software\Policies\Google\Chrome'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Extension management settings
Set-ItemProperty -Path $k -Name 'ExtensionSettings' -Value '<value>' -Type StringDisable
# Disable: chrome/ExtensionSettings
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": chrome/ExtensionSettings
$k = 'HKLM:\Software\Policies\Google\Chrome'
Remove-ItemProperty -Path $k -Name 'ExtensionSettings' -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Extension management settingsExtensionSettings | Text boxtext | ExtensionSettings | REG_SZ | Max length: 1000000 |
Application
Google Chrome (Google) — November 2026 templates
Official templates downloaded on November 12, 2026.