Use Onyx in Chrome from any page
Use the Onyx extension to ask questions from anywhere. You can also replace your new-tab page with a custom Onyx page:
In the future, the Onyx Chrome Extension will allow you to ask questions about the page you are currently on and optionally index the recent pages into the Onyx knowledge base. You’ll be able to ask questions about recently visited pages via both the extension and the Onyx web app.
If you are using Onyx Cloud, you can simply install the extension from the Chrome Web Store.
The following steps are for users self-hosting Onyx.
chrome://extensions/
in your Chrome browser.
onyx-chrome-extension
).The Onyx Chrome Extension will now be able to connect to your self-hosted Onyx instance and can be used from any page in Chrome!
This guide provides instructions for installing, managing, and updating Chrome extensions in both enterprise and self-hosted settings.
Use these guidelines if you need to install and manage the Onyx Chrome Extension for a large group of users using Google Admin.
Don’t forget to save your changes after configuring the extension.
Instead of loading the extension manually, you can package your extension and publish it as private or unlisted on the Chrome Web Store, making it available for force-installs or distribution to managed Chrome instances.
Below are strategies to keep the Onyx Chrome Extension up to date.
If you have force-installed the extension through the Admin console, Google Chrome will handle automated updates. Updates typically occur when Chrome launches and then every five hours.
If you ever need to pin a specific Onyx Chrome Extension version (for compatibility reasons), you can set “Version pinning” for force-installed extensions within your Admin console.
Avoid pinning for extended periods, because pinned extensions do not receive security updates.
manifest.json
file (e.g., from “1.0” to “1.1”).If you manage a large organization, here are options to oversee which extensions users can install and how they’re updated. Many of these guidelines align with enterprise best practices from Google’s documentation on Chrome extension management.
Several policy-driven strategies can be enforced on managed devices:
Below is a brief overview of how to enforce these via Google Admin console or Windows Group Policy (GPO).
Force-installing an extension ensures users have the extension silently added and cannot remove it:
Force-installed extensions will automatically update unless you pin them to a specific version.
You can refine extension management by blocking or allowing certain permissions (for example, USB access, cookie access, etc.).
Access Settings
In the Admin console, go to your organizational unit at Devices → Chrome → Apps & extensions → Users & browsers → Additional settings (gear icon).
Set Permissions
Under Permissions and URLs, choose which permissions to block or allow.
Override Global Settings
You can also override global permission settings on a per-extension basis in this section.
In many enterprise scenarios, you may want to block extensions from modifying or reading data on specific domains (for instance, internal corporate portals). This is done via runtime_blocked_hosts:
Access Settings
In the Admin console, go to Devices → Chrome → Apps & extensions → Users & browsers → Additional settings (gear icon).
Add Blocked Hosts
Under “Runtime blocked hosts,” add patterns such as: *://*.sensitive-domain.com
Add Allowed Hosts (Optional)
Under “Runtime allowed hosts,” include host patterns you want to allow if they fall under a larger blocked domain.
This effectively prevents most extension-level script injections, web requests, or cookie access on specified sites.
If you’re not using the Admin console, you can still manage Onyx (and other) Chrome extensions via Windows Group Policy:
Install Policy Templates
Install the Chrome ADM/ADMX policy templates.
Access Group Policy Editor
Open gpedit.msc → Computer Configuration → Administrative Templates → Google → Google Chrome → Extensions.
Configure Policies
Configure: - Configure extension installation blocklist (ExtensionInstallBlocklist) - Configure extension installation allowlist (ExtensionInstallAllowlist) - Configure the list of force-installed apps and extensions (ExtensionInstallForcelist) - Extensions Management Settings (ExtensionSettings)
Specify Details
Use JSON or registry entries to specify details (e.g., blocked_permissions, runtime_blocked_hosts, etc.).
For details on each policy, refer to Google’s Chrome Enterprise policy list.
If you want to avoid the Chrome Web Store:
Build & Pack the Extension
In Chrome, go to chrome://extensions, Enable Developer Mode, then click “Pack Extension.” This creates a CRX file (and a private key PEM). Keep your PEM safe.
Host the Files
Host the CRX & an Update Manifest XML on your server or intranet.
Configure Client Settings
Use either Google Admin console or GPO settings to point clients to your CRX update URL so Chrome will install/update automatically.
For more detailed information, refer to: