Install Helperbird for Specific Users
Give Helperbird to some of your users and not others. Pick between force install and allow install, then scope the policy to an organizational unit or a group.
On this page5 sections
Not everyone needs Helperbird. This page is about deciding who gets it and making the policy stop there.
Force Install or Let People Choose
Two settings do different jobs.
| Installation policy | What happens |
|---|---|
| Force install | Helperbird installs on its own. Nobody has to act, and nobody can remove it. |
| Allow install | Helperbird becomes available to install. Nothing happens until the user installs it. |
Pick allow install when Helperbird is for the students or staff who ask for it, and force install when it should be there for everyone in that group. See force install Helperbird for what force install covers and the extension ID for each browser.
Allow install and force install both read the same subscription key policy. If you set subKey and isAdminControl on the group, Helperbird Pro turns on for anyone in it as soon as they have the extension.
Scope It in the Google Admin Console
Chrome policy follows organizational units, so the usual pattern is a dedicated unit for the people who need Helperbird. Move those accounts in, then set the installation policy on that unit only.
- To build the unit: set up a child organizational unit.
- To add Helperbird and set the policy on it: install through the Google Admin console.
Scope It on Windows and macOS
Outside the Google Admin console, the targeting is done by whichever tool delivers the policy. Helperbird has no per-user setting of its own.
- Microsoft Intune: assign the configuration profile to a group rather than to all devices. See deploy using Microsoft Intune.
- Windows Group Policy: link the GPO to one organizational unit, or use security filtering. See deploy with Windows Group Policy.
- Jamf Pro: scope the configuration profile to a smart group. See deploy with Jamf Pro.
Run a Pilot First
Point the policy at a handful of real accounts before you widen it. Check the install arrived and Pro is active with verify and troubleshoot a managed deployment, ask that group what they think, then move more people into the unit or group.
Widening later is a membership change. You do not have to rebuild the policy.
Need Additional Help?
Ran into a snag while getting started? No worries at all. Reach out to our friendly Helperbird support team, and we'll help you smooth things out in no time.
Printed from the Helperbird Help Center · Updated August 12th, 2026
Questions? We are happy to help — helperbird.com/support