On this page
Before you start
Worth two minutes so the rollout matches what you expect.
This is a Google Admin console procedure. It applies to managed Chrome on ChromeOS, Windows, macOS, and Linux, for users signed in to a browser profile managed by your Workspace domain. You need an admin account with the Chrome management privilege, found under Services and Chrome Management.
What this sets up
- Haven installs automatically on every targeted user's Chrome, silently, with no action from them
- The Haven icon is pinned to the toolbar so it cannot be hidden
- Targeting by organizational unit or by group, so you can pilot before going fleet wide
What it does not set up
- Membership in your Haven organization. Installing Haven and joining your organization are two separate steps
- A signed in Haven session. People still sign in to Haven, or accept an invite, as normal
- Microsoft Edge. This guide covers Chrome only
Deploying Haven places and pins the extension. Connecting those people to your Haven organization happens through Haven's invite and sign in flow. If you want everyone mapped to a specific organization as part of the rollout, email support@starthaven.com and we will walk through it with you.
The value you need
Everything below runs off this one identifier.
https://clients2.google.com/service/update2/crxOnly needed if you add Haven by ID rather than from the store.
Set it up in the Admin console
Recommended for most organizations.
-
Sign in to the Google Admin console with an admin account that has Chrome management rights.
-
Go to:
Devices › Chrome › Apps & extensions › Users & browsers -
In the left hand tree, select the organizational unit or group you want Haven deployed to. Settings apply to everyone below the unit you select unless something lower overrides them.
If you want to pilot first, select a test unit here and move the policy up the tree later.
-
Click the + button in the lower right and choose Add from Chrome Web Store.
-
Search for Haven, or paste the extension ID. Check that the listing shows the publisher starthaven.com, then select it.
-
In the Haven row, set Installation policy to:
Force install + pin to browser toolbarPlain Force install also works, but it lets the icon collapse into the puzzle piece menu. Choose the pin version so the icon stays visible.
-
Leave Permissions at the default unless your security policy requires a review. Haven needs its declared permissions to work.
-
Click Save in the top right.
Changes reach managed browsers on their next policy refresh, usually within minutes. To force it on a specific machine, open chrome://policy and click Reload policies.
Set it up with a policy file
For teams managing Chrome policy through JSON or the registry, alongside tools like Intune, Jamf, or an RMM.
Rather than using the Apps and extensions screen, add Haven through the ExtensionSettings policy:
{
"ExtensionSettings": {
"becohfjpbibfjlfeiphcjecdjbdhomgi": {
"installation_mode": "force_installed",
"update_url": "https://clients2.google.com/service/update2/crx",
"toolbar_pin": "force_pinned"
}
}
}
force_installed installs Haven automatically and prevents users removing it. force_pinned pins the icon and prevents users unpinning it. The update_url must be the Chrome Web Store address above so the browser pulls Haven from the store.
Deliver the policy through whatever manages your target browsers: Group Policy on Windows, a configuration profile on macOS, or the JSON policy file on Linux and ChromeOS.
Do not use both the Admin console and a policy file for the same organizational unit. Choose one source of truth so the two cannot issue conflicting policy.
Confirm the rollout worked
Check these three things on a machine you targeted.
- Open
chrome://extensions. Haven appears, switched on, labelled Installed by your administrator, with no Remove button. - The Haven icon is visible and pinned on the toolbar, not tucked inside the puzzle piece menu.
- Open
chrome://policy. AnExtensionInstallForcelistorExtensionSettingsentry lists the Haven extension ID. Click Reload policies if it has not appeared yet.
Troubleshooting
The five things that come up most often.
Haven did not install on some machines
Either the browser profile is not enrolled in your Workspace domain, or the user sits outside the organizational unit or group you targeted.
Open chrome://policy on the machine and look for a managed status or a CloudManagementEnrollmentToken entry. If neither is there, the profile is not managed. If the profile is managed, check which organizational unit the user belongs to in the Admin console.
Haven installed but the icon is not pinned
The installation policy is set to plain Force install rather than Force install + pin to browser toolbar. Change it in the Admin console, or add "toolbar_pin": "force_pinned" if you are using a policy file.
The icon is still hidden after I turned on pinning
The pin setting applies on the next policy refresh. On the machine, open chrome://policy, click Reload policies, then restart Chrome.
My team has Haven installed but they are not in our Haven organization
That is expected. Deployment installs and pins the extension. People join your Haven organization separately, through an invite or by signing in.
If you want help mapping everyone to your organization, email support@starthaven.com.
Can I pilot Haven with a small group before rolling it out to everyone?
Yes. Apply the policy to a test organizational unit first, confirm the three checks above, then move the policy up the tree to cover the rest of your organization.
Still stuck?
Tell us the symptom and what you see at chrome://policy on an affected machine, and we will help you sort it.