Brave Browser: 1.94.121 to 1.97.56

Specifies whether users can let Brave use Generative AI to better understand forms and help them fill more fields. 0 = [removed: Allow][added: Has] the [removed: feature to be used, while allowing][added: same effect as 1. Before M153, the setting allowed] Google to use relevant data to improve its AI models. Relevant data may include prompts, inputs, outputs, source materials, and written feedback, depending on the feature. 0 is the default value, except when noted below. 1 = Allow the feature to be used, but does not allow Google to improve models using [removed: users' content][added: relevant data] (including prompts, inputs, outputs, source materials, and written feedback). 1 is the default value for Enterprise users managed by Google Admin console and for Education accounts managed by Google Workspace. 2 = Do not allow the feature. If the policy is unset, its behavior is determined by the GenAiDefaultSettings policy. For more information on data handling for generative AI features, please see https://support.google.com/chrome/a?p=generative_ai_settings.

[removed: Voice Typing][added: Talk to type] is an AI-based feature that allows users to input and edit text using their voice, powered by generative AI models to provide high-quality transcription and formatting. 0 = Allow the feature to be used, while allowing Google to use relevant data to improve its AI models. Relevant data may include prompts, inputs, outputs, source materials, and written feedback, depending on the feature. It may also be reviewed by humans to improve AI models. 0 is the default value, except when noted below. 1 = Allow the feature to be used, but does not allow Google to improve models using users' content (including prompts, inputs, outputs, source materials, and written feedback). 1 is the default value for Enterprise users managed by Google Admin console and for Education accounts managed by Google Workspace. 2 = Do not allow the feature. If the policy is unset, its behavior is determined by the GenAiDefaultSettings policy. For more information on data handling for generative AI features, please see https://support.google.com/chrome/a?p=generative_ai_settings.

Setting the policy to 0 (the default) means you can access [removed: the developer tools ][added: Chrome DevTools ]and the JavaScript console, but not in the context of extensions installed by enterprise policy or, since version 114 and if this is a managed user, extensions built into the browser. Setting the policy to 1 means you can access [removed: the developer tools ][added: Chrome DevTools ]and the JavaScript console in all contexts, including that of extensions installed by enterprise policy. Setting the policy to 2 means you can't access [removed: developer tools,][added: Chrome DevTools,] and you can't inspect website elements. This setting also turns off keyboard shortcuts and menu or context menu entries to open [removed: developer tools][added: Chrome DevTools] or the JavaScript console. As of Brave version 99, this setting also controls entry points for the 'View page source' feature. If you set this policy to 'DeveloperToolsDisallowed' (value 2), users cannot access source viewing via keyboard shortcut or the context menu. To fully block source viewing, you must also add 'view-source:*' to the URLBlocklist policy. As of Brave version 119, this setting also controls whether developer mode for Isolated Web Apps can be activated and used. As of Brave version 128, this setting will not control developer mode on extensions page if ExtensionDeveloperModeSettings policy is set. [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. ]The [added: DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailabilityBlocklist policies take precedence over this policy. The ]availability of [removed: Developer Tools][added: Chrome DevTools] is determined in the following order of precedence:[removed: ][added: ]1. If a URL matches a pattern in the DeveloperToolsAvailabilityAllowlist policy, [removed: Developer Tools][added: Chrome DevTools] are allowed. 2. If the DeveloperToolsAvailabilityAllowlist is set and the DeveloperToolsAvailabilityBlocklist is not, any URL not on the allowlist is blocked. 3. If a URL matches a pattern in the DeveloperToolsAvailabilityBlocklist policy, [removed: Developer Tools][added: Chrome DevTools] are blocked. 4. If [removed: a URL][added: neither policy] is [removed: not covered by the allowlist or blocklist,][added: set, or if a URL matches neither list,] this policy (DeveloperToolsAvailability) is [added: used as ]the [removed: fallback.][added: fallback mechanism.]

This policy is [removed: deprecated. Its usage is discouraged.][added: removed. It is not compatible with this version of Brave.] Read more at https://support.google.com/chrome/a/answer/7643500

Controls if the Gemini Spark agent is allowed to connect to Brave and use auto browse.[added: Gemini Spark might not be available to your organization.] 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: https://chromeenterprise.google/resources/release-notes/.

This policy is [removed: deprecated. Its usage is discouraged.][added: removed. It is not compatible with this version of Brave.] Read more at https://support.google.com/chrome/a/answer/7643500 See https://chromeenterprise.google/policies/?policy=FirstPartySetsOverrides for more information about schema and formatting.[removed: Example value: { "additions": [ { "associatedSites": [ "https://associate2.test" ], "ccTLDs": { "https://associate2.test": [ "https://associate2.com" ] }, "primary": "https://primary2.test", "serviceSites": [ "https://associate2-content.test" ] } ], "replacements": [ { "associatedSites": [ "https://associate1.test" ], "ccTLDs": { "https://associate1.test": [ "https://associate1.co.uk" ] }, "primary": "https://primary1.test", "serviceSites": [ "https://associate1-content.test" ] } ] }][added: ]

This policy [removed: controls the visibility of the middle slot announcement on the New Tab Page. If the policy ]is [removed: set to Enabled, the New Tab Page will show the middle slot announcement if it ][added: removed. It ]is [removed: available. If the policy is set to Disabled, the New Tab Page will ]not [removed: show the middle slot announcement even if it is available. ][added: compatible with this version of Brave. Read more at https://support.google.com/chrome/a/answer/7643500]

This policy is [removed: deprecated. Its usage is discouraged.][added: removed. It is not compatible with this version of Brave.] Read more at https://support.google.com/chrome/a/answer/7643500

This policy is [removed: deprecated. Its usage is discouraged.][added: removed. It is not compatible with this version of Brave.] Read more at https://support.google.com/chrome/a/answer/7643500 See https://chromeenterprise.google/policies/?policy=RelatedWebsiteSetsOverrides for more information about schema and formatting.[removed: Example value: { "additions": [ { "associatedSites": [ "https://associate2.test" ], "ccTLDs": { "https://associate2.test": [ "https://associate2.com" ] }, "primary": "https://primary2.test", "serviceSites": [ "https://associate2-content.test" ] } ], "replacements": [ { "associatedSites": [ "https://associate1.test" ], "ccTLDs": { "https://associate1.test": [ "https://associate1.co.uk" ] }, "primary": "https://primary1.test", "serviceSites": [ "https://associate1-content.test" ] } ] }][added: ]

[removed: Enable the Shared Clipboard feature which allows users to send text between Chrome Desktops and an Android device when Sync is enabled and the user is Signed-in. If this ][added: This ]policy is [removed: set to true, the capability of sending text, cross device, for chrome user is enabled. If this policy is set to false, the capability of sending text, cross device, for chrome user is disabled. If you set this policy, users cannot change or override it. If this policy is left unset, the shared clipboard feature is enabled by default. ][added: removed. ]It is [removed: up to the admins to set policies in all platforms they care about. It's recommended to set ][added: not compatible with ]this [removed: policy to one value in all platforms.][added: version of Brave. Read more at https://support.google.com/chrome/a/answer/7643500]