Set Helperbird JSON Policy for Individual Users
Give one person the Helperbird policy in Google Admin without touching anyone else, check it reached only them, and take it back when they are done with it.
On this page
One student has an accommodation. One teacher wants to try Pro before you buy for the department. Nobody else should notice.
Policy Goes to Units and Groups, Not to People
The left panel in Google Admin lists organizational units and groups. There is no row for a single person.
So reaching one person means putting them in a container that holds one person. Both routes below do that, and both take the same policy.
Two Ways to Reach One Person
| Route | Best when | Follow |
|---|---|---|
| A group with one member | A trial, a short-term accommodation, or a pilot you will add people to later | Set the policy for a user group |
| A child unit with one member | You already manage that person's Chrome settings by unit | Set up a child organizational unit |
Reach for the group. Moving somebody into a child unit changes every Chrome policy that applies to them, not only Helperbird's, and you have to move them back afterwards. Adding them to a group leaves their unit alone.
The policy you paste is the same one everyone else gets. It is on set the Helperbird JSON policy in Google Admin, along with where the field lives and every key you can add.
Check It Landed on the Right Person
Ask that person to open Helperbird's settings and look at Account. Once the policy has reached them it reads Managed by your organization.
Then check somebody outside the group or unit. Their Account should say nothing of the kind and their own plan should be untouched. That second check is the one that matters here, because the failure this page exists to avoid is a policy that went wider than you meant.
For the browser-level checks, chrome://policy and the rest, see verify and troubleshoot a managed deployment.
Taking It Back
An accommodation ends, or somebody leaves. Take the policy back the way you gave it.
- Group route. Remove the person from the group. Leave the group and its policy in place for whoever needs it next.
- Child unit route. Move them back to the unit they came from.
Helperbird then removes the organization key from their browser, and they fall back to their own subscription, or to Free. Nobody else in your domain changes.
Do not set isAdminControl to false to remove one person. That switch belongs to the whole unit or group, so flipping it takes Pro off everyone inside it.
Validate Your Policy
Check your JSON in the Helperbird JSON Policy Validator before you push it.
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 13th, 2026
Questions? We are happy to help — helperbird.com/support