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.
Overview Statistics
The top of the dashboard displays six key metrics that summarize your organization's training activity at a glance:
| Metric | Description |
|---|---|
| Total Users | All users in your organization |
| Active Users (30d) | Users who completed at least 1 challenge in the last 30 days |
| Challenges Completed | Total challenges solved across all users |
| Total XP | Combined XP earned by all users |
| Avg Score | Average score per challenge attempt (0-100%) |
| Training Completion Rate | Percentage of assigned training that has been completed |
Leaderboard
The leaderboard ranks your top performers by XP earned. Each entry shows the user's name, total XP, challenges completed, and scenarios completed. Use the leaderboard to drive gamification and quickly identify your most engaged learners.
Topic Statistics
The topic statistics section provides a per-topic breakdown showing how many users have attempted each topic, their average score, and the completion rate. This helps you identify topics where your team needs additional training or where knowledge gaps exist.
Filtering & Time Ranges
The dashboard supports filtering to help you drill down into specific segments of your organization:
| Filter | Description |
|---|---|
| Team | View metrics for a specific team within your organization |
| Date Range | Select a custom time period (last 7 days, 30 days, 90 days, or custom range) |
| Content Area | Filter by OWASP category — Web, API, Mobile, or Client-Side |
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, the dashboard's export function produces a CSV of user-level completion data tied to specific assignments and timestamps. Export at the end of each quarter and store the file alongside your other compliance artifacts. The export captures the state at the time it was generated, which matters for auditors who 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.