> For the complete documentation index, see [llms.txt](https://docs.kc7cyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kc7cyber.com/dashboard/analytics.md).

# Track Performance

Your dashboard reads out performance at four altitudes: the whole organization, one classroom, one game, and one question. Each level answers a different question, and this page walks down the ladder.

This page is for administrators and classroom managers.

## The Organization at a Glance

Your dashboard's **Overview** tab is the widest view. Four stat tiles run across the top:

* **Active students**, everyone who has ever joined.
* **Total games** across all classrooms.
* **Game enrollments**, one per student per game, so a student in two games counts twice.
* **Engagement rate**, how much of your population is actually playing.

Below them, **Active games** lists what's running, **Top players** shows your organization-wide standings (the **Full leaderboard** link, or **Leaderboard** in the sidebar, opens the complete ranked list with points for every account, including yours, marked YOU), and **Needs attention** flags students who've gone idle and for how long. The **Resource Capacity** card at the bottom tracks seats and classrooms against your plan.

## Classroom Health

Each classroom's **Home** tab gives the quick read: student count, games assigned, average completion, and its own needs-attention list. The **Leaderboard** tab ranks that classroom's students by points.

The deep view is the **Roster** tab's progress matrix: every student crossed with every game, each cell showing that student's completion and colored by status (complete, on track, started, just began, not started, or stuck), with arrows marking movement since last week. The matrix acts in place: click any cell to jump into that student's per-challenge drilldown, or to assign a game they haven't started, without leaving the page.

## One Game in Depth

Click **Analyze** on any game card to open its **Game Summary**. The top card holds the game's vitals: status and end date, difficulty, estimated time, and its question, point, and section counts, plus the invite link with a copy button. Below, **Class progress** shows average completion with done, in progress, and not started counts you can filter by, and a sortable per-student table with each person's status and exact progress (like 42/44). This is the page to project nothing from but read often: who finished, who stalled, and who never started.

## Question-Level Analytics

From the Game Summary, **Game Settings** steps into the game session management view, a separate surface with its own sidebar. It's the same environment event hosts use on game day, holding the live controls (pause and extend) described in the [event day guide](https://docs.kc7cyber.com/hosting-events/running-your-event/event-day). Tabs run across the top of every page there: **Questions**, **Game Ranking** (the live scoreboard), **Teams**, and **Query Data (ADX)**, which opens the game's dataset in Azure Data Explorer after a Microsoft login. For performance work, open **Manage Game** and choose **Analytics**:

* **User drop-off analysis** charts how many students attempted versus solved each question, in order. A widening gap marks where people got stumped.
* **Drop-off rate by question** counts students who attempted but never solved each question, pointing straight at the hardest challenges.
* **Question statistics** tables every question by section with attempts, solves, and average attempts. An average of 12 attempts is a question worth pre-teaching next time.

The same menu holds the **Answer Key** (for organizers only; nudge students toward the built-in hints first) and the **Organizer Guide**, a game-day hub with the share link as a QR code, participant count, and intro videos.

## Export Data

The **Game Ranking** page carries a **Manager Actions** row with the export buttons: **CSV**, **Excel**, **PDF**, and **Print**, covering the game's full standings with points and last-solve times. A **Show Emails** option adds addresses when you need them for records or follow-up. Question-level statistics live on screen in the Analytics view; for data needs beyond these, email <code class="expression">space.vars.support\_email</code>.

## Teams

Games with team mode use the **Teams** page in the same view, where teams are created and ranked by total team score using the scoring method set in the game's session settings (like divide and conquer). Team standings sit alongside the individual scoreboard, so both reads are always available during an event.

## Reading the Numbers

| Situation               | What to look at                                                                              |
| ----------------------- | -------------------------------------------------------------------------------------------- |
| Post-event review       | The Game Summary for completion and stalls, then question analytics for what stumped people. |
| Ongoing program         | The progress matrix weekly, plus the needs-attention lists for who's drifting.               |
| Planning the next event | High-average-attempt questions to pre-teach, and drop-off points to budget time around.      |

## Who Sees What

Administrators see analytics across the whole dashboard. Classroom managers see their assigned classrooms. Students see only their own progress, never each other's answers. Data is stored indefinitely, so last term's numbers stay readable.

## Troubleshooting

**Numbers look stale.** Progress updates as students play; refresh the page, and give it a minute during a live event.

**A student is missing from a game's progress.** They aren't registered in that game. Make the game visible to students, or use **Assign all students** from the game's menu.

**A student is missing everywhere.** They never finished creating an account. Have them open the game link again and complete signup.

## Related

* [Manage games](/dashboard/managing-games.md)
* [Manage users](/dashboard/managing-users.md)
* [Organize classrooms](/dashboard/classrooms.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kc7cyber.com/dashboard/analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.