IT Device Audit is a fleet-audit workflow packaged as an OpenTechnologyApp project template. Import it in one click and you get three queues, real automations, five triage playbooks, and two dashboards — pre-loaded with example data so you can see the shape of it before you touch a real device.
The template directory is going open source on GitHub — watch the org for the repo.
Three queues, one system
| Queue | What lives there |
|---|---|
| Device Inventory | One item per device — serial, hostname, platform, assigned user, OS version, last contact, health status, and how fresh the underlying data is |
| Audit Findings | One item per finding — device health, stale device, OS compliance, inventory mismatch, identity mismatch, network health, or a flagged manual review — with severity and state (open, investigating, blocked, resolved, suppressed) |
| Audit Runs | One item per daily, weekly, or ad-hoc audit pass — cadence, scope, run status, and how many devices were checked and findings opened or resolved |
Automations that do real work
Three automations ship enabled, not as advisory comments: when a device's Health Status changes to Critical, the item goes to urgent priority. When a finding's state changes to Resolved, the item closes. When an audit run's status changes to Failed, it goes urgent too — so a broken audit run gets someone's attention instead of quietly not happening.
Two scheduled flows create the audit work itself: one drops a new Daily Device Audit item into Audit Runs every day, one drops a new Weekly Device Audit item every Monday. Both are checklist items for a person to work through — neither sends an email.
Playbooks: the triage workflow, encoded
Five playbooks auto-attach to matching item types, each a short list of required steps rather than a wall of prose:
- Daily Device Audit — confirm source freshness (or mark the run blocked), review Critical/Warning/Unknown devices, create or update findings, record counts and close out the run
- Weekly Device Audit — device health and stale-device review, inventory and identity reconciliation, network-health review, aging/blocked findings, then record the outcome
- Critical Device Health — validate the evidence, assign an owner and an immediate containment step, record resolution or escalation
- Stale Device Review — confirm last contact and assigned user, decide active/offline/returned/retired, update the finding
- Inventory and Identity Review — verify serial, hostname, and assigned user, identify the authoritative record, record the correction or an accepted exception
Two dashboards
Device Health shows device status at a glance, health broken down by platform, open findings by severity, and a live list of every Critical, Warning, or Unknown device. Audit Operations shows audit work status, runs by cadence, findings by type, and open audit follow-ups.
What ships versus what you connect yourself
The template itself has no built-in device-manager connector — it's queues, fields, automations, playbooks, and dashboards, loaded with clearly-labeled example devices and findings so the shape is obvious on import. Pointing it at a real fleet is a separate, deliberate step.
Two starter scripts in the template directory are a starting point for that step, not a plug-and-play integration: jumpcloud-sync.js pulls devices from the JumpCloud API on a schedule, and device-post-ingest.js is a webhook endpoint for device-side health, network, and compliance telemetry. Both are meant to be read and adapted — map their output onto whichever of the queue's fields you actually want populated — not pasted in as a finished product. The MDM layer is deliberately swappable: nothing about the queues, playbooks, or dashboards is JumpCloud-specific.
Get it
Import IT Device Audit from the template picker in OpenTechnologyApp — it's built in. The standalone template files (fields + scripts) are heading to the OpenTechnology14 GitHub org as an open-source directory.