> 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/getting-started.md).

# Open Your Dashboard

This walkthrough takes you from "I just got the approval email" to knowing your way around, using the smallest set of features that gets your first event run. Everything else can wait.

## Get There

Your approval email has a direct link, and the URL looks like:

```
https://kc7cyber.com/tenant/[your-tenant-name]
```

You can also log in at [kc7cyber.com](https://kc7cyber.com) and open your dashboard from the site navigation. Bookmark it either way, since you'll come back every time you run an event.

## Learn the Layout

The screen has two zones, and one quirk worth knowing up front.

**The left sidebar** is your launcher. **Classes** lists your classrooms (plus **New class** to add one), and **Organization** holds the views that cut across everything: **All students**, **Leaderboard**, and **Settings & plan**. **Exit to KC7** takes you back to the main site, and there's a dark mode toggle at the bottom.

**The main area** is your dashboard's management page, with four tabs:

| Tab            | What it holds                                                                                     |
| -------------- | ------------------------------------------------------------------------------------------------- |
| **Overview**   | Quick actions, active games, top players, students needing attention, and your Resource Capacity. |
| **Classrooms** | The full classroom list, with game and student counts and an Add Classroom button.                |
| **Students**   | Everyone across all classrooms, searchable, with account type and registration date.              |
| **Settings**   | Your plan, organization-wide policies, and administrators.                                        |

The quirk: the sidebar's **All students** lands you on this management page's Overview tab rather than a separate screen, and **Settings & plan** is a shortcut to its Settings tab. If you ever feel lost, the tabs across the top of the main area are the reliable map.

At the top of the page, four stat tiles summarize the organization at a glance: active students, total games, game enrollments (a student in two games counts twice), and engagement rate.

## Find What's Already Set Up

When your first event was approved, KC7 created a classroom (named **My First Classroom** unless your request named it) with your first game inside, and made your account an administrator. Your dashboard already has everything it needs for one event.

## Test Your Game Link

Open your classroom from the sidebar and go to its **Games** tab. Your game's card shows its join code, and students join at `kc7cyber.com/go/[code]`, the same link that's in your approval email. Open it in a private or incognito window and confirm the game loads and a new participant can create an account. You're seeing exactly what your participants will see.

Also check the card's **Visible to students** toggle matches your plan: on if students should see the game the moment they join the classroom, off if you're saving the reveal for event day.

## Run Your Event, Then Look at Results

Day-of guidance lives in the [hosting guide](https://docs.kc7cyber.com/hosting-events/quick-start). Afterward, come back and look in two places: the classroom's **Home** tab for the quick read (average completion and who went idle), and its **Roster** tab for the full progress matrix. The complete tour of what the numbers mean is in [Track Performance](/dashboard/analytics.md).

## Success Check

You're done with this walkthrough when your game link works in an incognito window, your event has run, and you've seen your students' progress in the classroom.

## What You Can Ignore for Now

You don't need more games, more classrooms, co-managers, or policy settings to run your first event. Plenty of hosts run several events on a fraction of the dashboard. Pick features up when you actually need them.

## Common Questions

<details>

<summary>Do I need to do anything in the dashboard before my first event?</summary>

No. Your game is set up. Check the link works, share it, and come back for results afterward.

</details>

<details>

<summary>Where do I find my game link?</summary>

In your approval email, or on the game's card in your classroom's Games tab, as `kc7cyber.com/go/[code]`.

</details>

<details>

<summary>Can I add participants before the event?</summary>

You can, from the classroom's Roster tab, but you don't have to. Participants create accounts the first time they open the game link.

</details>

<details>

<summary>What if I delete something by accident?</summary>

Deletion is permanent, which is why it lives in each classroom's Danger Zone. Email <code class="expression">space.vars.support\_email</code> if you need help, and prefer unlinking games over deleting them when in doubt.

</details>

<details>

<summary>Do I need a new classroom for each event?</summary>

No. One classroom holds many games. Create new classrooms when you want to keep distinct groups apart, like "Fall 2026" and "Spring 2027."

</details>

<details>

<summary>How do I give someone else access?</summary>

For one classroom, add them as a Classroom Manager in that classroom's settings. For the whole dashboard, add them as an administrator in your Settings tab. See [managing users](/dashboard/managing-users.md).

</details>

## Next Steps

* [Add another game or a career path](/dashboard/managing-games.md)
* [Organize classrooms](/dashboard/classrooms.md)
* [Invite students and co-managers](/dashboard/managing-users.md)
* [Track performance](/dashboard/analytics.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/getting-started.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.