IT dashboards
Security posture and system health, live
Device compliance lives in your MDM, identity risk in Okta, uptime in monitoring and the backlog in your service desk. RapidDashboard joins them in a private data store and answers plain-English questions with a full IT dashboard.
Live examples
One question, one full dashboard
Pick a question. RapidDashboard answers with KPIs, charts, the records behind them and an AI summary of what to do next. Hover any chart for values or open its table view.
Show device compliance by operating system, which devices are out of compliance and who owns them.
Endpoint compliance
Endpoint coverage
97.2%
14 unmanaged 486 of 500 assets
Device compliance
91%
-4 pts vs 95% policy
Non-compliant
44
+9 vs last month
Patch compliance
87%
+3 pts critical within 14 days
- Compliant
- Non-compliant
| Compliant | Non-compliant | |
|---|---|---|
| Windows | 246 | 22 |
| macOS | 112 | 12 |
| iOS | 58 | 6 |
| Android | 26 | 4 |
| Device | Owner | Department | OS | Issue | Status |
|---|---|---|---|---|---|
| HLG-LT-0412 | A. Brennan | Finance | Windows 11 | BitLocker off | Remediate today |
| HLG-LT-0388 | S. Kowalski | Finance | Windows 11 | BitLocker off | Remediate today |
| HLG-LT-0451 | D. Ibarra | Finance | Windows 10 | BitLocker off | Remediate today |
| HLG-MB-0137 | N. Fischer | Engineering | macOS 13 | Below OS minimum | Update pushed |
| HLG-LT-0299 | K. Adeyemi | Claims | Windows 11 | EDR 9 days stale | Ticket open |
| HLG-MB-0142 | L. Moreau | Engineering | macOS 13 | Below OS minimum | Scheduled |
What changed and what to do
- Critical: Seven Windows laptops have BitLocker disabled, and three belong to Finance users who handle policyholder payment data.
- Warning: Four Engineering MacBooks run macOS 13, below the policy minimum. All four deferred the last two update prompts.
- Good: Critical patch compliance reached 87%, up 3 points, after the new Intune update ring went live.
AI summary
Device compliance is 91% across 486 managed endpoints, 4 points below the 95% policy, with 44 devices out of compliance. The most serious gap is seven Windows laptops without encryption, three of them in Finance. Fourteen assets in inventory are still unmanaged. Recommend an Intune encryption push today with a 48-hour follow-up check, and enrollment of the 14 unmanaged assets this week.
Ask next
- Which 14 assets are unmanaged?
- Compliance trend by department
- Show devices missing critical patches
What is our MFA enrollment rate, and are there privileged or stale accounts without MFA?
Identity & access risk
MFA enrollment
94%
+5 pts vs 12 weeks ago
Privileged, no MFA
3
of 22 admins critical risk
Stale accounts
8
+2 90+ days inactive
Departed, still active
3
+1 vs HR roster
94%
423 of 450 accounts · target 100%
- MFA enrolled
- Phishing-resistant (FIDO2)
- Policy 100%
| MFA enrolled | Phishing-resistant (FIDO2) | |
|---|---|---|
| W29 | 89% | 12% |
| W30 | 89% | 14% |
| W31 | 90% | 15% |
| W32 | 90% | 17% |
| W33 | 91% | 19% |
| W34 | 91% | 22% |
| W35 | 92% | 24% |
| W36 | 92% | 27% |
| W37 | 93% | 29% |
| W38 | 93% | 32% |
| W39 | 94% | 35% |
| W40 | 94% | 38% |
| Account | Type | Department | Last sign-in | MFA | Status |
|---|---|---|---|---|---|
| j.mercer-adm | Super admin | IT | Today | None | Admin, no MFA |
| svc-backup-adm | Service admin | IT | 2 days ago | None | Admin, no MFA |
| p.hale-adm | App admin | Claims | 6 days ago | None | Admin, no MFA |
| r.alvarez | User | Sales | 104 days ago | Push | Departed in June |
| m.osei | User | Finance | 97 days ago | SMS | Departed in July |
| ext.dlee | Contractor | Operations | 121 days ago | None | Stale 90+ days |
What changed and what to do
- Critical: Three of 22 admin accounts have no MFA, including a super admin that signed in today. These are the highest-value targets in the tenant.
- Warning: Eight accounts have been inactive for 90+ days, and three belong to employees HR lists as departed.
- Good: Phishing-resistant FIDO2 keys now cover 38% of accounts, up from 12% in July.
AI summary
MFA enrollment is 94%, with 423 of 450 accounts enrolled, and phishing-resistant coverage climbed to 38%. Three privileged accounts still have no MFA, and three departed employees keep active Okta accounts. Recommend enforcing MFA on all admin accounts before end of day and a terminated-employee access review against the HR roster this week.
Ask next
- Which apps do stale accounts reach?
- MFA enrollment by department
- Show failed sign-ins by location
Show service uptime and incidents for the last 30 days. Which services used the most downtime, and how is MTTR trending?
Service uptime & incidents
Services within SLA
5 / 7
99.9% target monthly availability
Incidents
7
P1 1 · P2 3 · P3 3
MTTR
42 min
+18 min vs 24 min target
MTTD
13 min
+4 min mean time to detect
99.9% SLA budget, 30 days: 43 min
| Item | Minutes to detect | Minutes to resolve |
|---|---|---|
| P1 Payment API | 38 min | 94 min |
| P2 Auth service | 6 min | 48 min |
| P2 VPN gateway | 9 min | 41 min |
| P2 Email relay | 4 min | 36 min |
| P3 File share | 12 min | 28 min |
| P3 Intranet | 7 min | 25 min |
| P3 Print server | 15 min | 22 min |
- MTTR
- Target 24 min
| MTTR | |
|---|---|
| Oct | 31 min |
| Nov | 29 min |
| Dec | 30 min |
| Jan | 27 min |
| Feb | 26 min |
| Mar | 28 min |
| Apr | 25 min |
| May | 27 min |
| Jun | 30 min |
| Jul | 33 min |
| Aug | 37 min |
| Sep | 42 min |
What changed and what to do
- Critical: The P1 on the payment API ran 94 minutes, more than twice the 43-minute monthly budget. An expired TLS certificate caused it, and certificate expiry had no monitor.
- Warning: MTTR has risen four months in a row to 42 minutes. Two of seven incidents had no runbook for the affected service.
- Info: Detection took 38 minutes on the P1 and 9 minutes on average for the rest, so monitoring coverage is the main lever.
AI summary
Five of seven business-critical services met the 99.9% availability target over 30 days. The payment API used 94 minutes of downtime in a single P1 caused by an expired certificate, and the auth service went slightly over budget at 48 minutes. MTTR has climbed to 42 minutes against a 24-minute target. Recommend certificate-expiry monitors on every public endpoint and runbooks for the payment and auth services this sprint.
Ask next
- Show the payment API incident timeline
- Which certificates expire in 60 days?
- MTTR by on-call engineer
Show help desk ticket aging. How many tickets are past SLA and which departments have the oldest open tickets?
Service desk backlog
Open tickets
74
+21 in 5 weeks
Past SLA
18
24% of open backlog
Oldest open
31 days
P2 Finance VPN access
SLA attainment
86%
-5 pts resolved this week
- P111%
- P21318%
- P33953%
- P42128%
| Segment | Value | Share |
|---|---|---|
| P1 | 1 | 1% |
| P2 | 13 | 18% |
| P3 | 39 | 53% |
| P4 | 21 | 28% |
What changed and what to do
- Critical: A P2 VPN access ticket for a remote Finance employee is 31 days old with no update in 14 days.
- Warning: Sales and Marketing hold 11 of the 18 past-SLA tickets, or 61%. Most are laptop and CRM access requests from Q3 hires.
- Info: Intake has outpaced resolution for five straight weeks, adding 21 tickets to the backlog.
AI summary
The open backlog grew to 74 tickets, 18 of them past SLA, because intake has run ahead of resolution for five weeks. The 31-day Finance VPN ticket carries both productivity and compliance risk. Sales and Marketing account for most past-SLA work, which points to onboarding gaps for recent hires. Recommend a triage session on the 18 past-SLA tickets this week and a standard new-hire access bundle.
Ask next
- Past-SLA tickets by assignee
- What are the top ticket categories?
- New-hire tickets in first 30 days
How well are we using our SaaS licenses, and how much could we reclaim before renewals?
SaaS spend & license utilization
SaaS spend
$1.21M
+12% vs last year
License utilization
81%
-3 pts active ÷ purchased
Unused seats
225
+31 no use in 60 days
Reclaimable
$127K
10.5% of annual SaaS spend
| Step | Change |
|---|---|
| Last year | $1.08M |
| New tools | +$0.11M |
| Price increases | +$0.06M |
| Seat growth | +$0.04M |
| Reclaimed | -$0.08M |
| Now | $1.21M |
- Microsoft 365 E3 · renews Mar431 / 450 · 96%
- Jira Software · renews Jan140 / 150 · 93%
- Salesforce Sales Cloud · renews Nov 3084 / 120 · 70%
- Zoom Workplace · renews Feb262 / 400 · 66%
- Adobe Creative Cloud · renews Dec38 / 60 · 63%
What changed and what to do
- Warning: Salesforce renews on November 30 with 36 seats unused for 60+ days, worth $71K a year. That is the largest single reclaim.
- Info: New tools added $110K this year, mostly department purchases outside the IT request process.
- Good: Microsoft 365 and Jira run above 90% utilization, so those renewals can go ahead at current counts.
AI summary
Annual SaaS spend reached $1.21M, up 12%, while license utilization across the top five apps slipped to 81%. 225 seats have seen no use in 60 days, worth $127K a year. Salesforce is the priority because it renews on November 30 with $71K of idle seats. Recommend a seat true-down on Salesforce before the renewal and reclaiming idle Zoom and Adobe seats this month.
Ask next
- Which users hold idle Salesforce seats?
- SaaS renewals in the next 90 days
- Shadow IT purchases by department
Sample data for a fictional company. Your dashboards run on your own connected systems.
Sound familiar?
Where the numbers live today
Compliance is an export
An audit request means pulling Intune, matching it to the HR roster and chasing the devices nobody can place.
MFA coverage from memory
Enrollment is "mostly done" until someone runs the report, and privileged accounts get the same estimate as everyone else.
Incident timelines take a morning
Reconstructing what went down, for how long and why means stitching monitoring alerts to service desk notes.
The backlog has no context
Aging tickets sit in a queue, and the ones blocking business-critical work surface when a manager asks in chat.
Metrics glossary
The metrics behind these dashboards
How each number is defined, so everyone reads it the same way.
- Uptime (availability)
-
The share of a period a service is available to users. A 99.9% target allows about 43 minutes of downtime in 30 days.
Formula(Total minutes − Downtime minutes) ÷ Total minutes
- MTTR (mean time to resolve)
-
The average time from the start of an incident to full restoration of service.
FormulaTotal resolution time ÷ Number of incidents
- Ticket SLA attainment
-
The share of service desk tickets responded to or resolved within the committed time for their priority.
FormulaTickets within SLA ÷ Tickets with an SLA
- Patch compliance
-
The share of managed devices with required security patches installed within the policy window, often 14 or 30 days for critical updates.
FormulaDevices fully patched in window ÷ Managed devices
- Endpoint coverage
-
The share of known devices that are enrolled in management and security tooling such as MDM and EDR.
FormulaManaged devices ÷ Devices in asset inventory
- License utilization
-
How many purchased software seats are actively used over a recent window, commonly 30 to 90 days.
FormulaActive seats ÷ Purchased seats
Connections
How your systems connect
Supported APIs and exports sync into a private RapidDashboard store you approve. Dashboards read from that store, so source systems keep their normal load.
Microsoft Intune / Jamf Pro
PullsDevice inventory, compliance state, OS version, encryption, patch status
Microsoft Graph and Jamf Pro APIs on a scheduled sync into your private store.
Okta / Entra ID
PullsMFA enrollment, factor types, admin roles, last sign-in, deprovisioning
Okta and Graph APIs, matched to the HR roster for joiner and leaver checks.
Datadog / Sentry
PullsUptime, monitors, incident timelines, error rates
REST APIs and webhooks, so incidents line up with service desk records.
Jira Service Management
PullsTickets, priorities, SLA timers, queues, requester department
Atlassian REST API on the refresh cadence your team sets.
What you can build
Dashboards and reports teams build next
Security posture
- Device compliance and encryption
- MFA and privileged access gaps
- Leaver accounts still active
Operations
- Uptime against SLA by service
- MTTR and MTTD trends
- Incident root cause log
Service desk
- Backlog aging by department
- SLA attainment by queue
- New-hire access requests
Automated reports
- Weekly security posture summary
- Monthly IT operations review
- Audit-ready compliance exports
Built for the most sensitive data in your environment
Device, identity and incident data maps your attack surface. RapidDashboard keeps it in a private data store on infrastructure you control, with role-based access and an architecture that fits HIPAA-aware and CMMC-aligned environments. AI features are optional and run on enterprise endpoints whose terms prohibit training on your data.
FAQ
IT & Technology dashboards: common questions
What should an IT dashboard show?
Most IT leaders track endpoint and patch compliance, MFA and privileged access coverage, service uptime with MTTR, help desk backlog against SLA, and license utilization. RapidDashboard builds each view from a plain-English question against data synced from your existing tools.
How is MTTR calculated?
Mean time to resolve is the total time from incident start to full restoration, divided by the number of incidents in the period. Showing it beside mean time to detect separates slow detection from slow repair.
How much downtime does a 99.9% uptime SLA allow?
A 99.9% target allows about 43 minutes of downtime in a 30-day month, and 99.99% allows about 4 minutes. RapidDashboard tracks downtime against that budget for each service so you see which one is spending it.
Can RapidDashboard connect to Intune, Jamf and Okta?
Yes. Microsoft Intune connects through Microsoft Graph, Jamf Pro and Okta through their official APIs, and Datadog and Jira Service Management through REST APIs. Data syncs on a schedule into a private store, so audits draw on one consistent source.
Is our security data used to train AI models?
No. Device and identity data stays in a private store you approve, and AI features run on enterprise endpoints whose terms prohibit training on customer data. AI is optional, and the dashboards work without it.
Keep exploring
Related example dashboards
See dashboards like these on your own data
Fifteen minutes with an AIBMM™ Certified Coach: bring one question, leave with the dashboard it would build on your systems.
Schedule a demo