Home / Docs

Getting started

Install for yourself in a minute, or roll out to your whole organisation.

Install

  1. Open the extension page in the Chrome Web Store.
  2. Select Add to Chrome and confirm.
  3. Pin the extension so you can see its status.

The core protection is on at once. On the welcome page that opens, choose Accept and create my free account: the account form opens in the same tab, you type the 6-digit code we e-mail you, and the browser is connected. From there you can start the free 14-day Pro trial. Already have an account? Use I already have an account on the same page. Prefer not to connect? Choose Keep everything on this device. To leave an account later: Settings → Sign out of this browser (the browser keeps its protection and its seat is freed).

Check it works

Open the extension's popup: it shows that protection is on and, once connected, the account or organisation it reports to.

Connect to an organisation’s console

  1. In the console, go to Fleet → Enrollment and create a token for the group of devices.
  2. In the extension, open Settings, select Use an enrolment token from my organization, enter the console address and the token, and select Connect.
  3. The device appears under Devices. Events start flowing within seconds; protection never waits for the console.

Deploy to an organisation

Force-install the extension with your management tool:

  • Group Policy / Intune (Windows): for Chrome, add the extension ID (bkplloeajblikjdffgdepnhicgajfhcd) to ExtensionInstallForcelist. For Microsoft Edge, add the ID followed by the Chrome Web Store update address (bkplloeajblikjdffgdepnhicgajfhcd;https://clients2.google.com/service/update2/crx): on its own, an ID makes Edge look in Edge Add-ons instead.
  • Google Admin console: Apps & extensions → Users & browsers → add from the Chrome Web Store and set to force install.
Zero-touch enrollmentDeliver the console address and an enrollment token through managed policy (managedMode, consoleUrl, enrollmentToken, optionally group and supportContact): browsers connect by themselves and users cannot change the connection. Contact us for the policy template.

Troubleshooting

  • In the extension: Settings → Advanced → Troubleshooting → Export diagnostics downloads one file with the version, the settings and a summary of recent events — no tokens, evidence text or full addresses.
  • In the console (administrators): Settings → Troubleshooting → Open diagnostics runs the self-tests; Download bundle saves them as a file.
  • Not connected? Settings → Advanced → Test connection checks the console address; Sync now sends what is waiting and refreshes the plan and the policy.
  • Still stuck? Contact us and attach both files.