Dashboard Overview
The admin dashboard provides a real-time overview of your organization's training progress — user activity, completion rates, XP rankings, and per-topic analytics.
Top metric tiles
The top of the dashboard displays four headline tiles that summarize your organization's training activity at a glance:
| Tile | Description |
|---|---|
| Completion Rate | Share of assigned training across the org that has been finished, expressed as a percentage. |
| Active Users | Users active in the last 30 days, shown as active / total. |
| Avg Score | Average score across completed challenges. The internal challenge scale runs to 160 (Phase 1 + Phase 2 combined), so values above 100 are expected here. |
| Avg Challenges Per User | Mean number of completed practice challenges per active learner. |
Assignment Summary, charts, and analytics panels
Below the headline tiles, the dashboard composes several specialised views in a fixed order. None of them is filterable; the dashboard is a single org-wide snapshot.
| Panel | What it shows |
|---|---|
| Assignment Summary | Three cards: Active, Overdue, and Avg Completion across all assignments. |
| Coverage Radar | Radar chart of training depth across the nine OWASP families (Web, API, Mobile, Client, LLM, Agentic AI, AI Dev Tools, Cloud-Native, CI/CD). The axis maxes out at the internal challenge cap of 160; the visual shape makes under-served areas obvious. |
| Engagement Ring | Ring gauge of overall training completion across the org. |
| Activity Trend | Stacked-bar chart of challenges and scenarios completed each day for the last 30 days. |
| Top Strengths / Focus Areas | Two side-by-side panels listing the top and bottom five topics by average score (only topics with at least three attempts count). Use Focus Areas to spot where to target the next assignment. |
| Team Performance | Per-team completion rate, average XP, challenges, and scenarios — useful once you have several teams. |
Leaderboard
The leaderboard ranks your top performers by XP earned. Each row shows the user's name, total XP, challenges completed, and scenarios completed; clicking a row opens that user's detail page. If the org has switched Show leaderboard off in Organization Settings, the panel renders with a small Hidden badge to remind admins that learners cannot currently see it.
Dashboard at a Glance
Here is what the admin dashboard looks like with live data:
Reading the dashboard signals
A dashboard is only as useful as the questions you bring to it. The headline numbers — total users, active users, completion rate — are designed to be reassuring at a glance, but they answer the question "is anything obviously broken" rather than "is the program working." For the second question, you have to look at the metrics that sit one layer beneath the summary and read them in context.
Why completion rate alone is misleading
An eighty-five percent completion rate looks good on a status slide, but it tells you nothing about what people learned. Two organizations with the same completion rate can have wildly different security postures depending on whether engineers engaged with the material or clicked through to mark it done. The per-topic average score is a more honest signal — a topic where the team averages forty-five percent accuracy after completion is a topic the team has not actually internalized, regardless of how many people marked it complete.
Pay close attention to the topics with the lowest average score, not the lowest completion rate. Those are the topics where your team's gap between thinking they know the material and actually knowing it is widest, and they are usually the topics where a real incident is most likely to originate.
Trends, disengagement, and audit exports
The week-over-week trend matters more than any single weekly number. A team that completes thirty challenges per week for six weeks straight is engaged. A team that completes ninety challenges in week one and zero in weeks two through six has gone through onboarding and then disengaged, and the same total completion rate hides that fact. When you spot a drop, the first place to look is the active-user count by team — disengagement usually starts with one or two specific teams, not across the board.
For audit evidence, look beyond the dashboard itself. The dashboard's only export today is the Leaderboard CSV; the user-level and assignment-level CSV exports live on the Users page and the Audit Log page respectively, and the per-assignment Compliance PDF lives on Reports. Export at the end of each quarter and store the file alongside your other compliance artifacts. Each export captures the state at the time it was generated, which is what auditors want to see — evidence as it existed during the audit period rather than as it exists today. For more on how to set up the assignments that produce this evidence, see Assignments.