Install the browser extension (Windows manual)

​

Setup at a glance (shortest path)

On the target PC, the user performs the following three steps. No scripts or registry edits are needed. For details, see Setup steps. Checks after saving (shortest)

1. Confirm that no warning appears on the settings screen
2. Click the reload button at the bottom right of the settings screen
3. Confirm that data appears in Integrations > Event Log in the admin console

​

Overview

This page describes how to install the extension from the store. You then set it up by entering values on the extension settings screen. You configure one PC at a time. This method suits testing on your own PC and installation on a small number of PCs. With this method, the extension isn’t force-installed. Users can disable or remove the extension. Removing it also deletes the values entered on the settings screen. If you want to prevent users from removing the extension, choose one of the following methods.

• To force-install on a single PC through the registry: Install the browser extension (Windows registry)
• To distribute in bulk with GPO: Install the browser extension (Windows GPO)
• To distribute in bulk with Intune: Install the browser extension (Windows Intune)

​

Prerequisites

• The common Windows prerequisites are met (see Browser extension deployment on Windows)
• Extensions can be installed from the store. If your organization’s policy restricts extension installation, check with your browser administrator
• Windows administrator rights aren’t required

​

Setup steps

​

Step 1: Get the values from the admin console

In the admin console, open Settings > Browser Extension > Extension policy. Note the values of ApiKey and OrganizationID.

​

Step 2: Install the extension from the store

Open the store page for your browser and add the extension. If you use both Chrome and Edge, install the extension and complete Step 3 in each browser. Values entered on the settings screen are saved per browser.

​

Step 3: Enter the values on the settings screen

1. Click the extension icon on the browser toolbar, then open the settings screen from the settings (⚙️) icon.
2. Enter the following values.

   Field	Value
   Organization ID	The OrganizationID noted in Step 1
   API Key	The ApiKey noted in Step 1
   Email address	The user’s work email address
   PC Name	A name that identifies the PC (for example, the computer name). Optional

3. Click Save. Setup is complete when “Settings saved!” appears.

Manual appears to the right of each saved field. To clear a value, click Reset to the right of the field. If you leave Email address empty, the extension uses the email address of the account signed in to the browser. However, it doesn’t use personal email addresses such as gmail.com. For details, see How the user’s email address is determined.

​

Verification

​

Check 1: Settings screen

Confirm that no warning appears on the settings screen. A warning may say that the API key or organization ID is incorrect. In that case, compare Organization ID and API Key with the values from Step 1.

​

Check 2: Reload button

Click the reload button at the bottom right of the settings screen. The reload button reloads the configuration values and sends unsent data in one action. If Reloaded! Sent N records. appears, data has been sent. If only Reloaded! appears, there is no data to send yet. Open some SaaS applications, then click it again.

​

Check 3: Event logs

Confirm that Chrome or Edge data appears in Integrations > Event Log in the admin console. For details, see Check data after rollout. If no data appears, review your configuration with Get Diag data for the browser extension.

​

FAQ

For common Windows questions, see Browser extension technical notes and FAQ for Windows.

​

Q. How do I uninstall the extension?

Open chrome://extensions (edge://extensions for Edge) and click Remove for the extension. The values entered on the settings screen are also deleted.

​

Q. What happens to values entered on the settings screen if I later distribute them by policy?

Values distributed by policy take precedence, and the corresponding fields on the settings screen become read-only. For details, see Precedence of configuration values.