How to Verify and Troubleshoot a Helperbird Managed Deployment

After deploying Helperbird with Intune, Group Policy, Jamf, or the Google Admin console, use this guide to confirm it worked, and to fix it if it didn't.

Step 1: Confirm the policies reached the browser

On a managed device, open the browser's policy page and click Reload policies:

• Chrome: chrome://policy
• Edge: edge://policy
• Firefox: about:policies → Active tab

You should see:

1. ExtensionInstallForcelist (Chrome/Edge) or ExtensionSettings (Firefox) listing the Helperbird ID, confirms the force-install policy arrived.
2. Helperbird's managed values (subKey, isAdminControl, and any optional keys) listed under its 3rd-party / extension policies, confirms the configuration arrived.

If the policy page shows nothing, the policy hasn't reached the device yet, force a sync (Intune) or run gpupdate /force (Group Policy), then reload.

Step 2: Confirm the subscription key activated

1. Open the extensions page (chrome://extensions, edge://extensions, or about:addons). Helperbird should be present and marked "Installed by your organization", users can't remove it.
2. Open Helperbird's Settings page and check Billing. Pro requires a valid subscription key, not only isAdminControl: true. Test one configured restriction as well as the plan status. The toolbar's on/off setting is a user-editable default, so being able to change it is expected.

Safari: There is no Chrome-style policy page. Confirm delivery in your MDM, then check Helperbird's Billing and the configured controls. A managed key is not copied into the personal subscription-key field. That field is not a reliable way to check whether the native policy arrived.

Troubleshooting

Helperbird isn't installing

• Policy not synced yet - allow up to 8 hours (Intune) or force a sync / gpupdate /force.
• Wrong ID for the browser - Chrome uses ahmapmilbkfamljbpgphfndeemhnajme; Edge uses bkibfggdahioahpokehoiimdmdjefjmd; Firefox uses [email protected]. They are not interchangeable.
• Missing update URL (Chrome) - Chrome force-install entries must end with ;https://clients2.google.com/service/update2/crx. (Edge from the Edge store needs only the ID.)
• Network blocked - the device must reach clients2.google.com (Chrome), edge.microsoft.com (Edge), or addons.mozilla.org (Firefox) to download the extension.
• A blanket block is winning - if extensions are blocked org-wide (ExtensionInstallBlocklist: *), force-install still works, but see Allowlist Helperbird when extensions are blocked.

The policy installs but Pro isn't active

• isAdminControl isn't set to true/1 - it is the master switch; without it, subKey and every other admin value are ignored.
• The subKey value is wrong or empty - re-check the value against your enterprise key.
• Value wrapper used in the wrong place - the {"Value": …} wrapper is only for the Google Admin console "Policy for extensions" field. In the Windows registry, macOS plist, and Firefox 3rdparty, values are flat (e.g. a subKey string and an isAdminControl DWORD/boolean).

Settings aren't locked / users can still change them

• Check isAdminControl. With it enabled, configured restrictions apply. With it disabled, personal settings are restored. floatingButton is intentionally user-editable; blocking the toolbar requires disableFeatures: true and FloatingButton in disabledFeatures.

Safari configuration is missing or stale

• Check the build: The native app and Safari extension must both include the new managed-configuration support. An older App Store build will not gain it from a profile alone.
• Mac: Use forced preferences in com.helperbird.Helperbird.Extension. Ordinary defaults and the containing app's preference domain are not the Mac delivery route.
• iPhone/iPad App Configuration: Target the managed containing app, com.helperbird.Helperbird, and open it after delivery or changes. This forwards settings to Safari. Its snapshot expires after seven days without refresh.
• iPhone/iPad DDM: Target the Safari extension through ExtensionConfigs, use the correct signed extension identifier, and supply the referenced private plist data asset. A JSON fragment alone is incomplete.
• Types: Use plist <true/> or <false/>, not strings. Google Admin's Value wrappers do not belong in Apple plists.
• Removal: A false gate releases all managed settings. Removing the key alone leaves feature management enabled. For the legacy iOS route, reopen the containing app to forward removal.

See Safari on Mac, iPad and iPhone setup, and the policy builder.

References

• Chrome Enterprise – Understand Chrome policy management (opens in a new tab)
• Chromium – Configuring policy for extensions (opens in a new tab)
• Mozilla – Customizing Firefox using policies.json (opens in a new tab)

Need Additional Help?

Still stuck? Contact Helperbird support with your browser, app version, delivery route, and the failing setting. Redact subscription keys and personal information from screenshots or configuration files before sharing them.