Skip to main content

Overview

Organizations can deploy the Velatir browser extension to all users with pre-configured settings using Chromeโ€™s managed storage API. This allows IT administrators to:
  • Pre-configure API endpoints and credentials
  • Lock settings to prevent user modification
  • Deploy via Group Policy, MDM, or managed preferences
  • Display organization branding in the extension

Extension Details

PropertyValue
Extension IDcaphhifinnebobmbailgabbcjhdfdjij
CRX Downloadhttps://cdn.velatir.com/chrome-extension.crx
Update Manifesthttps://cdn.velatir.com/update.xml

Managed Configuration Options

The following settings can be configured via enterprise policy:
PropertyTypeDescription
endpointstringVelatir API endpoint (e.g., api.velatir.com)
apiTokenstringX-API-Key for authentication
organizationNamestringDisplay name shown in โ€œManaged byโ€ banner
organizationIdstringOrganization identifier for audit logs
enabledServicesarrayList of service names to monitor (empty = all)

Microsoft Intune

Microsoft Intune provides multiple methods to deploy and configure Chrome extensions. Choose the approach that best fits your environment.

Prerequisites

  • Microsoft Intune admin access
  • Chrome ADMX templates (for Administrative Templates method)
  • Target devices enrolled in Intune
The Settings Catalog provides the most straightforward approach for deploying Chrome extensions.
  1. Sign in to the Microsoft Intune admin center
  2. Navigate to Devices โ†’ Configuration profiles โ†’ Create profile
  3. Select:
    • Platform: Windows 10 and later
    • Profile type: Settings catalog
  4. Click Create
  5. Name your profile (e.g., โ€œVelatir Browser Extensionโ€)
  6. Click Add settings and search for โ€œGoogle Chromeโ€
  7. Expand Google Chrome โ†’ Extensions
  8. Add the following settings:
Configure the list of force-installed apps and extensions:
caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml
Allowed extensions (optional - if using an allowlist):
caphhifinnebobmbailgabbcjhdfdjij
  1. Click Next through Scope tags
  2. Assign to your target device groups
  3. Click Create

Method 2: Administrative Templates (ADMX)

For organizations already using Chrome ADMX templates:
  1. Download Chrome ADMX templates if not already imported
  2. In Intune, go to Devices โ†’ Configuration profiles โ†’ Create profile
  3. Select:
    • Platform: Windows 10 and later
    • Profile type: Templates โ†’ Administrative Templates
  4. Navigate to: Computer Configuration โ†’ Google Chrome โ†’ Extensions
  5. Configure Configure the list of force-installed apps and extensions:
    • Set to Enabled
    • Add: caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml

Method 3: Custom OMA-URI

For advanced scenarios or when ADMX templates arenโ€™t available:
  1. Create a new Configuration profile
  2. Select Templates โ†’ Custom
  3. Add an OMA-URI setting:
SettingValue
NameChrome Force Install Extension
OMA-URI./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Extensions/ExtensionInstallForcelist
Data typeString
Value<enabled/><data id="ExtensionInstallForcelistDesc" value="1&#xF000;caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml"/>

Configuring Extension Policy via Intune

To pre-configure the extension settings (API endpoint, token, etc.), use the ExtensionSettings policy: Settings Catalog method:
  1. Search for โ€œConfigure extension management settingsโ€ under Google Chrome โ†’ Extensions
  2. Add the following JSON:
{
  "caphhifinnebobmbailgabbcjhdfdjij": {
    "installation_mode": "force_installed",
    "update_url": "https://cdn.velatir.com/update.xml",
    "toolbar_pin": "force_pinned"
  }
}
For extension-specific policy settings, use the 3rdparty policy:
{
  "3rdparty": {
    "extensions": {
      "caphhifinnebobmbailgabbcjhdfdjij": {
        "endpoint": "api.velatir.com",
        "apiToken": "your-api-token-here",
        "organizationName": "Acme Corporation",
        "organizationId": "acme-corp"
      }
    }
  }
}

Microsoft Edge Deployment via Intune

For Microsoft Edge (Chromium-based), the process is similar:
  1. In Settings Catalog, search for โ€œMicrosoft Edgeโ€ instead of โ€œGoogle Chromeโ€
  2. Use the same extension ID: caphhifinnebobmbailgabbcjhdfdjij
  3. Configure Configure the list of force-installed extensions:
caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml
The same CRX file and extension ID work for both Chrome and Edge since Edge is Chromium-based.

Windows (Group Policy)

Registry Method

Create a .reg file with your configuration:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist]
"1"="caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml"

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\caphhifinnebobmbailgabbcjhdfdjij\policy]
"endpoint"="api.velatir.com"
"apiToken"="your-api-token-here"
"organizationName"="Acme Corporation"
"organizationId"="acme-corp"

Group Policy (ADMX)

  1. Download the Chrome ADMX templates
  2. Add them to your Group Policy Central Store
  3. Navigate to: Computer Configuration > Administrative Templates > Google Chrome > Extensions
  4. Configure Configure the list of force-installed apps and extensions:
    • Add: caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml
  5. Configure Extension management settings with JSON:
{
  "caphhifinnebobmbailgabbcjhdfdjij": {
    "installation_mode": "force_installed",
    "update_url": "https://cdn.velatir.com/update.xml",
    "toolbar_pin": "force_pinned",
    "policy": {
      "endpoint": "api.velatir.com",
      "apiToken": "your-api-token-here",
      "organizationName": "Acme Corporation",
      "organizationId": "acme-corp"
    }
  }
}

