Browser coverage and troubleshooting
This page covers what the Browser extension page tells you about your computers, what the alerts mean, how to rotate or revoke the browser token, and what to check when something is wrong. For the…
Written By Christopher Scaminaci
Last updated 4 days ago
This page covers what the Browser extension page tells you about your computers, what the alerts mean, how to rotate or revoke the browser token, and what to check when something is wrong. For the setup, see Installing the browser extension.
At a glance
- What it does: shows which browsers are covered and how to fix common problems.
- Plan: every plan. Checking what people send needs Pro.
- Who: an Administrator. A Reviewer can read the page.
- Where: AI Governance → Staff computers → Browser extension.
Coverage
The Coverage panel of the Browser extension page lists the computers whose extension has reported in:
- how many computers report, by browser and by extension version;
- how many of your staff those computers cover, counted "by profile email (not verified)";
- when each computer last reported.
A computer reports a short heartbeat, so the last-seen time tells you the extension is alive. A computer that stops reporting has lost the extension, has the browser closed, or has no network.
Staff computers → Coverage shows the same installs person by person, beside the endpoint agent and your security products. There an extension reads Reporting when it was seen within 3 days (it reports every 6 hours while the browser is open, and a computer that is shut over a weekend is quiet for about 60) and Not reporting when it has been quiet longer. See Source health and coverage.
Who the coverage counts, and what you can trust
The browser token is one token for your whole organization, and it is stored on every computer you deliver it to. So anyone who can read it on a computer can send reports to StackJack as if they were any other computer. For that reason, every identity the extension reports is a claim that nothing has checked: the email of the browser profile, the email or organization id the AI site shows, and the id of the computer.
- Coverage and the attribution of a visit to a person use the reported profile email. StackJack matches it to a person who is already on your roster. It never adds a person because an email appeared in a report, so a report cannot grow your roster or your staff count.
- A report with an email that matches nobody is kept without a person.
- StackJack labels these emails "not verified" wherever it shows them.
- Use the extension to find AI use and to enforce your rules on managed computers. Do not use it as proof of who typed something.
Alerts
Both alerts open the Browser extension page.
Rotating and revoking the browser token
The Token panel lists your tokens by prefix, with their status and times. It never shows a whole token.
- Rotate (type
ROTATEto confirm) makes a new token and marks the old one Retiring. The old token keeps working for seven days, so computers that have not yet received the new settings keep working. Make the settings again and deliver them again within those seven days. A second rotation inside the seven days revokes the older retiring token at once. - Revoke now (type
REVOKEto confirm) stops a token at once. Computers that use it are refused and raise the "token refused" alert.
After a token is revoked or retired, a computer that still uses it is refused. The extension treats this as StackJack's answer that it may not be used, not as an outage, so it blocks nothing and checks nothing until it has a valid token.
What "unreachable" means
The extension treats StackJack as unreachable only when it has a real failure: the network is down, a request times out, StackJack answers with a server error, or StackJack says its policy is too old to trust. Then:
- with Block AI sites when StackJack cannot be reached off, the extension keeps your last rules, and lets sends through without a check;
- with it on, the extension blocks the AI sites it knows, after the policy has been out of date for longer than the allowed time, until it reads the policy again.
These answers are not outages, and none of them blocks anything: StackJack says the organization is not governed, StackJack refuses the token, or StackJack has the browser extension switched off. When the extension gets one of these, it clears its rules and stops checking.
A send that the extension could not check within about one and a half seconds is let through, and a note is kept that the send was not checked. The note holds no text.
If something is wrong
Turning it off
Turn off Use the StackJack browser extension on the Browser extension page. Within about five minutes the extensions clear their rules. Remove the policy with your RMM or Intune to remove the extension. Your stored data stays as it is.
Was this helpful?
More in Connect your AI
Data sourcesSend telemetry from coding toolsSettings for staff machinesDelivering the settings through your RMMStill need help? Ask the team