> 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/managing-games.md). # Manage Games Games are KC7 modules running inside a classroom. Each game you add is your own copy of a catalog module, with its own access code and link, its own enrollment, and its own progress tracking. This page is for administrators and classroom managers. ## Add a Game 1. Open the classroom and go to its **Games** tab (or use the **Add a game** quick action on the Home tab). Click **+ Add game**. 2. Browse the module catalog. You can search by name or filter by level (Beginner, Intermediate, Advanced). Each module card shows a difficulty rating, its question count, and a short description of the scenario. First-time groups often start with **How to play KC7** or another beginner module; the full catalog is described in the [game module guide](https://docs.kc7cyber.com/hosting-events/event-resources/game-modules). 3. Pick a module and set up your copy: * **Game name.** Prefilled with the module name. Rename it freely, especially if you'll run the same module for more than one cohort ("Spring 2027 - Valdoria" beats "Game 1"). * **Access code & link.** Every game gets its own join code, and students can join at `kc7cyber.com/go/[code]`. Use the regenerate button if you want a different code. * **Make visible to all students.** When this is on, students see the game in their classroom and are registered automatically. Leave it off to stage the game quietly and reveal it later. * **Schedule (optional).** Set open and close times if the game should only run during a window, like a competition or a class period. 4. Click **Add game**, and the game appears in the classroom's Games tab. ## Add a Career Path Next to the **Add game** button is a dropdown with two more options. The first, **Add a career path**, adds every game in a curated path to your class in order, and the games arrive hidden until you make them visible. Paths like Security Analyst I through IV each bundle six or seven games in a deliberate sequence, which makes them the fastest way to set up a multi-week program: add the path once, then reveal one game at a time as the group progresses. ## Link an Existing Game The second dropdown option, **Link an existing game**, attaches a game you already manage that isn't in any classroom yet. This pairs with **Unlink from class** (in each game's menu), which detaches a game from a classroom without deleting it. ## Join and Access Students can reach a game through two doors: * **The classroom join link** (the **Join link** button in the classroom header) adds them to the classroom roster. From there, every game that's visible to students registers them automatically. * **The game's own link**, `kc7cyber.com/go/[code]`, using the code shown on the game's card. This is the Go Link that event hosts share on game day, and it takes students straight into that specific game. The **Visible to students** toggle on each game card is the master switch for what the classroom sees. A hidden game shows a "Hidden from students" badge and stays invisible to students no matter how they joined, which is exactly what you want while preparing content or holding a competition module until the starting gun. The enrollment count on each card (like 9/9 or 1/9) shows how many classroom students are registered in that game. If a code has traveled further than you intended, open the game's menu and choose **Edit name & code** to change it, which retires the old link. ## Manage a Game Each game card carries its controls: **Analyze** opens that game's performance view, **Play** lets you open the game yourself, and the visibility toggle sits alongside. The **⋮** menu holds the rest: * **Game settings.** The game's configuration. * **Edit name & code.** Rename the game or change its join code. * **Assign all students.** Registers everyone currently in the classroom into this game, useful when a game was hidden while students joined. * **Unlink from class.** Detaches the game from this classroom without deleting it. Relink it later, or into another classroom, with Link an existing game. * **Delete game.** Permanent, so unlink instead if there's any chance you'll want the game or its data again. ### Inside the Management View **Game settings** opens the game session management view, a separate surface shared with event hosts. Its session settings hold the deeper controls: the session name and its join code (labeled **Password** there), an optional schedule, **team mode** with a choice of team scoring methods, the game's description and images, and a **Timing** section. Its **Manage Questions** page edits the game's content directly: rename sections, add questions, change point values, and drag questions into a new order. The same view carries the live event controls and scoreboard exports covered in [Track Performance](/dashboard/analytics.md#question-level-analytics). ## Run a Multi-Week Program Stack several games (or add a career path) in one classroom, keep everything hidden, and flip one game visible each week. Students get registered automatically at each reveal, the classroom's progress matrix shows the whole journey in one view, and nobody sees week four's content during week one. Scheduling can do the timing for you: set open and close windows at setup and the platform enforces them. ## Common Issues **Students can't see a game.** It's almost always the visibility toggle. Flip **Visible to students** on and classroom members are registered automatically. **A student joined the classroom but isn't in the game.** Make the game visible, or use **Assign all students** from the game's menu if you're keeping it selectively hidden. **The join code leaked.** Use **Edit name & code** to change it. The old code stops working. **A scheduled game won't open.** Check its open and close times; outside the window, students can't play. **Wrong module picked.** A game can't change modules. Delete it if nobody has played, or unlink it and add a fresh game if you want to keep the record. ## Next Steps * [Organize classrooms](/dashboard/classrooms.md) * [Add students and managers](/dashboard/managing-users.md) * [Track game analytics](/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/managing-games.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.