Skip to main content
A Jamf Pro Configuration Profile with two Application & Custom Settings payloads: one to force-install the extension, one to push its managed-config.
Generate your profile first: App → Settings → MDM → Jamf Pro downloads inviolet-extension.jamf.plist with your org_id, enrollment_token, and config_signature already substituted. See the MDM overview for what the payload contains.

​
Prerequisites

  • Jamf Pro administrator access
  • The generated inviolet-extension.jamf.plist from Settings → MDM
  • A pilot smart group of Macs

​
1. Create a computer Configuration Profile

In Jamf Pro → Computers → Configuration Profiles → New, add two Application & Custom Settings payloads (Upload / custom schema).

​
2. Payload A — force-install

  • Preference domain: com.google.Chrome
  • Set ExtensionInstallForcelist with the Inviolet force-install entry from the generated plist.

​
3. Payload B — managed config

  • Preference domain: com.google.Chrome.extensions.<inviolet-extension-id>
  • Add the org.inviolet.extension managed-storage dictionary (org_id, enrollment_token, expected_user_email_template, identity_mode, config_signature) exactly as shown in the generated plist.

​
4. Scope

Scope the profile to a pilot smart group, then broaden.

​
5. Verify

On a target Mac, open chrome://policy/ and confirm both the force-install and managed-storage entries are present. The extension then enrolls into your tenant.