IT Mass Deployment (Extension Only)
Audience: IT and endpoint administrators deploying Pyze to all client machines with nothing installed outside the browser. The extension is force-installed from the Chrome Web Store or Edge Add-ons by policy. There is no native host, so no files, registry keys, or system rights are needed on the endpoint.
Without the native host, events carry a random id generated once per browser install and Pyze reports activity per installation rather than per signed-in user. If you need users identified across machines, use the store guide instead, which adds the native host.
For the permissions, data collected, and privileges your security team will ask about, see the IT & Security Review.
Step 1: Force-Install the Extension
Pyze gives you the store extension ID (or IDs) for your organization’s build. Use whichever policy your endpoint management already applies to the browser.
Add one entry per browser:
| Browser | Installs from | Policy value |
|---|---|---|
| Chrome | Chrome Web Store | <chrome-store-id> |
| Edge | Edge Add-ons (when Pyze has an Edge listing) | <edge-addons-id> |
| Edge | Chrome Web Store (no Edge listing) | <chrome-store-id>;https://clients2.google.com/service/update2/crx |
Where to set it:
| Browser | Policy |
|---|---|
| Chrome | GPO: Google Chrome › Extensions › Configure the list of force-installed apps and extensions. Registry: HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist, value 1 |
| Edge | GPO: Microsoft Edge › Extensions › Control which extensions are installed silently. Registry: HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist, value 1 |
| Intune | Settings Catalog › Google Chrome or Microsoft Edge › Extensions › Configure the list of force-installed apps and extensions (Edge: Control which extensions are installed silently) |
| macOS | MDM profile key ExtensionInstallForcelist (array) in com.google.Chrome and com.microsoft.Edge |
If you manage extensions with the ExtensionSettings JSON policy, add the Pyze ID to the existing object:
{
"<extension-id>": {
"installation_mode": "force_installed",
"update_url": "https://clients2.google.com/service/update2/crx"
}
}
For an Edge Add-ons listing use https://edge.microsoft.com/extensionwebstorebase/v1/crx as the update_url.
Both policies are honoured on managed devices: domain-joined, MDM-enrolled, or in Chrome Browser Cloud Management.
Step 2: Verify on a Client
- Open
chrome://policy(Edge:edge://policy) and click Reload policies. The entry should be listed without error. - Open
chrome://extensions(Edge:edge://extensions). Pyze <Customer> should appear with the label Installed by your organization. Users cannot disable or remove it. - Open one of the approved sites. Events reach Pyze within a few minutes and the installation appears in the Pyze portal.
Updates and Removal
Updates. Pyze publishes to the store and browsers update automatically. Nothing to push. Pyze notifies you before any release that changes permissions or the approved domain list.
Removal. Delete the force-install entry. The browser uninstalls the extension on every managed device at the next policy refresh and deletes its local storage. To prevent reinstallation, add the ID to ExtensionInstallBlocklist. Nothing else remains on the endpoint.
Adding the Native Host Later
To move to per-user identification, ask your Pyze contact for the native host package and a build of the extension that declares the nativeMessaging permission, then follow the store guide in full. Pyze will tell you whether the extension ID changes for your organization.