Brave Browser: 1.92.144 to 1.94.117

Controls if the Gemini Spark agent is allowed to connect to Brave and use auto browse. 0 = Gemini Spark is allowed to connect to and use Brave auto browse 1 = Gemini Spark is not allowed to connect to or use Brave auto browse Warning: Enabling Gemini Spark to connect to Brave and use auto browse permits the Gemini Spark agent to perform autonomous, multi-step actions on Brave clients using the active browser session. This entails significant security risks, including credential risks, Local Network Ingress and loss of context aware signals. Existing management and security controls might not be respected. Administrators are advised to carefully evaluate their organization's network threat model, compliance and privacy guidelines before enabling this feature. This policy has no effect when the Google Gemini app or Brave auto browse policies are disabled. For example, the Google Gemini app can be disabled by GeminiSettings policy. For more information on Google Gemini in Brave, please see https://support.google.com/chrome/a?p=gemini_in_chrome. Brave auto browse and Gemini Spark are not available in all countries or all languages. Setting this policy to 0 - Enabled does not guarantee the feature will be enabled; it remains subject to availability. For more info on the roll-out, check the Enterprise Release Notes: [removed: https://chromeenterprise.google/resources/release-notes/ If the policy is unset, its behavior is determined by the GenAiDefaultSettings policy.][added: https://chromeenterprise.google/resources/release-notes/.]

This policy can be used to allow Chrome DevTools on specific URLs. URL patterns are matched against the URL of every frame on the page being inspected. The resulting behavior depends on whether the DeveloperToolsAvailabilityBlocklist policy is also set. If this policy is set and DeveloperToolsAvailabilityBlocklist is not, every frame's URL must match a pattern on this allowlist for Chrome DevTools to be allowed. If any frame's URL does not match, DevTools will be blocked for the entire page. 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 frame's URL matches a pattern on this allowlist, it will be allowed, even if it also matches a pattern in the blocklist. If a URL matches a pattern on the blocklist (but not the allowlist), it will be blocked. If a 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. This policy also applies to Chrome DevTools opened for extensions and web applications. [added: Blanket host wildcards (i.e., "*" or "[*]") are not allowed; use the DeveloperToolsAvailability policy to enable the feature globally. ]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://*

[removed: Setting the][added: Specify a list of origins that run in a dedicated process. On Android, this] policy [removed: means each of the named origins in a comma-separated list runs in a dedicated process. ][added: only works on devices with sufficient memory (strictly more than 3.2GB RAM), as isolating too many sites on resource-constrained devices may cause performance problems. For resource-constrained Android devices, please use IsolateOriginsShortlist instead. Devices with less than 1GB memory are not recommended to configure any process isolation specifically. ]Each named origin's process will only be allowed to contain documents from that origin and its subdomains. For example, specifying https://a1.example.com/ allows https://a2.a1.example.com/ in the same process, but not https://example.com or https://b.example.com. Since Brave 77, you can also specify a range of origins to isolate using a wildcard. For example, specifying https://[*.]corp.example.com will give every origin underneath https://corp.example.com its own dedicated process, including https://corp.example.com itself, https://a1.corp.example.com, and https://a2.a1.corp.example.com. Note that all sites (i.e., scheme plus eTLD+1, such as https://example.com) are already isolated by default on Desktop platforms, as noted in the SitePerProcess policy. This IsolateOrigins policy is useful to isolate specific origins at a finer granularity (e.g., https://a.example.com). [added: Note that Android isolates certain sensitive sites by default starting in Brave version 77, and this policy extends that mode to isolate specific additional origins. ]Also note that origins isolated by this policy will be unable to script other origins in the same site, which is otherwise possible if two same-site documents modify their document.domain values to match. Administrators should confirm this uncommon behavior is not used on an origin before isolating it. Setting the policy to [removed: off][added: an empty string] or leaving it unset [removed: lets users change this setting. Note: For Android, use][added: means site isolation won't be required for any specific origins. Users can still turn on process isolation manually, through] the [removed: IsolateOriginsAndroid policy instead.][added: command line flag.] Example value: https://a.example.com/,https://othersite.org/,https://[*.]corp.example.com

When this policy is Enabled, anonymous reporting of usage and crash-related data about Brave to Google is recommended to be enabled by default. Users will still be able to change this setting. When this policy is Disabled, anonymous reporting is disabled and no usage or crash data is sent to Google. Users won't be able to change this setting. When this policy is not set, users can choose the anonymous reporting behavior at installation or first run, and can change this setting later. (For Google Chrome OS, see DeviceMetricsReportingEnabled.)[removed: If the RestructureMetricsConsentSettings experiment is active on the device and both this policy and the MetricsReportingLevel policy are set, the MetricsReportingLevel policy takes precedence.]

Setting the policy provides access to the listed URLs in Incognito mode. Use it to open exceptions to certain URL patterns defined in IncognitoModeUrlBlocklist, using the format specified at ( https://support.google.com/chrome/a?p=url_blocklist_filter_format ). If both this policy and IncognitoModeUrlBlocklist are set, the allowlist takes precedence. If a URL matches a pattern on the allowlist, it will be allowed. If it matches a pattern on the blocklist (but not the allowlist), it will be blocked. If a URL matches neither, the general URLBlocklist/URLAllowlist policies will be used as a fallback. If this policy is set and IncognitoModeUrlBlocklist is not, any URL not on the allowlist will be blocked in Incognito mode. If IncognitoModeAvailability is set to disallow (value 1), but this policy is configured, Incognito mode will be available only for the URLs matching the allowlist. Leaving the policy unset allows no exceptions to IncognitoModeUrlBlocklist and IncognitoModeAvailability. This policy only affects Incognito mode. To allow URLs for all user profiles, please use the URLAllowlist policy. [added: Blanket host wildcards (i.e., "*" or "[*]") are not allowed; use the IncognitoModeAvailability policy to enable the feature globally. ]This policy is limited to 1000 entries. Example value: example.com https://ssl.server.com hosting.com/bad_path https://server:8080/path .exact.hostname.com file://* custom_scheme:* *

When this policy is Enabled, anonymous reporting of usage and crash-related data about Brave to Google is recommended to be enabled by default. Users will still be able to change this setting. When this policy is Disabled, anonymous reporting is disabled and no usage or crash data is sent to Google. Users won't be able to change this setting. When this policy is not set, users can choose the anonymous reporting behavior at installation or first run, and can change this setting later. (For Google Chrome OS, see DeviceMetricsReportingEnabled.)[removed: If the RestructureMetricsConsentSettings experiment is active on the device and both this policy and the MetricsReportingLevel policy are set, the MetricsReportingLevel policy takes precedence.]

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 M15[removed: 2][added: 6]. Long term, the policy LocalNetworkAccessAllowedForUrls can be used to allowlist URL patterns that should be automatically granted the Local Network Access permission.