Jamf

Use Jamf Pro to deploy the Robost extension to Chrome or Edge on macOS (and optionally Windows) devices enrolled in Jamf. The policy is delivered as a Chrome Preferences plist pushed via a Jamf computer configuration profile.

Extension ID: gefljjkloapnkdffchpnakeplfmfiggh

Update manifest URL: https://storage.googleapis.com/clarity-extension-dist/update.xml

Prerequisites

• Jamf Pro admin access
• Chrome or Edge installed on target devices (managed by Jamf)
• Robost enrollment token — generate one via the Robost API (POST /settings/devices) or request one from Robost support. Self-service device enrollment in the admin console is planned.
• Target Jamf smart group or static group identified

Step 1 — Create a configuration profile

1. In Jamf Pro, go to Computers → Configuration Profiles → + New.
2. Give the profile a name (e.g. Robost Extension Policy) and set Level to Computer Level.
3. In the left-hand payload list, click + Add and choose Application & Custom Settings.

Step 2 — Add the Chrome preference domain

1. Set Preference Domain to com.google.Chrome (or com.microsoft.Edge for Edge).
2. In the Custom Settings XML field, paste the following plist. Replace the placeholder values with your actual server URL and enrollment token:

<?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>gefljjkloapnkdffchpnakeplfmfiggh;https://storage.googleapis.com/clarity-extension-dist/update.xml</string>
  </array>
  <key>ExtensionSettings</key>
  <dict>
    <key>gefljjkloapnkdffchpnakeplfmfiggh</key>
    <dict>
      <key>managed_configuration</key>
      <dict>
        <key>api_base_url</key>
        <string>https://api.robostai.com</string>
        <key>enrollment_token</key>
        <string>ctk_YOUR_ENROLLMENT_TOKEN_HERE</string>
      </dict>
    </dict>
  </dict>
</dict>
</plist>

The extension reads api_base_url and enrollment_token from chrome.storage.managed at startup. When both keys are present, the device enrolls automatically without user action.

Note

For self-hosted deployments, replace https://api.robostai.com with your internal server URL (e.g. https://robost.yourdomain.com).

Note

For Microsoft Edge, use preference domain com.microsoft.Edge instead of com.google.Chrome. The managed-config key names (api_base_url, enrollment_token) are identical.

Step 3 — Scope and deploy

1. Switch to the Scope tab and add your target smart group or static group.
2. Click Save. Jamf pushes the profile on the next device check-in (typically within 15 minutes, or immediately if you trigger Check In from the device record).

Verifying the rollout

On a managed device:

1. Open chrome://policy and click Reload policies. Confirm ExtensionInstallForcelist shows the extension ID and update URL, and that ExtensionSettings contains the managed config block.
2. Open chrome://extensions → confirm Robost is listed as Installed by your administrator.
3. Open the extension’s options page (click the puzzle icon → Robost) and confirm Enrolled shows Yes.