(Internal) Allowlisting Chrome extension permissions (Microsoft 365)

🔍 Articles in This Section

Please use the following list to see additional internal articles regarding Gem Extension:

• (Internal) Gem extension: Overview
• (Internal) Allowlisting Chrome extension permissions (Microsoft 365) (📍you are here)
• (Internal) Gem extension sourcing site overview matrix

Some companies block all Chrome extensions by default. In these situations, we need to coordinate with a customer’s IT team to get Gem’s Chrome extension whitelisted with the right permissions. This will allow users to use the Gem Chrome extension.

Google’s official document details how IT teams can set extension policies and override defaults via Microsoft’s Group Policy Editor: https://support.google.com/chrome/a/answer/7532015?hl=en&ref_topic=9023098&sjid=14382407900571010880-NC

Within Microsoft’s Group Policy Editor, the IT team should navigate to Administrative Templates > Google > Google Chrome > Extensions. From there, they should open the Extension management settings.

Within the JSON policy editor, we need to add a policy for the Gem Chrome extension.

For reference, the ID of the Gem Chrome extension is bnbpceglddpnehbopmdjegpfinikcaoh.

An example policy may look something like this:

{

"bnbpceglddpnehbopmdjegpfinikcaoh": {

"runtime_blocked_hosts": ["*://*"],

"runtime_allowed_hosts": [

"*://*.[gem.com](http://gem.com/)",

"*://*.[linkedin.com](http://linkedin.com/)"

]

}

}

This example policy would prevent the Gem Chrome extension from interacting with all sites by default. It only allows the Gem Chrome extension to interact with sites explicitly listed, in this case Gem and LinkedIn. If you need advice on how to format a particular site in the policy, reach out to the Gem engineering team.

Once the policy is satisfactory, the IT team can save and deploy the policy to users by following Google’s official documentation: https://support.google.com/chrome/a/answer/7532015?hl=en&ref_topic=9023098&sjid=14382407900571010880-NC