How to Deploy Helperbird with Jamf Pro (macOS)

Choose the browser you are deploying. Safari uses Helperbird's native Apple managed configuration. Chrome uses Chrome extension policies. The preference domains and installation steps are different; do not reuse a Chrome payload for Safari.

Use the Helperbird policy builder to create a macOS configuration profile or plist. For iPhone and iPad, follow the managed iPad setup instead.

For the full Safari profile workflow, see creating a Helperbird mobileconfig for Mac. Mobile administrators can use the dedicated iPhone and iPad AppConfig guide or declarative MDM guide.

Google Chrome must be installed on the Macs (deploy it via Jamf if needed). On macOS, Chrome reads managed policies from the com.google.Chrome preference domain, and per-extension managed configuration from com.google.Chrome.extensions.<extension-id>.

Before You Start

• A Jamf Pro account with permission to create configuration profiles.
• Helperbird's Chrome extension ID: ahmapmilbkfamljbpgphfndeemhnajme

Safari on Mac

Use a signed Helperbird Apple build containing the 2026.9.6 managed-configuration support. Installing a profile alone does not add this support to an older app. Install Helperbird and enable its Safari extension separately from configuring its settings.

1. Open the policy builder and choose the Safari/macOS format.
2. Enable Admin control, enter your organization's subscription key if needed, and choose any feature restrictions or toolbar defaults.
3. Download the macOS .mobileconfig, or the .plist for an Application & Custom Settings payload in Jamf Pro.
4. For a custom settings payload, use preference domain com.helperbird.Helperbird.Extension. This is the Safari extension, not the containing app.
5. Scope the profile to a test Mac first. After delivery, open Helperbird in Safari and check its Billing status and one configured feature.

Mac settings must be forced managed preferences. Ordinary defaults write values are ignored. Jamf's Application & Custom Settings documentation (opens in a new tab) explains how its preference-domain payload works.

Safari accepts the same ten Helperbird policy keys as Chrome and Edge. isAdminControl must be the boolean true for any of them to apply. With that gate enabled, an empty subKey leaves feature management active without supplying a managed subscription. A key must pass subscription validation; the policy cannot grant Pro by itself.

floatingButton is a user-editable starting state, not a lock. Users can turn the toolbar off or back on. To block it, enable disableFeatures and include the case-sensitive code FloatingButton in disabledFeatures.

To release all managed settings, set isAdminControl to false or remove the profile. Personal settings become active again. Test key rotation, removal, and feature restrictions on an enrolled Mac before wider deployment. Keep downloaded configuration files private because they can contain your subscription key.

The following three steps cover Chrome on macOS, not Safari.

Step 1: Force-install Helperbird

1. In Jamf Pro, go to Computers > Configuration Profiles > New.
2. Add an Application & Custom Settings > External Applications payload. Set:

• Source: Custom Schema (or Upload, depending on your Jamf version)
• Preference Domain: com.google.Chrome

3. Provide this property list, which force-installs Helperbird from the Chrome Web Store:

<dict>
<key>ExtensionInstallForcelist</key>
<array>
<string>ahmapmilbkfamljbpgphfndeemhnajme;https://clients2.google.com/service/update2/crx</string>
</array>
</dict>

Step 2: Activate Helperbird Pro

To unlock Pro, push your subscription key as managed configuration for the extension. Add a second Application & Custom Settings payload to the same profile:

• Preference Domain: com.google.Chrome.extensions.ahmapmilbkfamljbpgphfndeemhnajme
• Property list:

<dict>
<key>subKey</key>
<string>YOUR-ENTERPRISE-SUBSCRIPTION-KEY</string>
<key>isAdminControl</key>
<true/>
</dict>

Notes:

• isAdminControl is the master switch. It must be true or none of the admin values (including subKey) apply.
• Keys are flat, matching the names in the JSON policy. Optional keys: floatingButton (<true/>), floatingButtonPosition (<string>, left or right, default left), disableFeatures + disabledFeatures (<array>), excludedDomains + excludedDomainsList, enableTtsWordHighlight, ttsWordHighlightColor (<string>).
• For Microsoft Edge on macOS, use the same approach with preference domains com.microsoft.Edge and com.microsoft.Edge.extensions.bkibfggdahioahpokehoiimdmdjefjmd.

Step 3: Scope and Verify

1. On the Scope tab, target the Macs or smart group that should receive Helperbird, then Save.
2. On a managed Mac (after the profile installs), open Chrome and go to chrome://policy → Reload policies. You should see Helperbird in ExtensionInstallForcelist and the subKey/isAdminControl values under its 3rd-party policies.
3. Helperbird appears marked "Installed by your organization" with Pro active.

References

• Chromium – Configuring policy for extensions (macOS managed preferences) (opens in a new tab)
• Chrome Enterprise – Set Chrome Browser policies on Mac (opens in a new tab)
• Jamf Pro – Application & Custom Settings (opens in a new tab)

Need Additional Help?

Reach out to our Helperbird support team and we'll help you deploy with Jamf.