> ## 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.
# Browser Extension - Managed Deployment
> Browser support, managed configuration, and deployment methods for rolling the Velatir browser extension out across your organisation
Deploy the extension to managed devices with the ingest key pre-configured. Pick a method below; the browser support and configuration reference follow.
Deploying **[Velatir for Desktop](/desktop-app/overview)**? It handles all of this for you. Use this guide only if you manage browser extensions through your own Group Policy or MDM.
## Deployment methods
Force-install via GPO, PowerShell, manual registry, or the Intune Settings Catalog. Chrome, Edge, Firefox, Vivaldi, and Brave.
A single .mobileconfig profile for Chrome, Firefox, Vivaldi, and Brave.
Island, Prisma Access, Surf, and browsers with no policy surface.
## Extension IDs
| Browser | Extension ID | Store |
| --------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Chrome | `bbiokppljpbjgiogcoggjnfffbeiihja` | [Chrome Web Store](https://chromewebstore.google.com/detail/velatir/bbiokppljpbjgiogcoggjnfffbeiihja) |
| Edge | `phgnjcoglpdamjjmidheehacjbkgkooc` | [Edge Add-ons](https://microsoftedge.microsoft.com/addons/detail/velatir/phgnjcoglpdamjjmidheehacjbkgkooc) |
| Firefox | `velatir@velatir.com` | [Firefox Add-ons](https://addons.mozilla.org/en-US/firefox/addon/velatir/) |
| Vivaldi | `bbiokppljpbjgiogcoggjnfffbeiihja` | Chrome Web Store (same as Chrome) |
| Brave | `bbiokppljpbjgiogcoggjnfffbeiihja` | Chrome Web Store (same as Chrome) |
| ChatGPT Atlas (macOS) | `bbiokppljpbjgiogcoggjnfffbeiihja` | Chrome Web Store (same as Chrome) |
Vivaldi, Brave, and Atlas install the Chrome Web Store build (same extension ID, same managed-storage schema), so no separate listing is needed.
## Supported browsers
The [deployment methods](#deployment-methods) cover every browser with an enterprise policy surface.
| Browser | Deployment | Policy location |
| --------------------------------- | ------------------------- | ------------------------------------------------------------------ |
| Chrome | MSI / GPO / mobileconfig | `HKLM\SOFTWARE\Policies\Google\Chrome` / `com.google.Chrome` |
| Edge | MSI / GPO / mobileconfig | `HKLM\SOFTWARE\Policies\Microsoft\Edge` / `com.microsoft.Edge` |
| Firefox | MSI / GPO / mobileconfig | `HKLM\SOFTWARE\Policies\Mozilla\Firefox` / `org.mozilla.firefox` |
| Vivaldi | MSI / GPO / mobileconfig | `HKLM\SOFTWARE\Policies\Vivaldi` / `com.vivaldi.Vivaldi` |
| Brave | MSI / GPO / mobileconfig | `HKLM\SOFTWARE\Policies\BraveSoftware\Brave` / `com.brave.Browser` |
| ChatGPT Atlas | mobileconfig (macOS only) | `com.openai.atlas.web` |
| Island, Prisma Access, Surf | Vendor console | [Vendor-managed browsers](#vendor-managed-browsers) |
| Comet, Arc, Dia, Opera / Opera GX | Manual install | [No policy surface](#browsers-without-a-policy-surface) |
## Managed configuration
The extension reads its configuration from managed storage:
| Property | Type | Description |
| ---------- | ------ | --------------------------------------------------------------------------------------------------------- |
| `apiToken` | string | Your organisation's ingest key (e.g. `vltr_ingest_...`). Maps each machine's traces to your organisation. |
It fetches your organisation's display name from the platform, so that is not configured through managed storage.
## Vendor-managed browsers
Island, Prisma Access Browser (formerly Talon), and Surf Security run their own management plane and do not honour host-OS Chromium policy keys or preference plists. Force-install and pre-configure the extension from each vendor's admin console using these values:
| Field | Value |
| -------------------- | ------------------------------------------------- |
| Extension ID | `bbiokppljpbjgiogcoggjnfffbeiihja` |
| Update URL | `https://clients2.google.com/service/update2/crx` |
| Managed-storage JSON | `{"apiToken":"vltr_ingest_yourIngestKeyHere"}` |
| Browser | Where | Steps |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Island | Island admin console | **Device Management > Extensions > Extension Policy**: add the ID, set **Force-installed**, paste the JSON, scope to your groups. |
| Prisma Access | [Strata Cloud Manager](https://docs.paloaltonetworks.com/prisma-access-browser/administration/manage-prisma-access-browser-extensions) | In the browser policy profile under **Manage Extensions**, force-install the ID from the update URL and paste the JSON. Force-install must go through Strata Cloud Manager, not the registry. |
| Surf | Surf admin console | In extension management, add the ID as force-installed and paste the JSON. |
## Browsers without a policy surface
Comet, Arc, Dia, and Opera / Opera GX publish no framework to force-install an extension. Users install it manually:
1. Open the [Chrome Web Store listing](https://chromewebstore.google.com/detail/velatir/bbiokppljpbjgiogcoggjnfffbeiihja).
2. Click **Add to browser** (on Opera, via Opera's "Install Chrome Extensions" add-on).
3. Open the Velatir popup and enter the ingest key.
We will add these to the MSI / mobileconfig if and when the vendors publish a policy reference.
## Verify
After the profile or policy applies:
* Open the browser's policy page and confirm the Velatir extension ID is force-installed with your `apiToken`: `chrome://policy`, `edge://policy`, `vivaldi://policy`, `brave://policy`, or `about:policies` (Firefox shows `velatir@velatir.com` set to `force_installed`).
* Open the extensions page and confirm Velatir is present: `chrome://extensions`, `edge://extensions`, `about:addons` (Firefox: "Installed by enterprise policy"), `vivaldi://extensions`, `brave://extensions`. For Atlas, use the extensions panel in the Atlas menu.
* On Windows, trigger an Intune sync first, then **Reload policies** on the policy page.
* On macOS, confirm the managed-preference plist exists, e.g. `ls /Library/Managed\ Preferences/com.google.Chrome.plist`.
## Troubleshoot
* **Extension not installing**: confirm the browser was installed before the policy applied, and check the policy page for errors. Windows: confirm the device synced with Intune (**Devices > Monitor > Device configuration status**). macOS: confirm the profile is installed under **System Settings > Privacy & Security > Profiles**. Firefox (macOS): set `EnterprisePoliciesEnabled` to `true`, or Firefox ignores all policies.
* **Configuration not appearing**: restart the browser after policy changes. Windows: run scripts in 64-bit PowerShell with administrator / SYSTEM rights, or registry writes land under `WOW6432Node`. macOS: match the preference domain exactly. Firefox (Windows) with `policies.json`: confirm the file is at `C:\Program Files\Mozilla Firefox\distribution\policies.json`, which Firefox updates can remove.
* **Collect diagnostics for support**: click five times anywhere inside the extension window to open its diagnostics view. It shows the configured endpoint, whether the ingest key is accepted, the service catalogue state, and the connection to the desktop agent. Use **Copy report** and paste the result into your support request.
* **Policy conflicts (Windows)**: if multiple Intune profiles set `ExtensionInstallForcelist`, use the [PowerShell script](/setup/browser-extension-windows-advanced) instead of the Settings Catalog. It writes to a high value name (`1000`) that does not collide with MDM-managed entries.
***
Features and manual installation
Set up your account and get your ingest key