> 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/manage-your-tenant/managing-games.md).
# Manage games
Games are KC7 modules running inside a classroom. Each game is an independent clone of a core module with its own join link, roster, analytics, and settings.
This page is for tenant managers and classroom managers.
## Before you start
* You need Tenant Manager or Classroom Manager access for the classroom.
* You need a classroom to put the game in. To create one, see [organize classrooms](/manage-your-tenant/classrooms.md).
* Each game counts as one session against your tier quota.
## What a game gives you
| Property | Notes |
| -------------------- | --------------------------------------------------------------------------------------------------- |
| Unique join link | Sends participants straight to this game. Works without classroom membership unless you require it. |
| Independent roster | The same person can be enrolled in multiple games and tracked separately in each. |
| Separate analytics | Performance and completion stay isolated per game. |
| Independent settings | Start/end times, team mode, auto-assign, and difficulty, per game. |
## Create a game
1. In the tenant dashboard, open the classroom you want the game in.
2. Click the **View modules** tab.
3. Click **Create game**.
4. Enter a name (for example, "February 2024 - Valdoria") and pick a core module from the dropdown.
5. Click **Create**.
The new game appears in the classroom's module list. From there you can copy the join link, open settings, view analytics, or manage students.
## Get participants in
Three ways to enroll people, each suited to a different scale.
{% tabs %}
{% tab title="Direct link" %}
Copy the game's join link and send it through email, your LMS, chat, or a QR code on a handout. New users create an account, returning users get straight in.
Best for one-off events or when you want manual control. Gets tedious across many games or frequent cohorts.
{% endtab %}
{% tab title="Classroom join link" %}
Share the classroom's join link and password instead. Participants who use it become classroom members. Any game with auto-assign on enrolls them automatically.
Best for ongoing programs. Watch your auto-assign settings so participants don't see content before you're ready to release it.
{% endtab %}
{% tab title="Manual assignment" %}
Open the game's **Students** tab, search by username, and add participants individually or in batches. They get enrolled in that game only.
Best for small groups or selective access. Doesn't scale to hundreds of participants but gives you a clean record of who was added when.
{% endtab %}
{% endtabs %}
## Lifecycle
* **Active.** Watch the live scoreboard, monitor participation, track completion, and export results. You can pause and resume a running game.
* **Ended.** After the end time, submissions close but results stay accessible and participants can review their work. Join links keep working unless you change the password.
* **Retired.** Delete the game when you're done with it. Participant data stays in any exports you've taken.
## Pick a multi-game pattern
How you organize games depends on what you're running.
{% tabs %}
{% tab title="Same module, different dates" %}
Create a fresh game each time you run the same module. Each instance has its own roster, dates, and analytics, so March participants and April participants stay separate even though the content is identical.
Name games with the date so they're easy to find later: "March 2024 - Valdoria," "April 2024 - Valdoria."
{% hint style="info" %}
Participants who complete a game can't replay it in another instance to improve their score. If you have repeat players across months, rotate modules.
{% endhint %}
{% endtab %}
{% tab title="Different modules, same classroom" %}
Stack modules in one classroom to build a learning path. Start with "A Scandal in Valdoria" as an intro, follow with an intermediate module, finish with an advanced capstone.
Create all the games up front and keep auto-assign off until you're ready to release each one. Name them in sequence: "Week 1 - Beginner - Valdoria," "Week 4 - Intermediate - Network Analysis."
Classroom analytics show each participant's progress across the whole program in one view.
{% endtab %}
{% tab title="Multiple classrooms" %}
For larger programs, split games across classrooms by organizational unit, skill level, time period, or program type. More setup and permission management, but better structure at scale.
{% endtab %}
{% endtabs %}
Name games with the date or cohort, the module, and any context you'll need later. "Spring 2024 Intro - Valdoria" beats "Game 1." Create games in advance for semester schedules and multi-week programs, and control access with the auto-assign toggle or staged link sharing.
## Settings reference
Open a game from its classroom to manage its details, timing, and challenges.
### Basics
| Setting | Notes |
| -------------------------- | ------------------------------------------------------------ |
| Name | The game's display name, visible to participants. |
| Description and objectives | Shown to participants before and during play. |
| Difficulty | 1 to 5. Sets the recommended player level. |
| Required level | Minimum player level to start (used mainly by core modules). |
| Requirements | Free-text prerequisites, like "Complete Module X first." |
### Join and access
| Setting | Default | What it does |
| ----------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Join link | Generated | Each game has a `/go/` link that sends participants straight in. Change the password to invalidate old shares. |
| Auto-assign | Off | On enrolls every classroom member and auto-enrolls anyone who joins the classroom later. Off means manual or join-link enrollment. Turning it off doesn't unenroll anyone. Turn it on for recurring events and large cohorts; keep it off for games scheduled later or selective access. |
### Timing
| Setting | Default | What it does |
| ---------------- | ------- | ----------------------------------------------------------------------------------------------- |
| Start / end time | Open | Start makes the game playable; end closes submissions. You can pause and resume a running game. |
| Timer | Off | Optional countdown for the session. |
### Teams
| Setting | Default | What it does |
| ------------ | ------- | ------------------------------------------------------------------------ |
| Team mode | On | Lets participants form teams. |
| Team scoring | Sum | How a team's score is computed: sum, average, top N, highest, or unique. |
## Common issues
**Participants can't access the game.** Check the join link and password, confirm the game has started and isn't paused, and confirm the participant is enrolled (or that auto-assign is on and they're a classroom member).
**Auto-assign isn't working.** The toggle must be on and the participant must be a classroom member.
**Wrong module selected.** If nobody has played, delete the game and create a new one. If anyone has started, the module can't change. Create a new game and keep the old one for its data.
**Settings aren't saving.** Click Save before leaving the page, confirm you have Classroom Manager or Tenant Manager access, and refresh if values look stale.
## Next steps
* [Organize classrooms](/manage-your-tenant/classrooms.md)
* [Track game analytics](/manage-your-tenant/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/manage-your-tenant/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.