Documentation Index
Fetch the complete documentation index at: https://docs.velatir.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Deploy the Velatir browser extension to managed devices with pre-configured settings. This guide covers deployment via Microsoft Intune (Windows), SCCM / Configuration Manager (Windows), and Jamf Pro (macOS).Extension Details
| Browser | Extension ID | Store Link |
|---|---|---|
| Chrome | bbiokppljpbjgiogcoggjnfffbeiihja | Chrome Web Store |
| Edge | phgnjcoglpdamjjmidheehacjbkgkooc | Edge Add-ons |
| Firefox | velatir@velatir.com | Firefox Add-ons |
Managed Configuration
The extension accepts configuration via managed storage:| Property | Type | Description |
|---|---|---|
apiToken | string | Your Velatir API key |
organizationName | string | Display name shown in the extension |
Additional properties (
endpoint, organizationId, enabledServices) are available for advanced configurations. Contact support if you need these.Microsoft Intune (Windows)
Method A: MSI via Line-of-Business App (Recommended)
This is the simplest and most reliable method. It works on all Windows editions (Pro, Enterprise, Education), deploys to all browsers in one step, and configures the API token and organisation name automatically. Download the MSI installer:For ARM64 Windows fleets, use
VelatirExtension-arm64.msi instead. The examples below show the x64 filename; substitute the arm64 name throughout for ARM64 deployments.MSI Properties
| Property | Required | Description |
|---|---|---|
API_TOKEN | Yes | Your Velatir API token (e.g., vltr_...) |
ORGANIZATION_NAME | Yes | Your organisation’s display name shown in the extension |
ADDLOCAL | No | Comma-separated list of browsers. Defaults to all. Options: Chrome, Edge, Firefox |
ENABLE_PRIVATE_BROWSING | No | Set to 1 to enable the extension in private browsing. Applies to Edge (InPrivate) and Firefox only. Chrome does not support this on Windows. |
Steps
- Sign in to the Microsoft Intune admin center
- Navigate to Apps > All apps, then click + Add
- Select Line-of-Business app as the App Type
- Upload
VelatirExtension-x64.msi(orVelatirExtension-arm64.msifor ARM64 fleets) in the App package file field and click OK - In App information, fill in the following:
- Name: Velatir Browser Extension
- Description: Velatir AI compliance browser extension
- Publisher: Velatir
- Set Ignore app version to No
- In the Command-line arguments field, enter:
- Click OK, then click Next
- In the Assignments tab, click Add group and select the device groups to deploy to
- Click Next, review your configuration, and click Create
ADDLOCAL to the command-line arguments:
ENABLE_PRIVATE_BROWSING:
In Firefox, the extension is automatically enabled in private browsing mode. In Edge, the policy requires the extension to be allowed in InPrivate, but each user must still manually enable the extension for InPrivate mode in their browser settings.
Updating the API Token
To rotate the API token, update the command-line arguments with the new token value and redeploy. Reinstalling overwrites the existing registry keys:The MSI writes registry keys to force-install the extension from each browser’s official store and configure managed storage with your API token. When
ENABLE_PRIVATE_BROWSING=1 is set, it also configures Edge MandatoryExtensionsForInPrivateNavigation (blocks InPrivate until the user enables the extension) and Firefox private_browsing in ExtensionSettings (enables directly). Chrome does not support an Incognito policy on Windows. No files are copied beyond a marker in Program Files\Velatir. Uninstalling removes all registry keys cleanly.Method B: PowerShell Script
A single PowerShell script covers Chrome, Edge, and Firefox. It uses the Windows computer name ($env:COMPUTERNAME) as the machineId shared across all three browsers, matching the MSI’s behaviour so both deployment paths produce the same value.
Edit $ApiToken and $OrganizationName at the top of the script, then run it as Administrator or SYSTEM in 64-bit PowerShell. Set $EnablePrivateBrowsing = $true to enable the extension in Edge InPrivate and Firefox private browsing.
Configuration script (Configure-Velatir.ps1):
The script uses the Windows computer name (
$env:COMPUTERNAME) as the machineId and writes it into each browser’s managed policy. The value is stable across reruns and consistent between Chrome, Edge, and Firefox, matching the MSI deployment behaviour.To deploy to a subset of browsers, comment out the corresponding Chrome, Edge, or Firefox section in both the configuration and uninstall scripts.
In Firefox, setting
$EnablePrivateBrowsing = $true enables the extension in private browsing automatically. In Edge, the policy requires the extension to be allowed in InPrivate, but each user must still manually enable the extension for InPrivate mode in their browser settings. Chrome does not support an Incognito policy on Windows.Uninstall
To reverse everything the configuration script writes, run the script below. It’s safe to run whether or not the configuration script has been applied, and it leaves any MDM-managed policies (at forcelist indexes other than1000) untouched.
Uninstall script (Remove-Velatir.ps1):
Removing the force-install policy does not uninstall the extension from existing browser profiles. Users will simply be able to disable or remove it themselves. To force removal, block the extension first (Chrome/Edge
ExtensionInstallBlocklist, or Firefox ExtensionSettings with installation_mode: blocked) before running the uninstall script.If you deployed via the MSI rather than this script, use
msiexec /x VelatirExtension-x64.msi /qn (or VelatirExtension-arm64.msi for ARM64 fleets) — the MSI’s uninstall removes its own registry writes cleanly.Alternative: Firefox via policies.json
If you prefer apolicies.json file over registry keys for Firefox, use the following script instead of (or alongside) the Firefox section above.
Configuration script (Configure-VelatirFirefoxJson.ps1):
Method C: Settings Catalog (Force Install Only)
Use this method if you only need to force-install the extension without pre-configured settings. Users will need to enter their API token manually after installation.The Intune Settings Catalog does not support Firefox extension deployment. For Firefox, use Method A or Method B.
- Chrome
- Edge
- Sign in to the Microsoft Intune admin center
- Go to Devices > Configuration > Create > New policy
- Select:
- Platform: Windows 10 and later
- Profile type: Settings catalog
- Name your profile (e.g., “Velatir Chrome Extension”)
- Click Add settings and search for Google Chrome
- Select Google Chrome > Extensions
- Enable Configure the list of force-installed apps and extensions
- Add the following value:
- Assign to your device groups and create the profile
SCCM / Configuration Manager (Windows)
If your organisation uses Microsoft SCCM (ConfigMgr) instead of Intune, you can deploy the Velatir browser extension using the pre-built MSI installer that Velatir provides. No need to build anything. Just pass your API token and organisation name as properties at install time. Download the MSI installer:For ARM64 Windows fleets, use
VelatirExtension-arm64.msi instead. The examples below show the x64 filename; substitute the arm64 name throughout for ARM64 deployments.MSI Properties
| Property | Required | Description |
|---|---|---|
API_TOKEN | Yes | Your Velatir API token (e.g., vltr_...) |
ORGANIZATION_NAME | Yes | Your organisation’s display name shown in the extension |
ADDLOCAL | No | Comma-separated list of browsers. Defaults to all. Options: Chrome, Edge, Firefox |
ENABLE_PRIVATE_BROWSING | No | Set to 1 to enable the extension in private browsing. Applies to Edge (InPrivate) and Firefox only. |
Step 1: Create an Application
- Open the Configuration Manager Console
- Navigate to Software Library > Application Management > Applications
- Click Create Application > Manually specify the application information
- Add a Deployment Type and select Script Installer
- Set the content location to the network share containing
VelatirExtension-x64.msi(andVelatirExtension-arm64.msiif you support ARM64 endpoints)
Step 2: Configure Install Command
All browsers (Chrome, Edge, and Firefox):In Firefox, the extension is automatically enabled in private browsing mode. In Edge, the policy requires the extension to be allowed in InPrivate, but each user must still manually enable the extension for InPrivate mode in their browser settings.
Step 3: Configure Detection Method
Use a registry-based detection rule to check if the extension is already configured:- Chrome
- Edge
- Firefox
| Setting | Value |
|---|---|
| Hive | HKEY_LOCAL_MACHINE |
| Key | SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bbiokppljpbjgiogcoggjnfffbeiihja\policy |
| Value | apiToken |
| Data Type | String |
| Rule | The registry setting must exist |
Step 4: Deploy
- Right-click the application > Deploy
- Select the target Device Collection
- Set purpose to Required (auto-install) or Available (self-service via Software Center)
- Set a deployment schedule and complete the wizard
Updating the API Token
To rotate the API token, re-deploy the MSI with the new value. Reinstalling overwrites the existing registry keys:The MSI writes registry keys to force-install the extension from the browser’s official store and configure managed storage with your API token. When
ENABLE_PRIVATE_BROWSING=1 is set, it also configures private browsing for Edge (InPrivate) and Firefox. Chrome does not support an Incognito policy on Windows. No files are copied beyond a marker in Program Files\Velatir. Uninstalling removes all registry keys cleanly.Manual Registry Configuration (Windows)
If you’re not using Intune or SCCM, you can apply the same policies directly to the Windows registry. Useregedit, Group Policy Preferences, or any other tool that writes registry values. The tables below list every key, value name, and data needed.
All values are written under HKEY_LOCAL_MACHINE (HKLM) as REG_SZ (String). Run any tool you use in 64-bit context so writes don’t land under WOW6432Node.
Use the value name
1000 for the force-install entries. This avoids colliding with MDM-managed entries, which typically start at 1.- Chrome
- Edge
- Firefox
Required
Optional
Chrome does not support an Incognito policy on Windows, so there’s no equivalent to the Edge InPrivate or Firefox private-browsing entry.
| Key | Value name | Data |
|---|---|---|
SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist | 1000 | bbiokppljpbjgiogcoggjnfffbeiihja;https://clients2.google.com/service/update2/crx |
SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bbiokppljpbjgiogcoggjnfffbeiihja\policy | apiToken | Your Velatir API token (e.g. vltr_...) |
SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bbiokppljpbjgiogcoggjnfffbeiihja\policy | organizationName | Your organisation’s display name |
| Key | Value name | Data |
|---|---|---|
SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\bbiokppljpbjgiogcoggjnfffbeiihja\policy | machineId | Stable per-device identifier (e.g. computer name) |
To remove the configuration, delete the values you added. Removing the force-install entry doesn’t uninstall the extension from existing browser profiles. Users will simply be able to disable or remove it themselves.
Jamf Pro (macOS)
Configuration Profile
A single.mobileconfig profile handles force-install and managed storage for Chrome, Edge, and Firefox. Upload it to Jamf Pro as a Configuration Profile (or any MDM that supports .mobileconfig files).
Replace
vltr_yourApiTokenHere with your Velatir API token and Your Organization with your organisation’s display name before deploying.velatir-browser-extension.mobileconfig
- In Jamf Pro, go to Computers > Configuration Profiles > Upload
- Upload the
.mobileconfigfile above - Scope the profile to your target computers
- Save the configuration profile
Verification
Windows
- Trigger an Intune sync on the device or wait for the scheduled check-in
- Verify policies are applied:
- Chrome: Navigate to
chrome://policyand click Reload policies - Edge: Navigate to
edge://policyand click Reload policies - Firefox: Navigate to
about:policies
- Chrome: Navigate to
- Verify you see:
- Chrome/Edge:
ExtensionInstallForcelistwith the Velatir extension ID, and your configuredapiTokenandorganizationName - Firefox:
ExtensionSettingscontainingvelatir@velatir.comwithforce_installedmode
- Chrome/Edge:
- Confirm the extension is installed:
- Chrome:
chrome://extensions - Edge:
edge://extensions - Firefox:
about:addons(should show “Installed by enterprise policy”)
- Chrome:
macOS
- After the Jamf profile deploys, verify the plist files exist:
- Check the applied settings:
- Verify policies in the browser:
- Chrome:
chrome://policy - Edge:
edge://policy - Firefox:
about:policies
- Chrome:
- Confirm the extension is installed:
- Chrome:
chrome://extensions - Edge:
edge://extensions - Firefox:
about:addons
- Chrome:
Troubleshooting
Extension not installing
- Windows: Verify the device has synced with Intune. Check Devices > Monitor > Device configuration status
- macOS: Verify the configuration profile is installed under System Settings > Privacy & Security > Profiles
- Firefox (macOS): Ensure
EnterprisePoliciesEnabledis set totruein the plist. Firefox ignores all policies without it. - Ensure the browser is installed before the policy applies
- Check the browser’s policy page for errors (
chrome://policy,edge://policy, orabout:policiesfor Firefox)
Configuration not appearing
- Windows: Verify the script is running in 64-bit PowerShell with administrator / SYSTEM privileges
- macOS: Check that the preference domain matches exactly (
com.google.Chrome,com.microsoft.Edge, ororg.mozilla.firefox) - Firefox (Windows): If using
policies.json, check that the file exists atC:\Program Files\Mozilla Firefox\distribution\policies.json. Firefox updates can remove this directory. - Restart the browser after policy changes
Policy conflicts (Windows)
If multiple Intune profiles configureExtensionInstallForcelist, they may conflict. Use the PowerShell script (Method B) instead of Settings Catalog to avoid this issue, as the script writes to a high-numbered value name (1000) that does not collide with MDM-managed entries.
32-bit vs 64-bit context (Windows)
Registry changes may be written toWOW6432Node if the script runs in 32-bit context. Always run the configuration and uninstall scripts in 64-bit PowerShell.
Browser Extension Overview
General extension features and manual installation
Get API Token
Set up your Velatir account and get an API token