Coverage you can see
A quiet failure is worse than none, because the dashboard still looks fine. Coverage is an input, so gaps surface as posture rather than as surprise.
FOR IT OPERATIONS
Roll it out, keep coverage healthy, and keep support clear.
Managed installation, device health, staged updates, and stable error codes make coverage visible across a fleet.
Context
The situation
Someone chose this. Now you have to deploy it to a fleet, keep it working, and answer the people who noticed a new process.
Managed installation, device health, staged updates, and stable error codes make coverage visible across a fleet. Coverage is a first-class posture input, so a silent failure moves the score rather than hiding.
On this page
What you get from this
Stable error codes
Every failure has a code you can search. Include it when you contact support.
Permissions, justified
The permission set for each platform is published item by item, so you are not asking anyone to trust a checkbox list.
Collection boundary
The boundary
We observe here
What you can tell colleagues, in one sentence they will believe: it records which app talked to which country, and how much; it does not record what was said, typed, visited, or sent.
We never collect here
Communication content, URLs, paths, query strings, DNS names beyond the registrable domain, headers, cookies, tokens, files, screenshots, form data, keystrokes, usernames, email addresses, hardware serial numbers, or precise location.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Self-install
Pro
Small group
Team
Shared workspace, no dedicated fleet path
Enterprise
The fit for fleet rollout