Beta mumus is in public beta: free while we test it with real teams. Found something odd? Tell us.

Install a browser extension for the whole company, with IT in control

Many companies block browser extensions, and for good reason: an extension can read the pages it runs on. Blocking all of them is not the only option, though. Chrome and Edge let IT allow or install exactly the extensions the company has reviewed, for every managed browser, while everything else stays blocked.

Allow one extension, keep the rest blocked

Three browser policies cover almost every setup. They exist with the same names in Google Chrome and Microsoft Edge.

  • ExtensionInstallBlocklist with "*": users cannot install any extension on their own.
  • ExtensionInstallAllowlist: the reviewed extensions users may install themselves, by ID.
  • ExtensionInstallForcelist: extensions installed for everyone, which users cannot remove.

An extension is identified by its ID, the 32 letters at the end of its Chrome Web Store address. The update address for Chrome Web Store extensions is https://clients2.google.com/service/update2/crx; Edge accepts it too.

Google Admin console (managed Chrome)

  1. Open Devices, then Chrome, then Apps and extensions, then Users and browsers.
  2. Choose the organisational unit, add the extension from the Chrome Web Store by its ID.
  3. Set the installation policy to "Force install" or "Allow install".

Windows (Group Policy or Intune)

With the Chrome or Edge ADMX templates, the policies are under Extensions. As registry values, a force-installed extension looks like this (Edge uses Microsoft\Edge instead of Google\Chrome):

HKLM\Software\Policies\Google\Chrome\ExtensionInstallForcelist
  1 = "<extension-id>;https://clients2.google.com/service/update2/crx"
HKLM\Software\Policies\Google\Chrome\ExtensionInstallBlocklist
  1 = "*"

In Intune, use a settings catalog profile for Google Chrome or Microsoft Edge with the same policy names.

macOS (configuration profile)

Deploy a configuration profile for the preference domain com.google.Chrome (or com.microsoft.Edge) with your device management tool:

<key>ExtensionInstallForcelist</key>
<array>
  <string><extension-id>;https://clients2.google.com/service/update2/crx</string>
</array>
<key>ExtensionInstallBlocklist</key>
<array><string>*</string></array>

What to review before allowing an extension

  • Which permissions it asks for, and whether it asks for access to all websites or only when the user allows it
  • Where it sends data, and whether the vendor offers a data processing agreement
  • Who publishes it, how it is updated, and whether a version can be pinned
  • Whether it works with your single sign-on and two-factor rules

If no extension is possible at all

Some environments allow no extension, for example locked-down kiosks or customer devices. Then use reporting channels that need no installation: a feedback widget on the website itself, a connector in the content management system, or reporting by e-mail.

The mumus extension asks for access to a website only when the user reports on it (optional host permissions), stores its sign-in token only in its background worker and sends it only to your mumus address. Without the extension, the website widget and the WordPress and TYPO3 connectors let people report from the website or its backend, and report by e-mail works from any device.

Frequently asked questions

Can users remove a force-installed extension?

No. Extensions installed with ExtensionInstallForcelist cannot be disabled or removed by users. Use ExtensionInstallAllowlist instead if people should decide themselves.

Does the policy also work for Microsoft Edge?

Yes. Edge supports the same policy names and can install Chrome Web Store extensions with the Chrome Web Store update address.

More questions in the help centre

Turn website feedback into tasks your team can fix.