Deploy Krisp CX Bridge across your organization

Who can use this feature?

Plan: Call Center AI
Managed from: Admin Portal
User type: Admin

Summary

Install Krisp CX Bridge from the Chrome Web Store or Microsoft Edge Add-ons store
Force-install across your organization with Microsoft 365, Google Admin Console, or Group Policy
Allow the local ports the extension uses to reach the Krisp desktop app
Review the browser permissions the extension requests.

This article covers how to install Krisp CX Bridge on individual devices or across your organization, and what your network and browsers need to allow. Before installing, make sure Krisp Bridge is enabled for your team in the Admin Portal. For details, see Krisp CX Bridge.

Install from the browser store

To install the extension on a single device, use the store link for your browser:

Google Chrome: Krisp CX Bridge on the Chrome Web Store
Microsoft Edge: Krisp CX Bridge on the Microsoft Edge Add-ons store

Deploy across your organization

To roll the extension out to all agents, use one of the deployment options below. The Krisp CX Bridge extension ID is apkneiablbgdpmflgkfhjnkijammlflo.

Microsoft Edge deployment

Option 1: Microsoft 365 Admin Center (cloud-based)

Access the Microsoft Edge management service in the Microsoft 365 Admin Center.
Select or create a configuration profile, then go to the Extensions tab.
Add the Krisp CX Bridge extension by ID: apkneiablbgdpmflgkfhjnkijammlflo.
Set the installation policy to Force install and save.

Option 2: Windows Group Policy (GPO)

Install the Microsoft Edge policy templates:

Visit the Microsoft Edge for Business download page, select your Edge version and platform, then download the policy files.
Unzip the file and copy msedge.admx, msedgeupdate.admx, msedgewebview2.admx, and the en-US folder from windows\admx to C:\Windows\PolicyDefinitions.

Configure Group Policy:

Open the Group Policy Editor (press Win + R, type gpedit.msc, then press Enter).
Go to Computer Configuration >>> Administrative Templates >>> Microsoft Edge >>> Extensions.
Double-click Control which extensions are installed silently (ExtensionInstallForcelist).
Set it to Enabled, click Show, and add: apkneiablbgdpmflgkfhjnkijammlflo;https://clients2.google.com/service/update2/crx
Apply and close.

Google Chrome deployment

Option 1: Google Admin Console

Go to Admin Console >>> Devices >>> Chrome >>> Apps & extensions >>> Users & browsers.
Select the target Organizational Unit (OU) or group.
Click Add >>> Add from Chrome Web Store, then select the Krisp CX Bridge extension.
Set the installation policy to Force install (or Force install + pin) and save.

Option 2: Windows Group Policy (GPO)

Install the Google Chrome policy templates:

Visit the Google Chrome Enterprise download page and download the Chrome ADMX/ADML templates.
Unzip the file and copy chrome.admx, google.admx, and the en-US folder from windows\admx to C:\Windows\PolicyDefinitions.

Configure Group Policy:

Open the Group Policy Editor (press Win + R, type gpedit.msc, then press Enter).
Go to Computer Configuration >>> Administrative Templates >>> Google Chrome >>> Extensions.
Double-click Configure the list of force-installed extensions (ExtensionInstallForcelist).
Set it to Enabled, click Show, and add: apkneiablbgdpmflgkfhjnkijammlflo;https://clients2.google.com/service/update2/crx
Apply and close.

For Remote mode, your IT team also deploys a browser policy that sets Remote mode. The mode in this policy must match the mode selected in the Admin Portal.

Network requirements

In Local mode, Krisp CX Bridge connects to the Krisp desktop app over a local port, trying a set of ports in order until it finds one that is open. For the extension to link to the app and capture call data, make sure your firewall or network configuration does not block these ports: 50166, 50173, 50180, 17329, 23847, 28673, 31753, 38421, 41587, and 46219.

In Remote mode, the extension in the virtual desktop must be able to reach Krisp cloud.

Required permissions

Krisp CX Bridge requests several browser permissions so it can monitor call states and communicate with the Krisp app:

Permission	Why it is needed
Scripting	Injects scripts into CCaaS platform web pages to access their APIs for real-time call state monitoring and integration.
Tabs	Detects and identifies active CCaaS tabs in the browser to establish integration and relay call status accurately.
Context menu	Adds a Send Debug Logs option to the extension's context menu for easier troubleshooting.
Storage	Securely stores extension configuration and preferences locally for a consistent experience.
System CPU	Evaluates the device environment to confirm compatibility and optimal Krisp performance.
Web navigation	Detects iframe navigation events when a CCaaS app runs inside an iframe, so the extension can inject integration scripts and keep call state monitoring accurate.
Host permissions	Injects scripts into CCaaS platform pages on matching domains so the extension can monitor call states and interact with these platforms.