Skip to content

Deploy the extension (IT guide)

This guide is for IT admins rolling the InPolicy extension out to employees. Steps 1 to 4 use the Google Admin console for Chrome. For Microsoft Edge, see Microsoft Edge with Intune. There is nothing to install on InPolicy’s side.

When you’re done:

  • The extension appears in every employee’s Chrome, pinned to the toolbar, without them doing anything.
  • Employees can’t remove or disable it.
  • You decide which sites it stays off on, and who doesn’t get it at all.

Employees still sign in to the extension once, with their work account. See Install the extension.

  • A Google Admin role that can manage Chrome apps and extensions. A super admin can do everything here. A custom role works if it includes Chrome management privileges, but moving users between organizational units (OUs) also needs user-management rights, which usually means a super admin.
  • The InPolicy extension ID: ikifbjcchpaiggmbalpgfkahomkekbjh
  • Chrome or Microsoft Edge. Edge uses the same extension, installed from the Chrome Web Store, on devices your organization manages.
  1. In the Admin console, go to Devices → Chrome → Apps & extensions → Users & browsers.
  2. In the left panel, select the OU you want to deploy to.
  3. Click the yellow + button, then Add Chrome app or extension by ID.
  4. Paste ikifbjcchpaiggmbalpgfkahomkekbjh, keep From the Chrome Web Store selected, and click Save.
  5. On the InPolicy row, set Installation policy to Force install + pin to browser toolbar.
  6. Click Save (top right).

Chrome picks the change up within a few minutes. It arrives in a browser that’s already open, so no restart is needed.

Force install already stops employees from removing InPolicy or switching it off in chrome://extensions. The InPolicy popup also has its own Pause switch. To remove that too:

  1. Open the InPolicy row’s settings panel (click the row).

  2. Find Policy for extensions and paste:

    { "allowUserPause": { "Value": false } }
  3. Click Save.

With this set, the popup shows Always on · Managed by your organization instead of the Pause switch, and InPolicy keeps checking even if the employee had paused it before. To turn InPolicy off on particular sites, use the next step. Leave the setting out (or set true) to let employees pause as before.

Use Chrome’s blocked hosts setting when InPolicy shouldn’t run on a site at all, such as an internal tool or a chat app your policies don’t cover.

  1. Open the InPolicy row’s settings panel.

  2. Under Permissions and URL access, add one entry per line to Runtime blocked hosts, for example:

    *://chat.google.com
    *://*.internal.example.com
  3. Click Save. The panel closes without saving if you don’t.

On those sites Chrome stops InPolicy from reading the page, so nothing is checked or underlined. This is enforced by Chrome and employees can’t override it.

Things to know:

  • Whole sites only. Entries match a host, not a path. *://*.example.com covers every subdomain.
  • Google Chat is one entry. *://chat.google.com turns InPolicy off in standalone Google Chat and in the Chat panel inside Gmail. Gmail emails are still checked.
  • Up to 100 entries.

You can also block sites in the InPolicy dashboard, without Google Admin. See Block sites and exclude people from checking.

To keep InPolicy off for certain people (for example legal or the executive team), put them in their own OU and don’t force-install there:

  1. A super admin creates a child OU (for example InPolicy excluded) and moves those users into it under Directory → Users.
  2. In Apps & extensions, select that OU and set InPolicy’s Installation policy to Block (or Allow install if they may choose to install it).
  3. Click Save. Chrome removes a force-installed extension from those users automatically.

Child OUs inherit the parent’s settings until you change them, so check that the child OU shows the override rather than Inherited.

To keep the extension installed but stop it checking someone, use Exclude from checking in the InPolicy dashboard instead. See Block sites and exclude people from checking.

Edge uses the same extension and the same settings as Chrome. You set them with Edge’s policies instead of Google Admin.

In the Intune admin center, create a configuration profile for your devices using the Settings catalog, and set these Microsoft Edge policies:

  1. Force-install. In Control which extensions are installed silently (ExtensionInstallForcelist), add:

    ikifbjcchpaiggmbalpgfkahomkekbjh;https://clients2.google.com/service/update2/crx
  2. Turn it off on specific sites. In Configure extension management settings (ExtensionSettings), add:

    { "ikifbjcchpaiggmbalpgfkahomkekbjh": { "runtime_blocked_hosts": ["*://chat.google.com"] } }

    The rules are the same as in step 3.

  3. Lock it on. allowUserPause is a setting for InPolicy itself, not an Edge policy, so it isn’t in the Settings catalog:

    • macOS: deploy a custom configuration profile with the preference domain com.microsoft.Edge.extensions.ikifbjcchpaiggmbalpgfkahomkekbjh and the key allowUserPause set to false.
    • Windows: set the DWORD allowUserPause to 0 under HKLM\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\ikifbjcchpaiggmbalpgfkahomkekbjh\policy, for example with an Intune PowerShell script.

To leave some people out, assign the profile only to the groups that should get InPolicy.

To check it, use edge://policy and edge://extensions in place of the chrome:// pages below.

On a test employee’s machine:

  1. Go to chrome://policy and click Reload policies.
  2. Find ExtensionInstallForcelist. It should contain ikifbjcchpaiggmbalpgfkahomkekbjh.
  3. Expand ExtensionSettings. Blocked hosts appear under runtime_blocked_hosts for the InPolicy ID.
  4. Go to chrome://extensions. InPolicy shows Installed by your administrator, with no Remove button.
  5. Open the InPolicy popup. If you set allowUserPause: false, it shows Managed by your organization.

If a setting is missing from chrome://policy, it hasn’t reached the browser. The usual causes are a change that wasn’t saved, or a setting made on a different OU from the one the user is in.