Skip to main content
A patch deployment tracker that surfaces patch compliance, breaks it down by OS / department / criticality, and lists devices needing attention with owner contacts for outreach. Time: ~20 minutes · Difficulty: Beginner

What you’ll build

  • Overall patch compliance gauge
  • Three metric cards: Current / Pending / Overdue device counts
  • Pie chart of patch status by OS
  • A drillable table of devices with overdue patches, including owner email
  • A filter dropdown for department, OS, and patch criticality
  • One-click owner-notification (optional)

Prerequisites

  • Dimension access (Analyst or Super Admin)
  • A patch management or MDM Data Feed connected:
    • Microsoft Intune for Windows / iOS / Android / macOS
    • Jamf for macOS / iOS
    • SCCM / Configuration Manager for Windows
    • Automox / Tanium / Kandji for cross-platform
    • Or the ThreatAware Devices table if patch level is exposed there

Step 1 — Start a blank canvas

Builder Mode → New App → Blank Canvas Light.

Step 2 — Headline gauge

Step 3 — Status metric cards

Step 4 — Status distribution

Step 5 — Drilldown table

Step 6 — Filters

Step 7 — Owner outreach (optional)

To email device owners directly:
  1. Create an Email Action named Patch Outreach with input device_name and the recipient set to the device owner (tenant user). See Actions.
  2. In Studio:
Email Action recipients are tenant-user-only. If your device owners are end-employees not registered as tenant users, replace the Email Action with a Webhook Action that hits your transactional email API (SendGrid, Postmark, AWS SES).

Step 8 — Polish + branding

Step 9 — Auto-refresh + PDF

Step 10 — Publish

Click the Published chip. The app:
  • Auto-creates a Shortcut (e.g. https://<tenant>/app/patch-tracker)
  • Becomes accessible to everyone with workspace access
  • Is ready to Pin to Sidebar for ops teams

What you’ve built

Customisation ideas

  • Patch criticality SLA — “Add an SLA column showing days remaining before each overdue device breaches our patch SLA (Critical: 7 days, High: 14, Medium: 30)”
  • Reboot wave campaigns — “Add a ‘Reboot wave’ tag and a button to mark a device as in-wave; show wave-level progress”
  • Auto-create tickets — “For devices >30 days overdue, auto-create a Jira ticket every Monday via our Jira Webhook Action”
  • Per-region escalation — “Add a ‘Critical patches > 21 days’ Slack notification per region channel via Webhook Actions”

See also

Patch management (pre-built)

A pre-built patch tracking app you can import and customise

Actions

Email / Webhook Actions for owner notifications

Connect Your Data

Wire up Intune / Jamf / SCCM as a Data Feed

Studio AI Composer

Reference for the Composer interaction patterns