Brave Browser: 1.95.104 to 1.97.59

This policy can be used to allow Chrome DevTools on specific URLs. [added: Chrome DevTools availability is evaluated at the target level. ]URL patterns are matched against the URL of [removed: every][added: each target being inspected (such as the main] frame [removed: on the page being inspected.][added: of a page, an embedded subframe, an extension, or a web application).] The resulting behavior depends on whether the DeveloperToolsAvailabilityBlocklist policy is also set. If this policy is set and DeveloperToolsAvailabilityBlocklist is not, [removed: every frame's][added: a target's] URL must match a pattern on this allowlist for Chrome DevTools to be [removed: allowed.][added: allowed for that target.] If [removed: any frame's][added: a target's] URL does not [removed: match,][added: match this allowlist, Chrome] DevTools will be blocked for [added: that target (for example, a subframe whose URL is not on ]the [removed: entire page.][added: allowlist cannot be inspected, but the main page remains inspectable if its URL is allowlisted).] For information on the URL format, see https://support.google.com/chrome/a?p=url_blocklist_filter_format. If both this and the DeveloperToolsAvailabilityBlocklist policies are set, this allowlist takes precedence. If a [removed: frame's][added: target's] URL matches a pattern on this allowlist, it will be allowed, even if it also matches a pattern in the blocklist. If a [added: target's ]URL matches a pattern on [removed: the][added: this] blocklist (but not the allowlist), it will be blocked. If a [added: target's ]URL matches neither, the DeveloperToolsAvailability policy will be used as a fallback. If this policy is not set, the availability of Chrome DevTools is determined by the DeveloperToolsAvailabilityBlocklist and DeveloperToolsAvailability policies. [added: Blanket host wildcards (i.e., "*" or "[*]") are not allowed; use the DeveloperToolsAvailability policy to enable the feature globally. ]This policy [removed: also applies to][added: affects Chrome DevTools, direct] Chrome DevTools [removed: opened for extensions][added: Protocol (CDP) access (for instance, when launched with --remote-debugging-port or --remote-debugging-pipe),] and [removed: web applications. Blanket host wildcards (i.e., "*" or "[*]") are not allowed; use][added: Chrome DevTools Protocol (CDP) access via chrome.debugger APIs. Both this policy and] the [removed: DeveloperToolsAvailability][added: RemoteDebuggingAllowed policy apply: RemoteDebuggingAllowed controls whether remote debugging can start, while this] policy [removed: to enable the feature globally.][added: restricts whether individual targets can be inspected even when remote debugging is running.] This policy is limited to 1,000 entries. Example value: example.com https://ssl.server.com hosting.com/bad_path https://server:8080/path .exact.hostname.com file://*

This policy can be used to block Chrome DevTools on specific URLs. For information on the URL format, see https://support.google.com/chrome/a?p=url_blocklist_filter_format. [added: Chrome DevTools availability is evaluated at the target level. ]URL patterns are matched against the URL of [removed: every][added: each target being inspected (such as the main] frame [removed: on the page being inspected.][added: of a page, an embedded subframe, an extension, or a web application).] The resulting behavior depends on whether the DeveloperToolsAvailabilityAllowlist policy is also set. If this policy is set and DeveloperToolsAvailabilityAllowlist is not, [removed: any frame's][added: a target's] URL matching a pattern on this blocklist will block Chrome DevTools for [added: that target (for example, a subframe whose URL matches this blocklist cannot be inspected, but ]the [removed: entire page.][added: main page remains inspectable if its URL is not blocklisted).] If a [removed: frame's][added: target's] URL does[removed: n'][added: no]t match any pattern, the availability is determined by the DeveloperToolsAvailability policy. If both this and the DeveloperToolsAvailabilityAllowlist policies are set, the allowlist takes precedence. If a [removed: frame's][added: target's] URL matches a pattern on the allowlist, it will be allowed, even if it also matches a pattern in this blocklist. If a [added: target's ]URL matches a pattern on this blocklist (but not the allowlist), it will be blocked. If a [added: target's ]URL matches neither, the DeveloperToolsAvailability policy will be used as a fallback. If this policy is not set, the availability of Chrome DevTools is determined by the DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailability policies.[added: This policy affects Chrome DevTools, direct Chrome DevTools Protocol (CDP) access (for instance, when launched with --remote-debugging-port or --remote-debugging-pipe), and Chrome DevTools Protocol (CDP) access via chrome.debugger APIs. Both this policy and the RemoteDebuggingAllowed policy apply: RemoteDebuggingAllowed controls whether remote debugging can start, while this policy restricts whether individual targets can be inspected even when remote debugging is running.] This policy is limited to 1,000 entries. Example value: https://example.com example.com https://ssl.server.com hosting.com/bad_path https://server:8080/path .exact.hostname.com * file://*

Setting the policy to Enabled disallows screenshots taken with keyboard shortcuts or extension APIs. Setting the policy to Disabled or not set allows screenshots. [added: As of Brave version 154, enabling this policy also prevents extensions from attaching the debugger via 'chrome.debugger.attach()'. ]Note that on Microsoft® Windows®, macOS and Linux, this does not prevent screenshots that are taken with operating system or third party applications.

When this policy is set to Enabled, Local Network Access requests will only display warnings in Chrome DevTools due to Local Network Access checks failing. When this policy is set to Disabled or unset, Local Network Access requests will use the default handling of these requests. See https://wicg.github.io/local-network-access/ for Local Network Access restrictions. This enterprise policy is temporary, and will be removed after M1[removed: 56][added: 63]. Long term, the policy LocalNetworkAccessAllowedForUrls can be used to allowlist URL patterns that should be automatically granted the Local Network Access permission.

Setting the policy controls extension management settings for Brave, 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. [added: As of Brave 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" } }

Controls whether users may use remote debugging. If this policy is set to Enabled or not set, users may use remote debugging by specifying --remote-debugging-port and --remote-debugging-pipe command line [removed: switches.][added: switches on desktop platforms, or by enabling the USB debugging system setting on Android.] If this policy is set to Disabled, users are not allowed to use remote debugging.