If you run Google Workspace, this is a ten-minute job.
Capsulla is built for exactly one setup: a company on Google Workspace whose people work in Chrome. That narrowness is the point — there is no agent to package, no proxy to stand up, and nothing for anyone on staff to install or notice.
{ "orgKey": "cap_org-code" }Three fields in the console you already use
In Google Admin you find the extension by its ID, force-install it for the organizational units or groups you choose, and paste one line of policy carrying your organization key. The browsers pick it up on their own schedule — no ticket, no desk visit, no end-user instructions.
- A force-installed extension cannot be removed or disabled by the person using the browser.
- Roll it out to one group first. Nothing has to block on the first day.
The whole configuration is one line
Managed policy is how Chrome hands an extension its settings, and Capsulla uses it for exactly one value: the organization key that connects a browser to your console. Everything else — rules, retention, who gets alerts — is decided in the console and reaches the browser within minutes.
Managed browsers, and nothing else
If Chrome is enrolled in your Google Admin, you have everything Capsulla needs. No device management, no network changes, no certificates to distribute, and no dependency on where anybody is working from.
What it does not coverWorth knowing
- Browsers that are not enrolled cannot be reached by policy — Capsulla covers the managed ones, which is the same boundary every Chrome policy has.
- The organization key identifies your company to the console. Regenerating it disconnects every browser until the new key is deployed, which is also how you cut off a tenant you no longer control.
The rest of it
Stop the next leak before it leaves the browser.
Try it free for 14 days, no card needed. Start with one team and see what Capsulla catches in the first week.