Loading fleet status…
- In sync
- 0
- Laptops
- 0
- Need attention
- 0
Needs attention
Details
Devices by source
- Snipe-IT
- None
- JumpCloud
- None
- Kandji
- None
- SentinelOne
- None
- Google Workspace
- None
Tracked in Snipe-IT, per source
Breakdown
Recent drift
Ownership risk
Freshness
Top issues
Last seen, 13 weeks
|
No sync has loaded yet Devices appear here after the first sync finishes. |
Devices
Agent versions
Platforms
Gaps against Snipe-IT and the MDMs
All SentinelOne devices
Devices per version, newest first
Adoption, newest first
Devices, oldest version first
Coverage by division
Open a division for its departments and devices, least compliant first.
Likely machine swaps
Someone holds a newer laptop while an older one has gone quiet: candidates for recovery. Laptops in project use are not counted.
People with 2 or more laptops
Deployed laptops per person in Snipe-IT, excluding project use.
Shared and automation accounts, flagged by hand. They are left out of onboarding baselines and can be kept out of waste. Flag an account from a person's profile.
Flagged accounts
Every active tag, exclusion, snooze and note across the fleet. Bring an excluded device back into the counts, end a snooze early, or clean up tags here. Removals take effect on the next data refresh.
Active annotations
Get started with cost tracking
No seat data yet. Vendors wire themselves from the built-in connectors on the
daily run; external feeds can instead POST to /api/webhooks/seats (the directory
to /api/webhooks/directory). Your only step: set each tool's pricing in Settings.
Seats, waste and costs appear here after the first feed.
How the numbers work
Tools
Open a tool for its dormant and orphaned seats.
| Total |
|---|
Access review (CSV) Compliance export: who holds what, with directory status. The download is recorded in the audit trail.
| Total |
|---|
Monthly spend
Monthly waste
Savings by quarter
Tool pricing
Vendors wire themselves from the built-in connectors: pricing is the only manual step.
Only Administration can change the prices and the cost settings; you can read them here.
Cost settings
Only Administration can change these settings; you can read them here.
Sync schedule
Between 60 and 1440.
A source whose device count drops past the guard is treated as a failed fetch and its last good data is reused. Arm this when the drop is real (a decommission, a source migration): the next run accepts it, once.
The hourly CronJob tick reads these controls; changes are audited.
System status
Okta directory feed
Divisions and departments come from this feed, not from Sync now. It runs nightly at 04:30 New York, or right here. A run that would grow or shrink the roster past the guard is refused unless the allowance is armed; the allowance is used up by the next run.
Sync duration by source, last 30 runs
Data hygiene
Active sessions
Feed deliveries
Connector runs and webhooks, newest first.
Audit log
Every human change and security-relevant event: annotation edits, user and group changes, vendor edits, exports, break-glass sign-ins, token activity. Seat changes from the vendor feeds are logged too, as "system". Sync results and snapshots are not logged here; they are their own record.