- Force-install the extension (
ExtensionInstallForcelist) so users can’t remove it. - Push a signed managed-config (
chrome.storage.managed) so the extension knows which org it belongs to and how to establish identity — no per-user setup.
Every profile below is produced for you. Go to App → Settings → MDM, pick
your vendor and identity mode, and download the ready-to-import
file. This page explains what’s in it; the vendor pages are the click-by-click.
Generate the profile
- Open app.inviolet.ai → Settings → MDM.
- Choose your MDM (Intune, Jamf, Kandji, or Workspace ONE) and an identity mode.
- Download the generated file — the placeholders are already substituted with
your
org_id, a freshenrollment_token, and aconfig_signature.
The managed-config payload
Every vendor format carries the same five fields under theorg.inviolet.extension managed-storage key:
Identity modes
Verify any deployment
After the profile lands, on a target device openchrome://policy/ (or
edge://policy/) and confirm ExtensionInstallForcelist and ExtensionSettings
are present. The extension then reports into your tenant — new installs appear in
the fleet view, and MCP-discovery scans begin per device.