Setup through device management
Install the Browser Guard for Chrome and Edge through your device management and set it up with an enrolment code. Six settings, with examples for Windows, Intune and macOS.
With your device management you install the Browser Guard on many devices at once and give it an enrolment code, and for your own gateway also its address. Each device then enrols on its own; nobody has to enter anything. The Browser Guard does not use a project API key (since version 1.6.0).
The force installation below needs the entry of the Browser Guard in the Chrome Web Store or in Edge Add-ons. These entries follow after approval; there is no date yet. Until then, load the package Palveron gives you as described in Installation for one person. The settings of the Browser Guard on this page are what it reads from device management.
Download from the console (recommended)
Under Settings → Security → Browser Guard → Policy from the console, an admin downloads a ready-to-use policy for their device management. Choose how long the code is valid and the device limit, then download the file for your platform — Windows (PowerShell or registry), macOS, Google Admin or Firefox. Each download mints its own enrolment code for this project and writes it into the file; the code is shown once afterwards and then appears under Enrolment codes, where you can revoke it.
The file contains an enrolment code — treat it like a password. Anyone with the file can enrol a device into this project until the code expires or you revoke it. Store it where your device management keeps secrets, and revoke the code under Enrolment codes when the rollout is complete; devices that already enrolled keep working.
The files are for Palveron Cloud: they force-install the extension and set only the enrolment code (enrollment_code); the extension uses the built-in Cloud address, so no gateway_url is set. The other settings below (behavior during an outage, the question before an upload, the maximum age of the rules) stay the project's own settings in the console and are not written into the file. For your own gateway, or to set those keys per device, use the manual templates further down.
A platform is offered only once the Browser Guard has a store entry for that browser. Until then its download is locked and shows the reason; no code is minted.
Google Admin
The console produces the managed configuration as JSON. In the Google Admin console, open Devices → Chrome → Apps & Extensions, add the Browser Guard by its Chrome Web Store ID, set the installation policy to Force install, and paste this JSON into the extension's Policy for extensions field (example; the console fills your real code):
{
"enrollment_code": "code-from-your-download"
}Firefox
Firefox reads the setting through policies.json: the 3rdparty → Extensions policy is delivered to the extension through managed storage. The downloaded file sets only the Browser Guard's own enrolment — it does not change your other extensions or policies. Merge its keys into your existing policies.json in the Firefox distribution folder instead of replacing the file (example; the console fills your real code and the add-on id once Firefox has a store entry):
{
"policies": {
"3rdparty": {
"Extensions": {
"<FIREFOX_EXTENSION_ID>": {
"enrollment_code": "code-from-your-download"
}
}
}
}
}To force-install the add-on, add an ExtensionSettings entry for it to the same policies.json — again, merge it with any entries you already have, do not replace them:
{
"policies": {
"ExtensionSettings": {
"<FIREFOX_EXTENSION_ID>": {
"installation_mode": "force_installed",
"install_url": "https://addons.mozilla.org/firefox/downloads/latest/<FIREFOX_EXTENSION_ID>/latest.xpi"
}
}
}
}The console also produces a PowerShell script and a .reg file for Windows and a .mobileconfig for macOS. These set only the Browser Guard's own settings and do not change your other extensions or policies: the PowerShell script adds the force installation to any existing ExtensionSettings and leaves other entries in place; the .reg file carries only the Browser Guard's 3rdparty enrolment; and the macOS profile sets only the extension's own preference domain (com.google.Chrome.extensions.<CHROME_EXTENSION_ID> or the Edge counterpart), never ExtensionSettings. Set up the force installation separately: on Windows with the PowerShell script or your own extension-management policy, and on macOS by adding the ExtensionSettings payload to your existing configuration profile, as shown in the section macOS: configuration profiles below. Their structure matches the manual templates below, set to Palveron Cloud with the enrolment code filled in.
Set up by hand
The steps below set the Browser Guard up by hand — use them for your own gateway, or to set more than the enrolment code.
Overview
- Issue an enrolment code for the rollout (admin).
- Look up the extension ID in the store entry.
- Force-install the extension with the browser policy
ExtensionSettings. - Set the settings of the Browser Guard for the extension.
- Check the devices under Settings → Security → Devices.
Issue an enrolment code
Under Settings → Security → Browser Guard → Enrolment codes, an admin issues a code for the rollout (see Installation for one person):
- Valid for (days): long enough for the rollout, 1 to 365 days, default 30.
- Device limit: at least the number of devices you roll out to, 1 to 10000, default 500.
The code is shown only once. Store it where your device management keeps secrets.
Look up the extension ID
Chrome Web Store and Edge Add-ons each assign their own extension ID. You find it in the store entry of the Browser Guard, as the last part of its address. In the examples below, replace the marked placeholders:
| Placeholder | Replace with |
|---|---|
<CHROME_EXTENSION_ID> | ID from the Chrome Web Store entry |
<EDGE_EXTENSION_ID> | ID from the Edge Add-ons entry |
<ENROLLMENT_CODE> | The enrolment code from step 1 |
<GATEWAY_URL> | Only for your own gateway: its address. For Palveron Cloud, leave out gateway_url. |
Settings of the Browser Guard
The Browser Guard reads these six settings from device management:
| Key | Type | Required | Meaning |
|---|---|---|---|
gateway_url | string | no | Address of your own Palveron gateway. Without this value, the Browser Guard connects to Palveron Cloud (https://gateway.palveron.com). A value set here always takes precedence |
enrollment_code | string | yes | Enrolment code. A different code than the one a device enrolled with switches the device to the project of the new code. |
enabled | boolean | no | Switches the Browser Guard on or off. Default: on |
policy_max_age_minutes | integer | no | How long the rules loaded last stay valid, 15 to 1440 minutes. Default: 240 |
browser_outage_mode | string | no | pass or block: behavior when the gateway cannot check. Takes precedence over the project setting Behavior during an outage |
browser_attachment_mode | string | no | off, confirm, justify or block: the question before a file is uploaded to an AI service. Takes precedence over the project setting Question before uploading a file to an AI service. Another value counts as confirm |
For Palveron Cloud, enrollment_code is enough; then leave out gateway_url in the examples below.
As soon as gateway_url or enrollment_code is set in device management, these values apply, and the setup in the Browser Guard window is locked. If neither is set, the setup in the Browser Guard window applies, as for a single installation.
browser_outage_mode is the only way to set the outage behavior per device. Without it, the project setting under Settings → Security → Browser Guard → Behavior during an outage applies (Let through or Block).
browser_attachment_mode sets the question before an upload per device. Without it, the project setting under Settings → Security → Browser Guard → Question before uploading a file to an AI service applies, otherwise the default confirm. What the person sees with each setting is described in Question before an upload.
Windows: registry values
Chrome and Edge read both the force installation and the settings of an extension from the registry. You can distribute the values with Group Policy, Intune (next section) or your software distribution.
Force installation (ExtensionSettings)
The policy ExtensionSettings is a string value with JSON content.
Chrome, value ExtensionSettings under HKLM\SOFTWARE\Policies\Google\Chrome:
{
"<CHROME_EXTENSION_ID>": {
"installation_mode": "force_installed",
"update_url": "https://clients2.google.com/service/update2/crx"
}
}Edge, value ExtensionSettings under HKLM\SOFTWARE\Policies\Microsoft\Edge:
{
"<EDGE_EXTENSION_ID>": {
"installation_mode": "force_installed",
"update_url": "https://edge.microsoft.com/extensionwebstorebase/v1/crx"
}
}If you already manage other extensions with ExtensionSettings, add the entry to your existing JSON instead of replacing it.
Settings of the Browser Guard (3rdparty)
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\<CHROME_EXTENSION_ID>\policy]
"gateway_url"="<GATEWAY_URL>"
"enrollment_code"="<ENROLLMENT_CODE>"
"enabled"=dword:00000001
"policy_max_age_minutes"=dword:000000f0
"browser_outage_mode"="pass"
"browser_attachment_mode"="confirm"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\<EDGE_EXTENSION_ID>\policy]
"gateway_url"="<GATEWAY_URL>"
"enrollment_code"="<ENROLLMENT_CODE>"
"enabled"=dword:00000001
"policy_max_age_minutes"=dword:000000f0
"browser_outage_mode"="pass"
"browser_attachment_mode"="confirm"dword:000000f0 is 240 minutes. Strings are REG_SZ, enabled and policy_max_age_minutes are REG_DWORD. Leave out the optional values you do not want to set.
Microsoft Intune (Windows)
Deploy the following PowerShell script as a platform script for Windows devices. Set Run this script using the logged on credentials to No and Run script in 64 bit PowerShell Host to Yes, so that it writes to HKLM.
# Palveron AI Browser Guard: force installation and settings for Chrome and Edge.
# Replace the placeholders before uploading.
$ErrorActionPreference = "Stop"
$GatewayUrl = "" # Palveron Cloud: leave empty. Your own gateway: its address.
$EnrollmentCode = "<ENROLLMENT_CODE>"
$Browsers = @(
@{ Root = "HKLM:\SOFTWARE\Policies\Google\Chrome"; Id = "<CHROME_EXTENSION_ID>";
UpdateUrl = "https://clients2.google.com/service/update2/crx" },
@{ Root = "HKLM:\SOFTWARE\Policies\Microsoft\Edge"; Id = "<EDGE_EXTENSION_ID>";
UpdateUrl = "https://edge.microsoft.com/extensionwebstorebase/v1/crx" }
)
foreach ($b in $Browsers) {
# Create the key only if it is missing: New-Item -Force on an existing key
# replaces it with an empty key and deletes the browser's other policies.
if (-not (Test-Path $b.Root)) { New-Item -Path $b.Root -Force | Out-Null }
# Force installation. Adds this entry to an existing ExtensionSettings value
# and keeps the entries of other extensions. Invalid JSON stops the script.
$current = (Get-ItemProperty -Path $b.Root -Name "ExtensionSettings" `
-ErrorAction SilentlyContinue).ExtensionSettings
if ([string]::IsNullOrWhiteSpace($current)) { $settings = [pscustomobject]@{} }
else { $settings = $current | ConvertFrom-Json }
$settings | Add-Member -NotePropertyName $b.Id -Force -NotePropertyValue (
[pscustomobject]@{ installation_mode = "force_installed"; update_url = $b.UpdateUrl })
Set-ItemProperty -Path $b.Root -Name "ExtensionSettings" -Type String `
-Value ($settings | ConvertTo-Json -Compress -Depth 10)
# Settings of the Browser Guard.
$policy = "$($b.Root)\3rdparty\extensions\$($b.Id)\policy"
if (-not (Test-Path $policy)) { New-Item -Path $policy -Force | Out-Null }
if ($GatewayUrl) {
Set-ItemProperty -Path $policy -Name "gateway_url" -Type String -Value $GatewayUrl
} else {
Remove-ItemProperty -Path $policy -Name "gateway_url" -ErrorAction SilentlyContinue
}
Set-ItemProperty -Path $policy -Name "enrollment_code" -Type String -Value $EnrollmentCode
Set-ItemProperty -Path $policy -Name "enabled" -Type DWord -Value 1
Set-ItemProperty -Path $policy -Name "policy_max_age_minutes" -Type DWord -Value 240
Set-ItemProperty -Path $policy -Name "browser_outage_mode" -Type String -Value "pass"
Set-ItemProperty -Path $policy -Name "browser_attachment_mode" -Type String -Value "confirm"
}The script contains the enrolment code. Limit access to it in Intune like any other secret, and revoke the code under Enrolment codes when the rollout is complete; devices that already enrolled with it keep working.
The script keeps existing Chrome and Edge policies: it adds the entry of the Browser Guard to an existing ExtensionSettings value and leaves the entries of other extensions unchanged. If the existing value is not valid JSON, the script stops without changing it.
You can also set the force installation alone through the Intune settings catalog with the Chrome or Edge policy ExtensionSettings; the settings of the Browser Guard then still come from the 3rdparty values above. Set ExtensionSettings on a device in one way only: if you use the settings catalog, remove the force installation section from the script.
macOS: configuration profiles
Chrome
Deliver two payloads with your MDM, for example as custom settings:
Force installation, preference domain com.google.Chrome, key ExtensionSettings:
<key>ExtensionSettings</key>
<dict>
<key><CHROME_EXTENSION_ID></key>
<dict>
<key>installation_mode</key>
<string>force_installed</string>
<key>update_url</key>
<string>https://clients2.google.com/service/update2/crx</string>
</dict>
</dict>Settings of the Browser Guard, preference domain com.google.Chrome.extensions.<CHROME_EXTENSION_ID>:
<key>gateway_url</key>
<string><GATEWAY_URL></string>
<key>enrollment_code</key>
<string><ENROLLMENT_CODE></string>
<key>enabled</key>
<true/>
<key>policy_max_age_minutes</key>
<integer>240</integer>
<key>browser_outage_mode</key>
<string>pass</string>
<key>browser_attachment_mode</key>
<string>confirm</string>Edge
Force installation works like in Chrome, with the preference domain com.microsoft.Edge, the ID <EDGE_EXTENSION_ID> and the update address https://edge.microsoft.com/extensionwebstorebase/v1/crx.
For Edge on macOS, this page describes only the force installation, with no example for the settings of the Browser Guard. On Edge for macOS, enrol the device in the Browser Guard window after the force installation, as in Installation for one person.
Check the result
- In the browser,
chrome://policy(Chrome) oredge://policy(Edge) shows whetherExtensionSettingsand the values of the Browser Guard arrived. - In the dashboard, the devices appear under Settings → Security → Devices once they have enrolled.
Older setups with the project API key
Since version 1.6.0, the Browser Guard no longer uses a project API key. If your device management still passes a project API key to the Browser Guard, replace it with enrollment_code. As long as Settings → Security → Transition for older Browser Guards is Open, older Browser Guards keep reporting with the project API key; close the transition once all devices appear under Devices (see Installation for one person).
Remove
Remove the entry from ExtensionSettings and the 3rdparty values, or set installation_mode to removed. Revoke devices that should no longer count under Settings → Security → Devices.
Installation for one person
Issue an enrolment code, install the Browser Guard in Chrome or Edge and enrol the device. No project API key is needed.
LangChain
AI governance for LangChain pipelines. Automatic policy checks, personal-data masking, and audit trails for every LLM call, tool invocation, and chain run.