Fleet and install keys

Govern → AI usage → Computers lists every machine enrolled into the current tenant.

Column	Meaning
Machine	Hostname the machine enrolled with
User	The person who enrolled it (the console user when enrolled elevated)
OS	darwin, linux or windows, and amd64 or arm64
Version	Collector (CLI) version
Last seen	Time of the last report of any kind
Responses	AI responses reported from the machine in the selected window
Status	Active, Quiet (enrolled but not reporting recently), or Revoked

A quiet machine is off, asleep, or no longer running the collector. From the outside these look identical, and Shield360 doesn’t guess between them.

Browser extensions

The Shield360 browser extension enrols as a device named browser:<id>, with its browser (Chrome or Edge) as the OS and extension/<version> as the version. Selecting one opens a Browser extension page in place of the computer page, because the extension sends none of the computer telemetry (AI cost, apps, websites, the week grid). It shows:

• Status: the enrolled user, browser, extension version, when it enrolled, and its last check-in. The extension checks in each time it reads its policy, every few minutes while the browser is open. No check-in for 24 hours shows as No check-in for N hours: the browser has been closed, or the extension was removed. A revoked enrolment shows as Revoked.
• Policy it receives: the browser channel’s action for sensitive data in prompts (with any per-kind exceptions), the AI tools rules, and whether people may send anyway after a warning. Edit them under Protect → Policies.
• Decisions it sent: the decisions it reported in the selected range, by outcome (warned, blocked, masked, sent anyway) and by site, with links to the Violations feed filtered to the browser extension and to Data protection.

The extension reports only when it acts on a prompt or an AI site, so a range with no decisions is normal. Check-ins are what show it is alive.

POST /api/visibility/extension   { "host": "browser:<id>", "timeLimit": { "start": "…", "end": "…" } }

The route needs the same permission as the computer page and reads only the caller’s current environment; a device enrolled elsewhere returns 404.

IDE extensions

The Shield360 VS Code extension enrols as an IDE. It uses the machine’s own hostname, its OS as the OS, and ide/<version> as the version. Like the browser extension, it sends no computer telemetry. It checks in each time it reads its policy, every 15 minutes while the editor is open, and reports only the AI extensions the policy warns about or blocks. See IDE extension.

Revoking a machine

Revoke a machine to reject its token immediately. It can’t report again until it’s re-enrolled with a valid install key. Data it already reported is kept.

GET    /api/collector/devices
DELETE /api/collector/devices/{id}

Install keys

Install keys are managed under Settings → Collection & deployment.

GET    /api/collector/install-keys
POST   /api/collector/install-keys
DELETE /api/collector/install-keys/{id}

A key is shown once, when it’s created, and can be given an expiry date. Shield360 stores only its SHA-256 hash. An expired or revoked key can’t enrol new machines. Revoking a key stops new enrolments with it. Machines already enrolled with it keep their own tokens and keep reporting.