How to Set Helperbird JSON Policy for a User Group in Google Admin

One team needs Pro before everyone else does. A Google group gets it to them without touching the rest of your domain.

Point the Console at Your Group

Groups sit outside the organizational unit tree. In Users & browsers the left panel keeps a separate Groups list, so select your group there. Add the group to that list first if it is not showing.

Once the group is selected, two settings do the work:

• Installation policy. Set it to Force install so nobody in the group has to install Helperbird themselves. That gets them Helperbird Free. If Helperbird is not on the list yet, add it the same way you would for a unit: install Helperbird through the Google Admin console.
• Policy for extensions. Your subscription key goes here, and it is what turns on Pro. The field, the JSON to paste and what each key does are on set the Helperbird JSON policy in Google Admin.

Check You Edited the Group

Look at what is selected in the left panel before you save. This is the mistake groups invite: edit the organizational unit when you meant the group and your group is untouched, while everyone in that unit gets a policy you did not intend for them.

To confirm it landed, and for the usual failures, see verify a managed deployment.

When the Pilot Ends

Push isAdminControl: false to the group. Helperbird drops your key, everyone in the group goes back to their own subscription or to Free, and the group itself stays where it is for the next cohort.

Ending it for one member instead? Take them out of the group. See set the policy for an individual user.

Validate Your Policy

Check your JSON in the Helperbird JSON Policy Validator before you push it to the group.