macOS (Managed Preferences)

Configuration Profile

Create a .mobileconfig file or use your MDM to deploy a configuration profile: Domain: com.google.Chrome
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>ExtensionInstallForcelist</key>
  <array>
    <string>caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml</string>
  </array>
  <key>3rdparty</key>
  <dict>
    <key>extensions</key>
    <dict>
      <key>caphhifinnebobmbailgabbcjhdfdjij</key>
      <dict>
        <key>endpoint</key>
        <string>api.velatir.com</string>
        <key>apiToken</key>
        <string>your-api-token-here</string>
        <key>organizationName</key>
        <string>Acme Corporation</string>
        <key>organizationId</key>
        <string>acme-corp</string>
      </dict>
    </dict>
  </dict>
</dict>
</plist>

Manual Deployment

Place the plist file at:
/Library/Managed Preferences/com.google.Chrome.plist

Linux / ChromeOS (JSON Policy)

System-wide Policy

Create a JSON file at /etc/opt/chrome/policies/managed/velatir.json:
{
  "ExtensionInstallForcelist": [
    "caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml"
  ],
  "3rdparty": {
    "extensions": {
      "caphhifinnebobmbailgabbcjhdfdjij": {
        "endpoint": "api.velatir.com",
        "apiToken": "your-api-token-here",
        "organizationName": "Acme Corporation",
        "organizationId": "acme-corp"
      }
    }
  }
}
Set appropriate permissions:
sudo chmod 644 /etc/opt/chrome/policies/managed/velatir.json

Google Workspace Admin Console

For organizations using Chrome Browser Cloud Management:
  1. Sign in to the Google Admin console
  2. Navigate to Devices > Chrome > Apps & extensions > Users & browsers
  3. Select the organizational unit to configure
  4. Click the + button and select Add Chrome app or extension by ID
  5. Enter the extension ID: caphhifinnebobmbailgabbcjhdfdjij
  6. For Installation policy, select Force install
  7. For Update URL, enter: https://cdn.velatir.com/update.xml
  8. Click the extension and select Policy for extensions
  9. Enter your JSON configuration:
{
  "endpoint": "api.velatir.com",
  "apiToken": "your-api-token-here",
  "organizationName": "Acme Corporation",
  "organizationId": "acme-corp"
}
  1. Click Save

JAMF Pro (macOS)

  1. Create a new Configuration Profile
  2. Add a Custom Settings payload
  3. Set the preference domain to com.google.Chrome
  4. Upload or paste the following plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>ExtensionInstallForcelist</key>
  <array>
    <string>caphhifinnebobmbailgabbcjhdfdjij;https://cdn.velatir.com/update.xml</string>
  </array>
  <key>3rdparty</key>
  <dict>
    <key>extensions</key>
    <dict>
      <key>caphhifinnebobmbailgabbcjhdfdjij</key>
      <dict>
        <key>endpoint</key>
        <string>api.velatir.com</string>
        <key>apiToken</key>
        <string>your-api-token-here</string>
        <key>organizationName</key>
        <string>Acme Corporation</string>
        <key>organizationId</key>
        <string>acme-corp</string>
      </dict>
    </dict>
  </dict>
</dict>
</plist>

Update Manifest (update.xml)

The update manifest at https://cdn.velatir.com/update.xml follows this format:
<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
  <app appid='caphhifinnebobmbailgabbcjhdfdjij'>
    <updatecheck codebase='https://cdn.velatir.com/chrome-extension.crx' version='1.0.0' />
  </app>
</gupdate>
This manifest is hosted by Velatir and automatically updated when new extension versions are released.

Verification

After deployment, verify the configuration is applied:
  1. Open Chrome and navigate to chrome://policy
  2. Click Reload policies to refresh
  3. Search for caphhifinnebobmbailgabbcjhdfdjij or โ€œExtensionโ€
  4. Verify the managed settings appear under the extension policies
  5. Navigate to chrome://extensions - the Velatir extension should show as installed
  6. Open the Velatir extension - you should see โ€œManaged by [Organization Name]โ€œ

Troubleshooting

Settings not appearing

  • Verify the extension ID is caphhifinnebobmbailgabbcjhdfdjij
  • Check that policy files have correct permissions
  • Restart Chrome after policy changes
  • On Windows, run gpupdate /force
  • In Intune, trigger a device sync

Extension not installing

  • Ensure force installation policy is applied
  • Check chrome://extensions for error messages
  • Verify network access to cdn.velatir.com
  • Check chrome://policy for any policy errors

API connection issues

  • Verify the API token is valid
  • Check firewall rules for api.velatir.com
  • Review extension console for errors (chrome://extensions > Details > Inspect views)

Intune-specific issues

  • Verify the device has synced with Intune recently
  • Check Devices โ†’ Monitor โ†’ Device configuration status
  • Ensure Chrome is installed before the policy applies
  • For Edge, verify youโ€™re using the Edge-specific policies