> 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/overview.md). # Your KC7 Dashboard Your dashboard (sometimes called your tenant) is your organization's account on KC7. It holds every classroom, game, participant, and report tied to your organization, and it was created automatically when your first event was approved. Other organizations can't see anything inside it. This section is for dashboard owners and admins. To run a single event you barely need it. The [hosting guide](https://docs.kc7cyber.com/hosting-events/quick-start) covers that. ## Event vs Dashboard An **event** is a single game session you run for participants. Your **dashboard** is the account that lets you create and manage events. You requested an event, and KC7 created a dashboard so you could run it and any others later. Think in **event** terms when planning a session, inviting participants, or running the day. Think in **dashboard** terms when adding games, creating classrooms, managing co-hosts, or reviewing analytics across events. Many hosts run one event and never touch most dashboard features. ## How Your Dashboard Is Structured ```mermaid graph TD Dashboard[Dashboard] --> Classroom[Classrooms] Classroom --> Game[Games] Student[Students] -->|enroll in| Game Dashboard --> Org[Organization views] Org --> AllStudents[All students] Org --> Leaderboard[Leaderboard] Org --> Settings[Settings and plan] ``` * **Dashboard.** The top level, and your organization's whole account. Everything below belongs to it. * **Classroom.** A container for grouping games and students (a course, cohort, workshop group, or term). The sidebar lists your classrooms under **Classes**. * **Game.** An instance of a module (like "A Scandal in Valdoria") that lives inside a classroom. Each game has its own roster and progress tracking. * **Enrollment.** One student joined to one game. A student can be enrolled in several games, so your enrollment count can be higher than your student count. * **Seat.** One student in your dashboard. Seats are what your plan's capacity counts, and the **Resource Capacity** card on your overview shows how many you've used. Alongside your classrooms, the sidebar's **Organization** section gives you views that cut across everything at once: **All students**, the organization-wide **Leaderboard**, and **Settings & plan**. Your dashboard came with one classroom and one game already set up. Add more when you need them. {% embed url="" %} ## What Your Dashboard Gives You * Classrooms and games up to your plan's capacity. * Role-based access, so you can delegate without handing out full admin. * Live stats across your whole organization: active students, games, enrollments, and engagement at a glance. * Leaderboards and progress tracking for every classroom and game. * A **Needs attention** view that flags students who've gone idle, so you know who to check on. ## Roles Three roles, each with a different scope. Details are in the [user roles reference](/dashboard/managing-users.md#roles-and-permissions). * **Administrator.** Full access across the dashboard. You become one automatically when your dashboard is created, and you can add others in Settings. * **Classroom Manager.** Admin access limited to assigned classrooms, granted in each classroom's own settings. * **Student.** Joins classrooms, plays games, and sees their own progress. ## Plan Capacity Every dashboard includes the full module library and all platform features. Plans differ in capacity, measured in seats (students) and classrooms. Two places show you where you stand: * The **Resource Capacity** card at the bottom of your dashboard overview shows seats used against your plan's total, and your classroom count. * **Settings & plan** in the sidebar opens your Settings tab, where the Plan section shows your current plan, its capacity (set by your dashboard type), and which features are included, like advanced analytics, custom branding, and priority support. An **Upgrade Plan** button lives on that screen, and a few plan controls there are marked admin-only because KC7 staff manage them. For plan questions, upgrades, or fee waivers for organizations aligned with KC7's philanthropic mission, email space.vars.support\_email with your dashboard name and a description of your program. ## Access Your Dashboard Your dashboard URL looks like `https://kc7cyber.com/tenant/[your-tenant-name]`. The link is in your approval email. You can also log in at kc7cyber.com and pick your dashboard from the navigation. Bookmark it. ## Lifecycle * **Creation.** Automatic when your first event is approved. * **Initial tier.** Every new dashboard starts on Free. * **Data retention.** Stored indefinitely. No auto-expiration. * **Closure.** Email space.vars.support\_email to delete a dashboard. Support confirms first because deletion can't be reversed. ## Common Questions
Can one organization have multiple dashboards? Most organizations use one dashboard with multiple classrooms. For separate legal entities, multiple dashboards are possible. Email space.vars.support\_email to discuss.
Do I need to use dashboard features to run events? No. Once your event is created you have a participant link and a host dashboard. Classrooms, roles, analytics, and the rest are optional.
How do I transfer dashboard ownership? Add the new owner as an administrator in Settings, and once they've accepted, they can remove your access. For formal documentation, email space.vars.support\_email.
## Next Steps
Open your dashboardFirst-time walkthrough./pages/MDgMJtytdSYfY0bg3ZIJ
Manage gamesCreate games and get participants in./pages/vMNJXpH4LWjV8Xoc8VLC
Track performanceAnalytics across classrooms and games./pages/kYw6fHWC2iLTwg5fuces
--- # 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/overview.md?ask=&goal= ``` `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.