> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/client-app-deployment/browser-extension-requirements-for-it-admins.md).

# Browser extension requirements for IT admins

This article describes the browser versions, browser settings, browser policies, extension IDs, and network access that the Cerby browser extension needs.

If you manage browser policies, Mobile Device Management (MDM) platforms, or network settings for your organization, make sure your organization's devices meet the requirements in this article before you roll out the Cerby browser extension. The extension works best on devices that meet all of them.

***

## Supported browsers

The Cerby browser extension supports the following web browsers:

* **Google Chrome and Microsoft Edge:** The current version and the two previous major versions
* **Mozilla Firefox:** The current version, the two previous major versions, and the current Extended Support Release (ESR)
* **Safari:** Version 17 or later, which requires macOS 12 Monterey or later

Opera isn't supported. The Cerby browser extension isn't fully supported in incognito or private browsing windows.

***

## Browser settings

The following are the browser settings the Cerby browser extension needs on every device:

* **Chrome and Edge:** The extension's site access is set to **On all sites**.
* **Safari:** Each user turns on the extension and allows it on all websites.

***

## Browser policies for Chrome and Edge

If your organization manages Chrome or Edge with enterprise policies, allow the Cerby browser extension with its own policy entries. Your settings for other extensions stay the same.

* **`ExtensionInstallAllowlist`:** Add the extension's ID. The allowlist lets the extension install even when your policies block all other extensions. For the IDs, see [Extension IDs](#extension-ids).
* **`ExtensionSettings`:** Add an entry for the extension's ID next to the default (`*`) entry. In this entry, set `installation_mode`, `blocked_permissions`, and `runtime_blocked_hosts` explicitly. A field you leave out can take its value from the default entry and keep the extension blocked.

The following are the `ExtensionSettings` entries for Chrome and Edge:

**Google Chrome**

```json
"clccplmaaeihbagbefjinmclielobnkb": {
  "installation_mode": "allowed",
  "blocked_permissions": [],
  "runtime_blocked_hosts": []
}
```

**Microsoft Edge**

```json
"bbaiiaogfdgpbapebajffliefkfipoif": {
  "installation_mode": "allowed",
  "blocked_permissions": [],
  "runtime_blocked_hosts": []
}
```

If your organization force-installs the extension, set `installation_mode` to `force_installed` and add `update_url`. For the configuration, read the article [Install the Cerby browser extension via an MDM platform](https://help.cerby.com/setup-and-admin/client-app-deployment/install-the-cerby-browser-extension-via-an-mdm-service-and-a-configuration-file.md).

***

## Extension IDs

Use the following extension IDs to allow the Cerby browser extension in your browser policies or MDM platform:

| **Browser**     | **Extension ID**                         |
| --------------- | ---------------------------------------- |
| Google Chrome   | `clccplmaaeihbagbefjinmclielobnkb`       |
| Microsoft Edge  | `bbaiiaogfdgpbapebajffliefkfipoif`       |
| Mozilla Firefox | `{f961ea35-985c-412d-9b06-aafd75752587}` |

**Table 1.** Cerby browser extension IDs

To install the extension on your organization's devices, read the article [Install the Cerby browser extension via an MDM platform](https://help.cerby.com/setup-and-admin/client-app-deployment/install-the-cerby-browser-extension-via-an-mdm-service-and-a-configuration-file.md).

***

## Network access

The Cerby browser extension needs, at minimum, HTTPS access to `*.cerby.com`. If your organization uses a firewall or proxy, add this domain to its allowlist.

The extension doesn't need a minimum connection speed.

***

## Before contacting Cerby Support

If a user reports that the extension loads slowly or doesn't work, collect the following information before you contact Cerby Support at <support@cerby.com>:

* The user's web browser and its version
* For Chrome or Edge, a copy of the `chrome://policy` or `edge://policy` page from the user's device


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.cerby.com/setup-and-admin/client-app-deployment/browser-extension-requirements-for-it-admins.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
