Policy Builder & Validator
One set of settings, the right file for your devices. Create a policy for Chrome, Edge or Safari, or check a configuration you already have.
Generated in your browser. Your configuration is not uploaded or saved by this tool. Downloads contain your key: store and share them securely.
Deployment guides: Mac configuration profiles, iPhone and iPad AppConfig, and declarative MDM.
Choose your devices. We will provide the matching format and deployment steps.
Advanced: requires iOS/iPadOS 18.4+ and MDM support for ManagedApp. Use the data asset identifier from your MDM, and verify the team ID against your signed release. This produces a fragment, not a complete deployment declaration.
Requires a Helperbird Apple build with managed-feature support. Generating a file does not install Helperbird, enable its extension or enroll a device.
Optional. Add your organization’s key to provide Pro after Helperbird validates it. Leave it empty to configure features without supplying a subscription.
This is the master switch. Turn it off to release organization control; the supplied key and feature settings will no longer apply. The toolbar visibility setting is a user-editable default, not a lock.
Hide features you do not want available, so they do not appear in Helperbird at all. Most schools leave this off and only use it for exams or a specific class.
Disable Helperbird on specific websites. Users will see a badge letting them know Helperbird is turned off on those pages. Maximum 10 domains.
Subdomains are automatically included. Adding example.com also covers sub.example.com.
Set the toolbar’s initial state and position. Users can still turn it off or back on, and their choice wins over later policy refreshes. To block it entirely, disable the FloatingButton feature above. Useful in kiosk setups where the browser toolbar is hidden.
Read-aloud highlighting (optional)
Leave this unmanaged to keep each user’s settings.
This updates as you change the answers above.
Where this goes in Google Admin Console
- 1. Open admin.google.com and go to Devices › Chrome › Apps & extensions › Users & browsers.
- 2. Pick the organisational unit you want this to apply to, on the left.
- 3. Find Helperbird in the list, or add it by ID: ahmapmilbkfamljbpgphfndeemhnajme
- 4. Paste the JSON above into Policy for extensions, then Save.
Full walkthrough: Set the Helperbird JSON policy in Google Admin.
Where this goes in Intune
Chromium reads managed configuration from the Windows registry, and Intune has no built-in setting for it, so this is delivered as a platform script.
- 1. Force-install Helperbird first, otherwise there is nothing for the key to activate.
- 2. Go to Devices › Scripts and remediations › Platform scripts › Add › Windows 10 and later.
- 3. Upload the script above with Run this script using the logged-on credentials set to No, and Run script in 64-bit PowerShell set to Yes.
- 4. Sync the device, then open edge://policy and press Reload policies to check it landed.
On Group Policy instead? The same values go under Computer Configuration › Preferences › Windows Settings › Registry. Full walkthrough: Deploy Helperbird using Microsoft Intune.
Deploy to Safari on Mac
- Install a signed Helperbird build with managed-feature support and enable its Safari extension.
- For the .mobileconfig, upload it as a computer configuration profile in your MDM. It targets all users on the scoped Macs. The download is unsigned; your MDM handles delivery. Keep the profile identifier stable when updating it.
- For the .plist, use Jamf’s Application & Custom Settings with preference domain
com.helperbird.Helperbird.Extension. - Scope to a test Mac first. Open Helperbird and check that the expected features and toolbar settings apply.
A Mac .mobileconfig is not an iPhone/iPad AppConfig file. To release control, turn Organization control off, download again and replace the policy.
Jamf’s Mac deployment guide (opens a new tab)Deploy to iPhone & iPad
- Enroll your test device in an Apple MDM and distribute Helperbird as a managed app. A standalone profile installed from Safari does not deliver this app configuration.
- For Managed App Configuration, supply the plist dictionary in the app’s configuration editor. Target app ID
com.helperbird.Helperbird. Do not add acom.apple.configuration.managedwrapper. If your editor expects only a dictionary, paste the section from<dict>to</dict>. - Open the containing Helperbird app after each legacy configuration change, then reopen its Safari extension. The iOS app and extension must both be signed with the
group.com.helperbird.HelperbirdApp Group. Managed legacy snapshots expire after seven days without the app refreshing them.
Using declarative MDM instead?
Download both files. Host the plist privately as a com.apple.asset.data asset with content type application/x-plist. Merge the generated ExtensionConfigs fragment into your managed app declaration, preserving its other fields. This targets the extension directly and does not require the containing app’s legacy refresh. After adopting DDM, it remains authoritative; removing it must not revive an older legacy key.