How to Disable Helperbird Features Using JSON Policy - Admins

This guide shows you how to disable specific Helperbird features for users in your organization using the Google Admin Console and managed JSON policy.

This is useful if you want to limit access to certain tools (for example, writing or editing features) while keeping the rest of Helperbird available.

Before You Start

Make sure that:

• Helperbird is already added to your Organizational Unit (OU)
• You have administrator access to admin.google.com (opens in a new tab)
• You have already enabled admin control using isAdminControl

If you haven’t done this yet, follow our guide: How to Set Helperbird JSON Policy in Google Admin

Understanding Feature Types in Helperbird

Helperbird features are grouped into two types:

Main Features (All Features)

• Appear in Helperbird’s main feature list
• Disabling one removes it from the primary interface

Quick Features (Quick Actions)

• Appear in Quick Actions
• Disabling one removes it from the Quick Actions menu

Note: Some features appear in both places. Disabling them will remove the feature everywhere it appears.

How Feature Disabling Works

Helperbird uses two policy values:

• disableFeatures - turns feature disabling on or off
• disabledFeatures - the list of feature codes to disable

If disableFeatures is set to false, no features are disabled, even if a list exists.

Starter JSON Template (Recommended)

If you’re not sure where to start, use this starter template. It enables admin control and feature disabling, but does not disable anything yet.

{
 "subKey": {
 "Value": "YOUR SUBSCRIPTION KEY"
 },
 "isAdminControl": {
 "Value": true
 },
 "disableFeatures": {
 "Value": true
 },
 "disabledFeatures": {
 "Value": []
 }
}

Add feature codes from the tables below into the disabledFeatures list.

Example: Disable the Helperbird Editor Feature

To disable the Helperbird Editor feature everywhere it appears, add:

{
 "subKey": {
 "Value": "YOUR SUBSCRIPTION KEY"
 },
 "isAdminControl": {
 "Value": true
 },
 "disableFeatures": {
 "Value": true
 },
 "disabledFeatures": {
 "Value": [
 "EditorReader"
 ]
 }
}

Commonly Disabled Features (Example)

The following features are commonly disabled in managed environments:

EditorReader
VoiceTypingOptions
ScreenshotOptions

Example JSON:

{
 "subKey": {
 "Value": "YOUR SUBSCRIPTION KEY"
 },
 "isAdminControl": {
 "Value": true
 },
 "disableFeatures": {
 "Value": true
 },
 "disabledFeatures": {
 "Value": [
 "EditorReader",
 "VoiceTypingOptions",
 "EditWebsite",
 "ScreenshotOptions"
 ]
 }
}

Important Notes

• Feature codes are case-sensitive and must match the tables exactly
• Features that appear in both Main Features and Quick Actions will be removed from both
• Unknown or invalid feature codes are safely ignored

Verifying and Troubleshooting

If changes don’t appear immediately:

• Restart Chrome, or
• Visit chrome://policy and click Reload policies

Double-check:

• The correct OU is selected
• JSON formatting is valid
• disableFeatures is set to true

Validate Your Policy

Use our JSON Policy Validator to check your policy for errors, invalid feature codes, and see exactly what each setting does before deploying.

Need Additional Help?

If you need help finding a feature code or validating your policy, reach out to our Helperbird support team and we'll help you out!