# KC7 Host Resources Plan, run, and follow up on KC7 cybersecurity events, and manage your KC7 dashboard. This site walks you through hosting a KC7 cybersecurity event and using your KC7 dashboard. New hosts can go from request to running a session in a few hours. Returning hosts can jump straight to the dashboard docs to add games, manage classrooms, and review results. KC7 is a detective-style cybersecurity game. Participants investigate simulated incidents using the same tools real analysts use. You don't need a security background to host. The platform handles the teaching. Watch a 2-minute overview of KC7. {% embed url="" %} ## Pick Your Path
🎪 Host an EventPlan and run a KC7 event from request to follow-up/files/vUPBzKczUzG5Vt0XzA1Dhttps://docs.kc7cyber.com/hosting-events/quick-start
🏢 Your DashboardManage games, classrooms, users, and analytics/files/VDdxW9ISIRJBMkYXnYSghttps://docs.kc7cyber.com/dashboard/overview
🤝 Volunteer with KC7Contribute to content, scenarios, or community/files/hiotaOHzTuYZTufcMChkhttps://docs.kc7cyber.com/community/volunteer
💬 Get HelpDiscord, email, and troubleshooting/files/jhmb6uJhK1c6wKmGk8uLhttps://docs.kc7cyber.com/community/getting-help
## New Here? Three Steps
1. Request Your EventAbout 5 minutes.https://kc7cyber.com/gameon
2. Read the Quick StartAbout 15 minutes of prep.https://docs.kc7cyber.com/hosting-events/quick-start
3. Run Your Event45 minutes to a few hours.https://docs.kc7cyber.com/hosting-events/event-day
# Host an Event Plan, run, and wrap up a KC7 cybersecurity event. Everything for running a KC7 event, from the request form to the follow-up email. New hosts start with the quick start. Everything else here goes deeper on one part of the job.
Quick StartRequest, prep, and run your first event./pages/fUmyUGBgFwWNjElIIwfN
Plan Your EventFormat, logistics, promotion, timeline./pages/bLt2rpHLN821qozI6OV0
Run Event DayThe day-of guide./pages/H0ovo8O2jZKASzBLSphx
New to KC7 entirely? [What is a KC7 event?](/hosting-events/getting-started/what-is-kc7) explains the game and your role as host. # What Is a KC7 Event? What a KC7 event is, who hosts them, and what participants do A KC7 event is a hands-on cybersecurity experience where participants become investigators, working through a realistic (but fictional) cyber mystery using the same tools that professional analysts rely on every day. You bring the people and the setting. KC7 provides the game, the training, and the content, so you don't need a cybersecurity background to host. ## A Cybersecurity Mystery Game Built for Beginners KC7 is a story-driven cybersecurity game where players step into the role of investigators solving a cyber incident. They analyze simulated computer and network activity, look for suspicious patterns, and answer questions that move the story forward. The experience is designed from the ground up for people with no prior cybersecurity knowledge. Early questions teach the fundamentals, and each new challenge builds naturally on what came before. By the end, participants have practiced real skills like building a timeline of events, thinking logically about evidence, and explaining what happened in plain language. ## Your Role as Host: Set the Stage Hosting a KC7 event means gathering a group, whether students, employees, or community members, and giving them a shared space to learn together. You provide the time, the venue (physical or virtual), and the encouragement. KC7 handles everything instructional, including the game, the training content, and the built-in support that keeps participants moving forward. Your event might be a 90-minute classroom activity, a 3-hour team-building session, or a full-day workshop, in a computer lab, a conference room, or over Zoom. During the event, you circulate the room, answer logistical questions, keep energy up, and celebrate discoveries as they happen. ## Educators, Trainers, and Community Leaders Run These Events **Educators** use KC7 to introduce students to cybersecurity careers and computational thinking without having to teach the technical material themselves. The platform handles the instruction, freeing you to focus on facilitation and encouragement. **HR and corporate trainers** use it for security awareness training that doubles as team building. Employees learn to think like both attackers and defenders, and the interactive format sticks far better than slide decks. **Community organizers and student leaders** use it to bring people together around technology in an accessible, low-barrier way. No expensive equipment and no specialized instructors, just computers and an internet connection. **People building a cybersecurity program** use KC7 as a low-friction starting point. Run one successful event, gauge interest, and expand from there. ## How the Game Works for Participants Every participant follows the same path through the experience: 1. Open the participant link in their browser 2. Read the scenario briefing that sets up the mystery 3. Investigate using real security analysis tools embedded in the platform 4. Analyze log data to piece together what happened 5. Submit findings to the scoreboard as they progress 6. Pick up cybersecurity concepts naturally through the work itself There's nothing to install, no accounts to create ahead of time, and no prerequisites to worry about. ## The Tools Are Real Under the hood, participants work with the same technology stack that professional security analysts use daily: * **Azure Data Explorer (ADX)** stores and serves the security logs participants investigate * **Kusto Query Language (KQL)** is how they filter, search, and analyze the data * **KC7 Scoreboard** tracks progress and validates their answers in real time * **Built-in tutorials** are woven directly into the scenario, teaching concepts exactly when they're needed ## You Don't Need a Cybersecurity Background **The game teaches participants directly.** KC7 scenarios assume zero prior knowledge. Early questions introduce the basics, later challenges build on those foundations, and your role is keeping people motivated rather than explaining technical concepts. **The story carries the engagement.** Participants stay invested because they genuinely want to find out what happens next. **Hints are built into the platform.** When someone gets stuck, the game offers progressive hints that guide them forward without giving away the answer. You don't need to debug their queries or explain log formats. The platform handles that. KC7 runs from a 45-minute taster to a full-day workshop, and works as a competition, a team activity, or a relaxed learning session. See [Pick a format](/hosting-events/planning/planning#pick-a-format) to choose one. ## Skills Participants Walk Away With Participants practice the same skills professional security analysts use day to day: * **Log analysis:** reading and interpreting security event data * **Query writing:** using KQL to search and filter large datasets * **Pattern recognition:** spotting anomalies that point to suspicious activity * **Threat hunting:** following evidence trails to uncover what happened * **Critical thinking:** making judgments under uncertainty with incomplete information The thinking transfers beyond cybersecurity too: analyzing complex information, reasoning from evidence, and explaining technical findings in plain language. ## Your First Scenario: A Scandal in Valdoria Every host's first event runs KC7's flagship scenario: a mysterious security incident in the Kingdom of Valdoria, layered with political intrigue and digital evidence. The questions ramp up gradually: early ones teach basic log analysis and querying, middle ones apply those skills to deeper investigations, and later ones ask participants to synthesize evidence and draw conclusions. Most participants won't finish the entire scenario in a single session, and that's perfectly fine. Whether someone completes five questions or fifteen, they've had a meaningful learning experience. Everyone walks away having practiced real investigation skills, regardless of where they stop. ## What You'll Need to Get Started **For you:** * A free KC7 account, which gets created automatically when you request your event * About 1 to 2 days for your event request to be approved * A venue, either a physical space or a virtual meeting platform **For your participants:** * A computer with a modern browser (Chrome, Firefox, Edge, or Safari) * An internet connection * A willingness to try something new If someone can browse the web, they can play KC7. ## Start with One Event and Grow from There Most hosts run their first event as a trial. Run a single event and stop, or build KC7 into an ongoing program. Your account supports both, and the [dashboard guide](https://docs.kc7cyber.com/dashboard/overview) covers the platform once you want more. ## Ready to Host?
Run your first eventThe fast path, in about 5 minutes of reading./pages/fUmyUGBgFwWNjElIIwfN
Request your eventSubmit the request form to get started.https://kc7cyber.com/gameon
Plan your eventWalk through the full planning process./pages/bLt2rpHLN821qozI6OV0
# Quick Start The fast path from request to running your first KC7 event Your first event takes three steps and about 45 minutes of your time, plus a one to two day wait for approval. ## Before You Begin You need an organization name, a rough event date, and an estimated headcount. Nothing has to be final. {% hint style="info" %} First-time hosts often overthink the request. It simply starts a conversation, and most details get nailed down after approval. {% endhint %} ## The Three Steps {% stepper %} {% step %} ### Request Your Event Request your event The form takes about five minutes: contact info, organization, approximate date, estimated headcount, and a sentence about your audience. No proposals, no lesson plans. Approval usually lands in 1-2 days. If your event is time-sensitive, say so in the request and the team prioritizes it. While you wait, [plan the logistics](/hosting-events/planning/planning). {% endstep %} {% step %} ### Walk the Platform Yourself Your approval email arrives with two links. Save it. The **host dashboard** at `kc7cyber.com/intro/XXXX` is your control center. Spend 15-20 minutes here: * Watch the intro videos you'll show participants * Read the host guide * Open the live scoreboard and analytics tools {% hint style="warning" %} Keep the host dashboard link private. It's for you and your co-hosts, not participants. {% endhint %} The **participant link** at `kc7cyber.com/go/XXXX` is what you share with your group. From this one link, participants create an account, open the scenario, and start investigating. Test it yourself: * Create a test account and walk the sign-up flow * Read the opening of "A Scandal in Valdoria" * Solve a few challenges * Find the hint buttons so you can point stuck participants to them The email also includes access to your **dashboard**, your organization's account on KC7. Its free plan capacity is enough for many events in a row, and you can add games later without a new request. The [Dashboard guide](https://docs.kc7cyber.com/dashboard/overview) goes deeper. {% endstep %} {% step %} ### Run the Event Share the participant link with your group. They land in the scenario and start investigating. Watch progress from your host dashboard. Most participants take about 90 minutes. Some finish faster, some take longer, both are fine. Your job is to encourage people while the platform handles the teaching. {% endstep %} {% endstepper %} ## Common Questions
Can I request multiple events at once? Start with one. After your first event, you can create more games yourself from your dashboard without a new request.
What if event details change after approval? Date, count, and format changes are flexible and your links stay valid. For larger changes, email space.vars.support\_email.
Is there a cost? KC7 events are free for educational and community purposes.
What if I don't know all the details yet? Submit anyway. You work out specifics during planning.
## Want More Depth? * [Plan your KC7 event](/hosting-events/planning/planning) for marketing templates and detailed logistics * [Dashboard guide](https://docs.kc7cyber.com/dashboard/overview) for ongoing classroom use * [Discord community](https://docs.kc7cyber.com/community/getting-help) for real-time help from other hosts [Request your first event →](https://kc7cyber.com/gameon) # Plan Your Event Plan a KC7 event from request to event day, covering format, logistics, promotion, and the full prep timeline. Planning takes a few hours spread over two to three weeks, from request to event day. You handle the logistics and the encouragement while the platform teaches the cybersecurity. {% hint style="info" %} Already approved and need setup steps? Skip to [Pre-event setup](/hosting-events/running-your-event/pre-event-setup). {% endhint %} ## Before You Begin You need a rough date, an estimated headcount, and a sense of in-person or virtual. Nothing has to be final. ## Submit the Request Submit the form at [kc7cyber.com/gameon](https://kc7cyber.com/gameon). It takes about two minutes, and approval lands within 1-2 days. The [quick start](/hosting-events/getting-started/quick-start) covers the full process. ## Pick a Format Settle these while you wait for approval. ### In-Person or Virtual | | In-person | Virtual | | -------- | ----------------------------------------- | -------------------------------- | | Strength | High energy, easier facilitation | Flexible scheduling, no venue | | Needs | Room, WiFi, power, projection | Video platform, screen sharing | | Best for | Schools, training rooms, community spaces | Distributed teams, larger groups | The [In-person guide](/hosting-events/running-your-event/in-person) and [Virtual guide](/hosting-events/running-your-event/virtual) cover each in depth. ### Duration {% tabs %} {% tab title="45 minutes" %} **Good for** tight class periods, taster sessions, intros. **Format:** 5 min welcome, 35 min investigation, 5 min wrap-up. Most participants finish 3-6 questions. Frame it as first exposure. Tell them they can keep going later. {% endtab %} {% tab title="90 minutes" %} **Good for** first-time hosts, classroom periods, lunch-and-learns. **Format:** 10 min welcome and setup, 70 min investigation, 10 min debrief. Most won't finish all questions. Emphasize discovery over competition. {% endtab %} {% tab title="3 hours" %} **Good for** after-school programs, professional development, community workshops, team building. **Format:** 15 min welcome, 10 min teams and setup, 2.5 hours investigation with breaks, 15 min winners and wrap-up. Many participants complete the module. Expect natural collaboration. {% endtab %} {% tab title="Full day" %} **Good for** hackathons, training intensives, summer camps, conferences. **Format:** 30 min welcome and team building, 3-4 hours investigation, 1 hour lunch, 2-3 hours continued play or a new module, 30 min awards and reflection. Plan for multiple modules and deeper skill development. {% endtab %} {% endtabs %}
Sample agendas: 90-minute workshop, 3-hour competition, half-day intensive **90-minute workshop** | Time | Activity | Host notes | | --------- | ----------------------------- | ----------------------------------------------------------------- | | 0-5 min | Welcome and introductions | Keep it brief, build energy | | 5-10 min | KC7 overview and scenario | Use the [host scripts](/hosting-events/event-resources/templates) | | 10-15 min | Account setup and first login | Circulate to help | | 15-75 min | Investigation time | Roam and encourage, don't solve | | 75-85 min | Share discoveries | Ask "What surprised you?" | | 85-90 min | Next steps and resources | Leave them wanting more | **3-hour competition** | Time | Activity | Host notes | | ----------- | ------------------------- | -------------------------------------- | | 0-10 min | Registration and mingling | Background music helps | | 10-20 min | Welcome and rules | Cover scoring, teams, prizes | | 20-30 min | Team formation | Mix skill levels, name tags | | 30-45 min | Setup and first questions | Make sure all teams are progressing | | 45-135 min | Core investigation | 10-min break around the 90-minute mark | | 135-145 min | Final submissions | Build excitement | | 145-165 min | Winner announcements | Celebrate everyone, not just winners | | 165-180 min | Debrief and networking | Connect to real-world work | **Half-day intensive** | Time | Activity | Host notes | | ----------- | ---------------------------- | ------------------------------- | | 0-30 min | Welcome and team building | Icebreakers, collaborative tone | | 30-60 min | KC7 training and orientation | Deeper cyber concepts | | 60-180 min | Module 1 | Focus on fundamentals | | 180-240 min | Lunch and networking | Let teams bond | | 240-360 min | Module 2 or advanced | For teams who finished | | 360-390 min | Presentations and awards | Teams share findings | | 390-420 min | Reflection and next steps | Career pathways |
### Individual or Team Play **Individual play** suits classroom assessments, self-paced learning, large events, and mixed skill levels. Logistics stay simple and progress tracks per person. **Team play (2-4 people)** suits corporate team building, social events, and skill sharing. You get peer learning and a closer simulation of real security work. Even in individual events, people help each other informally. That's fine. ### Scoring Posture {% tabs %} {% tab title="Learning-focused" %} Hide the scoreboard at first, reveal it near the end, emphasize participation, and award creativity and teamwork. Good for educational settings and beginners. {% endtab %} {% tab title="Competitive" %} Display the live scoreboard, announce leaders periodically, offer real prizes, and consider playoff rounds for top teams. Good for hackathons and corporate events. {% endtab %} {% tab title="Collaborative" %} Share interesting findings publicly, cross-pollinate discoveries between teams, award group achievements, and focus on collective learning. Good for community events and workshops. {% endtab %} {% endtabs %} ## Plan Logistics Test everything from the actual venue at least a week ahead so event day stays calm. ### Venue Seat everyone comfortably with 10-15% extra space, clear sightlines to the screen, aisle room for hosts to circulate, and accessible seating near doors and facilities. {% tabs %} {% tab title="In-person venue" %} **Essential** * [ ] Stable WiFi for all participants (3 Mbps per device minimum) * [ ] Sufficient power outlets for all devices * [ ] Tables and chairs for all participants * [ ] Projection screen or large display for opening and closing * [ ] Climate control for a 2+ hour event * [ ] Accessible restroom facilities **Recommended.** Backup internet (mobile hotspot), extra power strips, a whiteboard, and lighting that works for both screens and notes. {% endtab %} {% tab title="Virtual venue" %} **Essential** * [ ] Video conferencing platform (Zoom, Teams, Google Meet) * [ ] Screen sharing for opening presentation * [ ] Stable internet (10+ Mbps upload for host) * [ ] Backup communication method (email, phone, secondary platform) **Recommended.** Recording (with consent), chat, breakout rooms for team events, co-host permissions for volunteers, and a waiting room. {% endtab %} {% endtabs %} ### Technical Setup Most technical surprises come from networks you didn't test. Visit the venue, connect to the actual network, load a practice game on multiple devices, and run the projector and audio with your laptop. School and corporate firewalls sometimes block cloud services, so confirm access ahead of time. Full specs live in [Technical requirements](/hosting-events/planning/technical-requirements).
Network testing checklist * [ ] Access kc7cyber.com from venue WiFi * [ ] Load a practice game and verify it runs smoothly * [ ] Test with multiple devices simultaneously * [ ] Confirm the WiFi password is available event day * [ ] Identify an IT contact for day-of troubleshooting * [ ] Plan a backup (mobile hotspot, guest network)
For the opening and closing, use a large screen or projector with a tested HDMI connection and audio for the intro videos. If the projector fails, screen-share to participant devices. A second display for the live scoreboard is a nice optional touch. ### Materials KC7 runs in a browser, so you don't need printed handouts. Hosts need the dashboard login, the participant link ready to display, the [host scripts](/hosting-events/event-resources/templates#host-scripts), and the [troubleshooting guide](/hosting-events/event-resources/troubleshooting) handy. Optional: name tags, certificates, prizes, snacks for longer events, and a sign-in sheet. ### Staffing Solo hosting works for 15 or fewer. Complete "A Scandal in Valdoria" yourself first, then focus on encouragement and light troubleshooting during the event. For larger groups, helpers free you up. They don't need cybersecurity expertise.
Team hosting roles for 16+ participants | Role | Ratio | What they do | | -------------------- | ----------- | ------------------------------------------------------------------------------------------------------------ | | Lead host | 1 | Opening and closing, overall coordination, time management, final scoreboard review | | Registration support | 1 per 25 | Welcome arrivals, help with account creation, distribute materials, answer general questions | | Technical support | 1 per 15-20 | Troubleshoot browser and connection issues, help stuck participants find hints, report patterns to lead host | | Roaming encouragers | 1 per 20-30 | Circulate, offer moral support, identify who might need technical help, maintain positive energy | Have all volunteers complete the game module in advance. Brief them together on roles and common issues so you don't have everyone helping the same person.
### Registration Start small (10-20) for your first event and scale up as you gain experience. Plan for a 10-20% no-show rate and send reminders to reduce it. If demand exceeds capacity, run multiple sessions. Tell participants what to bring (a laptop and a browser) in the confirmation and reminders. ### Accessibility KC7's web platform supports screen readers, adjustable fonts, and closed captions on intro videos. Your job is the physical and social environment: an accessible venue and restrooms, reserved seating near facilities, clear pathways, extra time for those who need it, a quieter space for reduced stimulation, and permission to work with a partner. {% hint style="success" %} Tell participants they can work at their own pace and don't need to finish all challenges. The learning happens throughout. {% endhint %} ### Backup Plans
If this fails, do that | If this fails | Backup | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | WiFi | Mobile hotspot tested in advance, guest network credentials, IT contact ready, postponement plan for total outage | | Projector | Screen-share to participant devices, fall back to printed materials, use a laptop display as a last resort with small groups | | Platform | Contact KC7 support (space.vars.support\_email), check Discord, have an alternative activity ready | | Lower attendance | Proceed anyway. Five participants still have a great experience and get more attention. | | Higher attendance | Add seating, split into multiple sessions, recruit spontaneous volunteers, manage expectations on personalized support | | Host can't attend | Identify a co-host or backup in advance, share materials, prepare a participant communication plan |
## Promote Your Event Two to three weeks of outreach with a few reminders fills most events. Match the message to the audience, and lead with "no experience needed" and the time commitment. {% tabs %} {% tab title="Students" %} **Channels.** School email, Discord, Instagram, classroom announcements, student org partnerships. **Messages.** "Learn by doing, not lectures." "No experience required." "Real skills for your resume." {% endtab %} {% tab title="Professionals" %} **Channels.** Company email, LinkedIn, professional Slack channels, department meetings. **Messages.** "Practical cybersecurity training." "Team collaboration exercise." "Real-world scenarios." {% endtab %} {% tab title="Community" %} **Channels.** Community newsletters, social media groups, local organization partnerships, word of mouth. **Messages.** "Accessible to all backgrounds." "Build digital literacy." "Fun community event." {% endtab %} {% endtabs %} Have answers ready for the objections you'll hear most: | Concern | Response | | --------------------------------------- | ------------------------------------------------------------------------------------------------- | | "I don't have cybersecurity experience" | "Perfect. This is designed for beginners. No prerequisites." | | "I'm not good with technology" | "If you can browse the web, you can play KC7." | | "I don't have time" | "90 minutes to 3 hours. Less than a movie." | | "What if I don't finish?" | "No pressure. Learning happens throughout. Many people don't finish and still have a great time." | Ready-made invitation emails, social posts, and registration fields are in [Templates and materials](/hosting-events/event-resources/templates#announcement-templates). ## Set up After Approval Save the approval email. It has your host dashboard link, participant link, and dashboard access, each described in the [quick start](/hosting-events/getting-started/quick-start#the-three-steps). Walk through both links as a participant before sharing them. ## Prepare in the Final Week Test your setup from the actual venue or platform about a week out. * **In-person:** confirm WiFi handles the group, screens display web content clearly, and there are enough power outlets. * **Virtual:** test screen sharing, video, and audio. A few days before, send participants the participant link and note they need only a computer and a browser. ## Full Prep Timeline
Every milestone, from request to follow-up **2+ weeks before** * [ ] [Submit your event request](/hosting-events/getting-started/quick-start) at [kc7cyber.com/gameon](https://kc7cyber.com/gameon) * [ ] Sketch the basics: date range, estimated headcount, in-person or virtual * [ ] [Choose your format](#pick-a-format): duration and play style * [ ] [Start logistics planning](#plan-logistics): venue, WiFi, staffing * [ ] Create a registration form and begin [promoting](#promote-your-event) **1-2 weeks before** * [ ] Receive your [approval email](/hosting-events/getting-started/quick-start#the-three-steps) * [ ] [Play the game yourself](/hosting-events/running-your-event/pre-event-setup#play-the-game-yourself), the single most useful prep step * [ ] Test your [technical setup](#technical-setup) from the actual venue or platform * [ ] Send invitation emails using [templates](/hosting-events/event-resources/templates#email-templates) * [ ] [Brief volunteers](#staffing) on roles and common issues **2-3 days before** * [ ] Send a [reminder email](/hosting-events/event-resources/templates#email-templates) with the participant link * [ ] Do a [final tech check](/hosting-events/running-your-event/pre-event-setup#pre-event-checklist) * [ ] Review your [opening remarks](/hosting-events/event-resources/templates#host-scripts) **Day of** * [ ] Arrive 30-60 minutes early and [set up](/hosting-events/running-your-event/event-day#before-participants-arrive-15-to-30-minutes) * [ ] [Welcome participants](/hosting-events/running-your-event/event-day#welcome-and-introduction-10-to-15-minutes) and play the intro videos * [ ] Share the participant link, then [facilitate the investigation](/hosting-events/running-your-event/event-day#facilitate-the-investigation-60-to-90-minutes) * [ ] [Wrap up](/hosting-events/after-the-event/after): celebrate the group and point everyone forward **After the event** * [ ] Send a thank-you and the [feedback survey](/hosting-events/event-resources/templates) within 24 hours * [ ] [Wrap up and follow up](/hosting-events/after-the-event/after): document lessons, plan the next event
## Optional Extras * Print certificates from the [templates](/hosting-events/event-resources/templates) * Offer small prizes for varied achievements, not just first place * Plan a brief celebration at the end KC7 already awards digital badges on completion. ## Next Steps
Prepare after approvalThe pre-event setup steps./pages/PMhPosFxQoMw7rJmyEmy
Run event dayThe day-of guide./pages/H0ovo8O2jZKASzBLSphx
Wrap UpClose out and follow up./pages/28MGUgheiwmdsDSFpA2m
# Technical Requirements What KC7 needs to run, by role, plus testing steps and common blockers This is the reference for what KC7 needs to run, broken down by role and venue type. If your participants can browse the web, they can play. ## Quick Summary * Stable broadband internet * A modern browser updated within the last year * A computer or laptop (tablets work but aren't ideal) * No installation ## Requirements by Role ### Hosts **Minimum.** A free account at [kc7cyber.com](https://kc7cyber.com), internet, an email address for the approval, and a basic computer. **Recommended.** A laptop or desktop, an optional second monitor, backup internet for virtual events, and a working microphone and camera if hosting online. ### Participants **Minimum.** Desktop, laptop, or Chromebook. Updated Chrome, Firefox, Safari, or Edge. A stable connection at 3 Mbps or more. 1024x768 resolution or higher. Keyboard and mouse or trackpad. **Recommended.** A full-size screen, wired internet, headphones for virtual events, and a place to take notes. ## Browser Compatibility | Support | Browsers | | --------------- | --------------------------------------------- | | Fully supported | Chrome 90+, Firefox 88+, Safari 14+, Edge 90+ | | Limited | Older browser versions, mobile browsers | | Not supported | Internet Explorer | JavaScript, cookies, and pop-ups must be enabled. ## Venue Requirements ### In-Person Events You need power outlets for everyone, WiFi that handles concurrent users, projection for instructions (recommended), and tables with computer space. For network, plan 3 Mbps per participant or more. Standard HTTPS (port 443) must be open. The network can't block kc7cyber.com. A guest network helps if your main network is restricted. ### Virtual Events **Hosts need** a video platform (Zoom, Teams, Discord), screen sharing, 10 Mbps upload or more, and a backup communication channel. **Participants need** access to the video platform, the ability to view a shared screen, and ideally a phone for video alongside a computer for the game. ## Test Before the Event **One week before.** Test the participant link on multiple browsers, verify network capacity, check firewall and content filter settings, and test projection or screen sharing. **Day before.** Confirm all links work, run through with a sample participant account, verify venue WiFi credentials, and have backup access methods ready. **Day of.** Arrive early, fully test one machine, and keep IT support contact info handy. ## Common Blockers ### School and Corporate Networks Firewall blocking KC7? Whitelist `*.kc7cyber.com`, switch to the guest network, or fall back to mobile hotspots. Content filter blocking the game? Request a temporary exception, work with IT to pre-approve, and test the week before. ### Browser Issues Old browser version? Update before the event or have an alternate browser ready. Extensions interfering? Switch to incognito mode, disable ad blockers temporarily, or change browsers. ## Device Notes | Device | Supported | Notes | | -------------- | --------------- | ----------------------------------------------------------------------- | | Chromebook | Yes | Keep Chrome OS updated. Check school management settings. | | iPad or tablet | Functional | Smaller screens and touch slow people down. An external keyboard helps. | | Phone | Not recommended | Use only for event communication, not play. | ## Bandwidth Calculator ``` Required Bandwidth = Number of Participants × 3 Mbps ``` | Participants | Bandwidth | | ------------ | --------- | | 10 | 30 Mbps | | 30 | 90 Mbps | | 100 | 300 Mbps | Add a 50% buffer for headroom. {% hint style="warning" %} Test KC7 access from school or corporate networks well in advance. Some networks block cloud services or require IT approval for whitelisting. {% endhint %} ## Tips for Large Events For 50 or more participants, stagger start times, line up dedicated IT support, test at maximum expected load, and have offline activities ready as a backup. ## Quick Troubleshooting **Can't access KC7.** Check internet, try a different browser, clear cache, disable VPN, check firewall. **Slow performance.** Close unnecessary tabs, check internet speed, try a wired connection, lower video quality on virtual events. ## Support For technical issues during an event, start with this checklist, then visit [Discord](https://docs.kc7cyber.com/community/getting-help) for real-time help, or email for a 24-48 hour response. For pre-event planning, walk through requirements with your IT team, test the participant experience, and prepare contingencies. # Set up Before the Event Final preparation in the week before your KC7 event Once approved, plan a couple of hours over the week before. The most useful step by far is playing the game yourself. For the links in your approval email, see the [quick start](/hosting-events/getting-started/quick-start#the-three-steps). ## Play the Game Yourself Complete "A Scandal in Valdoria" before your event. You'll know where people get stuck and feel confident guiding them. 1. Go to [kc7cyber.com/go/VALDY](https://kc7cyber.com/go/VALDY). 2. Create a KC7 account if you don't have one. 3. Play through. Plan for about 90 minutes. 4. Note the confusing parts, the "a-ha" moments, and how long each section takes. ## Prepare Your Team **Solo hosts.** Complete the module, review [Technical requirements](/hosting-events/planning/technical-requirements), and keep support contacts handy. **Team hosts.** Have all volunteers complete the module. Assign registration, tech support, and roaming roles, brief the team on common issues, and pick a comms channel for the day. Pull your opening, mid-event, and closing wording from the [host scripts](/hosting-events/event-resources/templates#host-scripts). ## Pre-Event Checklist **One week before** * [ ] Complete "A Scandal in Valdoria" yourself * [ ] Brief volunteers and test your Go Link (the participant link from your approval email) * [ ] Send participant invitations * [ ] Review [Technical requirements](/hosting-events/planning/technical-requirements) **A few days before** * [ ] Test the tech setup from the actual venue or platform * [ ] Prepare opening remarks and send a participant reminder **Day of** * [ ] Arrive 15 to 30 minutes early * [ ] Test internet and projection, then open the host dashboard and Go Link The [full prep timeline](/hosting-events/planning/planning#full-prep-timeline) has every milestone.
Tips from experienced hosts > "I tell participants upfront that getting stuck is part of learning. I got stuck too when I played." (High school teacher) > "I walk around and ask 'What are you discovering?' instead of 'Do you need help?'" (Corporate trainer) > "I keep the troubleshooting guide open on my laptop. It's saved me several times." (University TA)
## Next Step Move on to [Run event day](/hosting-events/running-your-event/event-day). # Run Event Day Run your KC7 event from welcome through wrap-up This guide takes you through event day in order, from pre-arrival setup through the welcome, the investigation, and the close. Pull this page up on your phone and follow along. {% hint style="info" %} Three things hosts wish they'd known: the first 15 minutes (logins and orientation) are the hardest, then it gets easier. You don't need to understand the cybersecurity, since the game teaches it. And most participants won't finish, which is fine. Five questions of progress is a successful event. {% endhint %} ## Before You Begin You need a tested setup and your approval email open. If you haven't done final prep, see [Set up before the event](/hosting-events/running-your-event/pre-event-setup). ## The Five Phases {% stepper %} {% step %} ### Before Participants Arrive (15 to 30 Minutes) Arrive early to test your setup. 1. Confirm your internet connection is stable. 2. Open your host dashboard on your device. 3. Open the Go Link (the participant link from your approval email, ending in your event code) in a separate window so you can show participants what they'll see. 4. Test projection or screen sharing if you're using it. 5. Have any backup tech ready (mobile hotspot, second laptop). {% endstep %} {% step %} ### Welcome and Introduction (10 to 15 Minutes) #### Play the KC7 Intro Videos Start by playing the two videos on your KC7 intro page. They cover what KC7 is, the Valdoria scenario, and what participants will experience. #### Set the Stage After the videos, add your own welcome. Keep it short. Sample wording: ``` Welcome to our KC7 cybersecurity investigation. You're about to become digital detectives solving a mystery in the Kingdom of Valdoria. No cybersecurity experience needed. The game teaches you as you go. You'll have about 90 minutes. Don't worry about finishing. The learning happens throughout, and everyone works at their own pace. There's a live scoreboard if you enjoy friendly competition. ``` #### Cover Four Key Points * This is meant to be challenging. Getting stuck is part of learning. * Each person creates their own account so progress is tracked individually. * Working with a neighbor or teammate is encouraged. * Ask for help anytime. You're not expected to solve it alone. {% endstep %} {% step %} ### Get Participants Started (5 to 10 Minutes) #### Share the Go Link Display your Go Link where everyone can see it. Write it on the board, project it, drop it in chat for virtual events, or text the link to the group. #### Account Creation Have everyone visit the Go Link and create an account. Two options: * **Full account (recommended).** Saves progress so participants can return later. * **Guest play.** Works for the event, but progress isn't saved. Encourage full accounts so people can finish later if they want. #### Quick Check Once everyone has accessed the game, ask: "Can everyone see the Kingdom of Valdoria welcome screen?" If yes, they can start. {% endstep %} {% step %} ### Facilitate the Investigation (60 to 90 Minutes) Your job during the investigation is encouragement and light guidance. The game handles the cybersecurity teaching. #### Do This * Circulate and check energy levels. * Offer encouragement when someone gets stuck. * Remind participants to use the built-in hint system. * Monitor the live scoreboard for overall progress. * Be visibly enthusiastic about discoveries. #### Avoid This * Giving away answers. * Teaching cybersecurity concepts. The game does that. * Rushing participants who are working methodically. * Focusing only on the highest scorers. For detailed coaching strategies, see [Support participants](/hosting-events/running-your-event/supporting-participants). #### Use Your Host Tools The **live scoreboard** shows progress. Check it every 15 to 20 minutes. If most people are stuck on the same challenge, give a gentle group reminder about hints. The **analytics page** shows which challenges are hardest and overall success rates. Useful for spotting common sticking points. For what to say to stuck participants, see [Support participants](/hosting-events/running-your-event/supporting-participants). #### Time Check at 30 to 45 Minutes ``` How's everyone doing? Great progress on the scoreboard. Reminder that there are built-in hints if you get stuck, and you're welcome to discuss approaches with each other. ``` #### Time Check at 60 Minutes (If Applicable) ``` About 30 minutes left. If you haven't finished, that's normal. Focus on the challenges you find most interesting rather than trying to finish everything. ``` {% endstep %} {% step %} ### Wrap Up (10 to 15 Minutes) Celebrate the group, then the top performers, then point everyone forward. Sample wording: ``` Congratulations everyone. You've just completed your first cybersecurity investigation. Whether you solved the whole mystery or worked through a few challenges, you've learned real digital investigation skills. ``` For the full closing flow with sample script, see [Wrap up your event](/hosting-events/after-the-event/after). {% endstep %} {% endstepper %} ## Quick Reference * **Welcome and intro.** 10 to 15 minutes * **Get started.** 5 to 10 minutes * **Investigation.** 60 to 90 minutes * **Wrap-up.** 10 to 15 minutes ## Next Step Continue to [Wrap up your event](/hosting-events/after-the-event/after) for the closing ceremony and post-event steps. # In-Person Events Run a KC7 event in a physical room This covers what's different about running KC7 in a physical room: venue, WiFi, room setup, on-site troubleshooting, and cleanup. For the run-of-show and coaching that apply to any event, see [Run event day](/hosting-events/running-your-event/event-day) and [Support participants](/hosting-events/running-your-event/supporting-participants). ## Before You Begin You need an approved event, a confirmed venue, and a rough headcount. If you're still planning, start at [Plan your event](/hosting-events/planning/planning). ## Pick a Venue A workable venue gives everyone a seat with laptop space, accessible power, reliable WiFi, and a screen visible from anywhere in the room, plus space to walk between participants. Check signage, accessibility, restrooms, and parking or transit. {% tabs %} {% tab title="Classroom or lab" %} **Good for** schools and training. Built-in tech and IT support. Watch for network restrictions and after-hours limits. {% endtab %} {% tab title="Conference room" %} **Good for** corporate events. Reliable infrastructure and AV. Seating is formal, refreshment space tight. {% endtab %} {% tab title="Community space" %} **Good for** public workshops. Flexible and low-cost, though WiFi and equipment vary and setup may fall to you. {% endtab %} {% tab title="Hackathon or event space" %} **Good for** large competitions. Strong WiFi, at higher cost and longer booking lead time. {% endtab %} {% endtabs %} ## Manage WiFi WiFi is the most common failure point. The week before, test it with as many devices as you can, verify roughly 3 Mbps per participant, and confirm the network doesn't block `*.kc7cyber.com`. On the day, prefer a guest network and keep a mobile hotspot as backup. Display the WiFi name and password where everyone can see it. {% hint style="warning" %} School and corporate networks often block cloud services. Test KC7 access in advance and request whitelisting if needed. The [bandwidth calculator](/hosting-events/planning/technical-requirements#bandwidth-calculator) helps you size the network. {% endhint %} ## Set up the Room Pick a layout for your group: | Layout | Group size | Notes | | -------- | ----------- | --------------------------------------------------------------- | | Theater | 30+ | Rows facing the screen. Easy to present, harder to collaborate. | | Clusters | Team events | Groups of 3 to 4 per table. You circulate between groups. | | U-shape | 10-20 | Everyone faces center. You see the whole room. | | Open | Flexible | Scattered tables, informal, pick-your-seat. | Test the projector and audio before participants arrive. Keep the screen showing something useful throughout: a welcome slide with WiFi credentials and the participant link, the intro videos during the opening, the scoreboard at key moments. ## Arrive 60-90 Minutes Early * [ ] Venue unlocked, tables and chairs in your layout, signage posted * [ ] Projection and audio tested * [ ] WiFi connected, speed verified, credentials displayed * [ ] One participant account walked through end-to-end * [ ] Host dashboard open; participant link tested in two browsers If you have co-hosts, brief them 30 minutes before: assign each a section of the room, align on when to step in, and confirm their access works. ## Facilitate in the Room The coaching itself (hints not answers, the Socratic move, handling different skill levels, individual vs team play) is the same for any event and lives in [Support participants](/hosting-events/running-your-event/supporting-participants). What a physical room changes: * **Circulate constantly.** Walk a full perimeter every 10-15 minutes, vary your route, and position yourself where you can see most of the room. Pause near anyone who looks stuck without hovering. * **Use the room's energy.** Call out wins out loud ("Several people just cleared Challenge 3"). Read body language: frustrated energy means a reminder about hints, low energy means call a break, widespread confusion means address it to the whole room. * **Handle struggles privately.** Check in with struggling participants one-on-one, never publicly. Mix skill levels at tables so peers help each other. ## Troubleshoot on Site Generic issues (KC7 won't load, lost progress) are in the [Troubleshooting guide](/hosting-events/event-resources/troubleshooting). The on-site-specific ones: **"I can't connect to WiFi."** Verify credentials, forget and rejoin the network, then fall back to a hotspot. If it's widespread, get IT involved. **Power and hardware.** If laptops start dying, point people to outlets and share power strips. For projector failures, share the participant link verbally and let participants work on their own screens. Bring more power strips and extension cords than you think you need. **Technical meltdown.** Stay calm, since participants follow your lead. Acknowledge the issue out loud, switch to your backup plan, and keep the room engaged. ## What to Bring **Essential.** Power strips and extension cords, displayed WiFi credentials and participant link, a host device with dashboard access, and a mobile hotspot backup. **Nice to have.** Name tags, prizes, snacks, a printed troubleshooting guide, and a backup activity in case of an outage. ## Close the Event For the closing flow (final scoreboard, recognition, next steps), see [Wrap up your event](/hosting-events/after-the-event/after). In a physical venue, also reset the room: * [ ] Furniture back to original layout * [ ] Equipment and materials packed, feedback forms collected * [ ] Equipment off, lights off, doors locked ## Related Pages
Run event dayThe day-of guide./pages/H0ovo8O2jZKASzBLSphx
Run a virtual eventRun online instead./pages/IFCmMHI3aKqjnP5Vpjol
# Virtual Events Run a KC7 event over video This covers what's different about running KC7 over video: platform, screen sharing, chat, breakout rooms, and remote troubleshooting. For the run-of-show and coaching that apply to any event, see [Run event day](/hosting-events/running-your-event/event-day) and [Support participants](/hosting-events/running-your-event/supporting-participants). ## Before You Begin You need an approved event, a video platform you can host on, and at least 10 Mbps upload. If you're still planning, start at [Plan your event](/hosting-events/planning/planning). ## Pick a Platform {% tabs %} {% tab title="Zoom" %} **Best for most events.** Reliable screen sharing, breakout rooms, recording, polls, and a waiting room. Pre-create breakout rooms and enable co-hosts. {% endtab %} {% tab title="Microsoft Teams" %} **Best where Teams is already standard.** Test external guest access ahead of time, since every organization configures it differently. {% endtab %} {% tab title="Discord" %} **Best for community and gaming audiences.** Free for large groups. Set up a main voice channel, per-team channels, and text channels for links. {% endtab %} {% tab title="Google Meet" %} **Best for Google Workspace orgs.** Breakout and engagement features are limited, so keep groups smaller. {% endtab %} {% endtabs %} ## Set up Before the Event A week out, test the platform end-to-end: screen sharing, breakout rooms, recording, and co-host permissions. Run the KC7 intro page through once to confirm the videos play with audio. Confirm 10 Mbps upload and send calendar invites. Thirty to sixty minutes before, join early and run through this: * [ ] Test camera, mic, and screen-share quality * [ ] Load the KC7 intro page; have the participant link ready to paste in chat * [ ] Open the host dashboard on a second screen or device * [ ] Enable the waiting room * [ ] Co-hosts join, get permissions, and confirm roles ## Share Your Screen Well Share a specific tab or window, not your full screen. Close email and messaging apps. Enable "Share Computer Sound" before playing videos. | Phase | What to share | | ------------- | ------------------------------------------------------- | | Intro | KC7 intro page, videos with audio, participant link | | Investigation | Stop sharing so participants focus on their own screens | | Wrap-up | Final scoreboard and next steps | ## Run It Online The run-of-show is the same as any event ([Run event day](/hosting-events/running-your-event/event-day)). Online, the differences are: * **Chat is your room.** Pin the participant link the moment you open. Have a co-host watch chat while you present, and save the transcript at the end. * **Breakout rooms** for teams or small-group help. Aim for 2 to 4 people, set a timer, and drop in to listen before interrupting. * **Energy takes more effort.** "Zoom fatigue" is real. Use higher vocal energy, call on people by name, run quick polls, and schedule breaks. Watch chat and the scoreboard for who's gone quiet. ## Troubleshoot Remotely **"I can't hear you."** Check mute, test speakers, try headphones, rejoin. **"You're breaking up."** If others hear you fine, it's on their end (have them turn off video). If not, check your connection and drop your own video. **"I can't see the screen."** Confirm you're sharing, and have them maximize the share or exit speaker view. **"I got kicked out."** Re-post the link in chat. If your connection drops, a co-host keeps things running while you rejoin. Platform quirks: Zoom breakout rooms must be enabled in account settings beforehand, Teams external guests need access enabled, and Discord issues usually trace to device settings or role permissions. ## Record the Session (Optional) {% hint style="warning" %} Announce recording and get any consent your jurisdiction requires before you start. {% endhint %} Record the intro, key announcements, and wrap-up, and pause during investigation. Useful for absent registrants and promo clips. ## Hybrid Events {% hint style="info" %} Hybrid is hard. Unless you must, run separate in-person and virtual events for a better experience on both sides. {% endhint %} ## Related Pages
Run event dayThe day-of guide./pages/H0ovo8O2jZKASzBLSphx
Run in personRun on site instead./pages/pcYoyFJ9EQRJXx4fRvNa
# Support Participants Coach participants through the investigation without being a cybersecurity expert Your job during the investigation is to encourage, point people to the built-in resources, and keep energy positive. KC7 handles the cybersecurity instruction. For the event flow, see [Run event day](/hosting-events/running-your-event/event-day). ## What You Own and What You Don't **You own:** a safe environment to make mistakes, pointing people to hints and tutorials, circulating to check in, celebrating discoveries, and managing time. **You don't own:** teaching cybersecurity (the game does that), solving challenges, answering every technical question, or making sure everyone finishes. Learning happens all the way through, wherever someone stops. ## Give Hints Without Spoilers Escalate gently, one step at a time: 1. Redirect to resources. "Have you tried the hint button?" 2. Ask a guiding question. "What columns of data do you have?" 3. Give strategic direction. "This challenge is about patterns in the timestamps." Instead of answering, ask a question back: they ask "How do I filter this?", you ask "What are you trying to find?" {% hint style="warning" %} Never give exact answers or syntax. Guide them to the built-in hints or a peer. {% endhint %} ## What to Say | Situation | What to say | What to avoid | | -------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------- | | "I'm completely stuck." | "Have you tried the hint button? What have you tried so far?" | Giving the answer | | "Is this answer right?" | "What makes you think that? Try submitting and see." | Confirming from their screen | | "I don't understand this." | "The game explains concepts as you hit them. Try reading the challenge again." | A technical explanation | | "This is too hard." | "These are meant to be challenging. Getting stuck is part of learning. Try a hint." | Agreeing, or comparing them to others | | "I'm finished. What now?" | "Did you try the bonus challenges? Want to help others without giving answers?" | Letting them disengage | For a struggling participant, normalize it ("This one stumps almost everyone"), shift focus to what they've already learned, and offer a fresh start ("Grab water and come back"). "You haven't figured it out *yet*" keeps the door open. For an advanced one, deepen the thinking ("Can you explain why that works?") or invite them to peer-teach. ## Energy Check-Ins Three group nudges during the event: > **30-45 min:** "Great progress on the scoreboard. Reminder that there are built-in hints if you get stuck." > **60 min:** "About halfway. Feeling stuck is normal. These are designed to make you think. Use those hint buttons." > **Final 30 min:** "Thirty minutes left. If you haven't finished, that's normal. Focus on the challenges you find most interesting." ## When to Step in vs Let Them Struggle Healthy struggle is 5 to 10 minutes of active thinking. Step in when frustration turns to disengagement, they've been stuck 15+ minutes with no progress, they're unaware of a resource, or tech is blocking them. ## By Format {% tabs %} {% tab title="In-person" %} Circulate constantly, crouch to eye level when helping, and use group announcements for common issues. Check in with struggling participants privately, and mix skill levels at tables. {% endtab %} {% tab title="Virtual" %} Monitor chat and acknowledge every question. Public chat for tips that help everyone, private messages for individual encouragement. Post periodic hint reminders, and use breakout rooms for small-group help. {% endtab %} {% endtabs %} ## Host Tools Check the **live scoreboard** every 15 to 20 minutes (not constantly) for group progress, and the **analytics dashboard** for which challenges are hardest. Use both for general guidance, not to single people out. ## Technical Issues Specific fixes are in the [Troubleshooting guide](/hosting-events/event-resources/troubleshooting). In the moment: stay calm, try a quick fix (refresh, different browser, clear cache), escalate to support if needed, and keep everyone else engaged. {% hint style="info" %} If KC7 is loading and accepting answers, it's working. The difficulty is intentional. {% endhint %} ## Finishers and Stallers Celebrate early finishers and invite them to help others or explore bonus challenges. Reassure those still working that not finishing is normal. Their account saves progress, so they can continue anytime. ## Related Pages * [Troubleshooting guide](/hosting-events/event-resources/troubleshooting) * [Event FAQs](/hosting-events/event-resources/faq) * [Get help](https://docs.kc7cyber.com/community/getting-help) # Wrap Up Your Event Close your event, share results, and decide whether to follow up. Wrapping up has two parts: the closing ceremony in the last 15 minutes of the event, and the post-event work afterward. The ceremony and the same-day basics are required. Everything beyond that is optional. ## The Closing Ceremony (Final 15 Minutes) Spend the final 15 minutes on three things: celebrate the group, recognize top performers without diminishing everyone else, and point people to what's next. Roughly 5 minutes each. {% hint style="info" %} Everyone who participated tackled real cybersecurity challenges. Celebrate that, regardless of how far they got. {% endhint %} ### Give a Time Warning About 10 to 15 minutes before the end: ``` About 10 minutes left. Finish what you're working on and submit any final answers. If you didn't finish everything, that's normal. Your progress is saved, and most people keep investigating after the event. ``` ### Celebrate the Group, Then the Winners Recognize the whole group before announcing standings. Specific observations land harder than generic praise ("Someone found a clever approach to Challenge 7"). {% tabs %} {% tab title="Individual events" %} Announce the top 3 to 5 with scores. Add context like "these scores represent completing X out of Y challenges." {% endtab %} {% tab title="Team events" %} Announce top teams. Call out collaboration and how teams used different strengths. {% endtab %} {% endtabs %} Frame winning as "went the furthest today," not "were the best." For the full closing script, see [Templates and materials](/hosting-events/event-resources/templates#host-scripts). ### Point Everyone Forward Their account saves progress, so they can keep playing "A Scandal in Valdoria," try other modules, or sign up at [kc7cyber.com](https://kc7cyber.com). Point students to clubs and competitions, professionals to certifications. ### Gather Feedback Before They Leave ``` Take 2 minutes for our participant survey. Your feedback shapes what we do next. ``` Share it by link, QR code, or chat. In person, close out logistics: stick around 10 to 15 minutes for questions and offer group photos. ## After the Event ### The Required Minimum **Within 24 to 48 hours:** 1. Email participants the final scoreboard and a thank-you. Use the [follow-up template](/hosting-events/event-resources/templates#follow-up-email-post-event). 2. Thank volunteers, co-hosts, and anyone who helped. 3. Confirm participants can still access the game. **Within one week:** 4. Fill out the [KC7 post-event survey](https://forms.gle/uvW9wd7AyEN1Hzce6) so KC7 can issue digital badges. 5. Open your dashboard and review results. That's a complete close. Everything below is optional. ### Optional Follow-Up Worth doing if you plan to host again or want to build a community.
Collect feedback and testimonials Send a 3 to 5 minute survey ([template](/hosting-events/event-resources/templates#participant-feedback-survey)) and reach out to engaged participants for testimonials while enthusiasm is high. Ask permission before quoting anyone.
Review your analytics Pull completion rates, hardest questions, and drop-off points from your dashboard. See [Track performance](https://docs.kc7cyber.com/dashboard/analytics). Use it to tune difficulty and timing next time.
Build a community and plan the next event Set up a space (Discord, Slack, email list) and share updates. Only add people who opt in. Create your next game anytime from your dashboard, no approval needed. See [Manage games](https://docs.kc7cyber.com/dashboard/managing-games).
Report to stakeholders For sponsors and leadership, share attendance, feedback highlights, learning outcomes, and photos. For the KC7 Foundation, the post-event survey triggers participant badges and opens up follow-on support.
## Your Dashboard Stays Active Your KC7 dashboard doesn't expire. Event data and analytics stay accessible, you can create new games anytime, and participants can keep playing. Some hosts run dozens of events, others run one. Both are fine. See [Your dashboard](https://docs.kc7cyber.com/dashboard/overview). ## Common Questions * **Did my event go well?** If participants stayed engaged and left positive, yes. Engagement matters more than completion rate. * **What if people didn't finish?** Expected. The learning happens during the investigation, wherever someone stops. * **Should I run another event?** Only if you want to. Your dashboard stays active, so you can return whenever. ## Next Steps
Use post-event templatesThank-you emails and surveys./pages/r5fZ8fEkcHmibVDbjpes
Run another eventPlan a fresh one./pages/bLt2rpHLN821qozI6OV0
Your dashboardReview results, add games.https://docs.kc7cyber.com/dashboard/overview
# Game Module Catalog Browse KC7 game modules and choose one that fits your audience A reference of KC7 game modules. Use this to pick scenarios for current and future events. For your first event, you'll start with "A Scandal in Valdoria." It's the default for every new dashboard. After your first event, you can add more modules through your dashboard. ## Featured Module: A Scandal in Valdoria The default module for all first-time events. | Attribute | Value | | ------------- | ---------------------------- | | Duration | About 90 minutes, self-paced | | Difficulty | Beginner | | Players | Unlimited | | Prerequisites | None | **Scenario.** The Kingdom of Valdoria faces a mysterious cybersecurity incident. As digital investigators, participants analyze logs, track suspicious activity, and uncover what happened. **Skills developed.** Log file analysis, pattern recognition, critical thinking, basic threat hunting, data correlation. **Best fit.** First-time KC7 events, mixed-skill audiences, intro to cybersecurity, team-building exercises. ## Module Categories Modules are tagged by difficulty so you can match audience to content. | Category | Audience | Notes | | ------------ | -------------------------- | -------------------- | | Beginner | No prerequisites | Concept introduction | | Intermediate | Some technical familiarity | Builds on basics | | Advanced | Experienced practitioners | Real depth | | Specialized | Industry or topic-specific | Tailored scenarios | ## Pick by Audience | Audience | Suggested starting point | | ------------------------------- | ------------------------------------------------------------------------ | | Complete beginners | A Scandal in Valdoria | | Middle and high school students | A Scandal in Valdoria, then age-appropriate modules in your dashboard | | College students | Foundational modules, progress to intermediate | | Working professionals | Match the team's experience, advanced for seasoned IT and security staff | ## How Modules Work Every module follows the same flow. 1. **Briefing.** Participants get the scenario and context. 2. **Investigation.** They analyze data, logs, and evidence. 3. **Discovery.** They uncover clues and piece together the story. 4. **Resolution.** They submit findings and earn points. 5. **Debrief.** They review solutions and learning outcomes. ### Scoring * Points for correct answers * Bonus points for speed * Partial credit for incomplete solutions * Team leaderboard for competition ### Completion Modules are self-paced. There's no requirement to finish. Learning happens throughout. Digital badges are awarded on completion. ## Add More Modules to Your Dashboard After your first event: 1. Log into your dashboard. 2. Navigate to your classroom. 3. Click **Add Game**. 4. Browse available modules. 5. Select based on your audience. For detail, see [Manage games](https://docs.kc7cyber.com/dashboard/managing-games). ## Pick by Time Available | Available time | Suggested difficulty | | -------------- | ---------------------------- | | 90 minutes | Beginner | | 3 to 4 hours | Intermediate | | Full day | Advanced or multiple modules | ## Module FAQ
Can participants retry modules? Yes. They can replay to improve scores or try different approaches.
Are solution guides provided? Yes. After events, hosts can access solution guides to help with debriefs.
Can we customize modules? Core modules have fixed content, but you can supplement with your own materials.
How often are new modules added? KC7 releases new content regularly. Check your dashboard for updates.
## Need Help Selecting? * Review module descriptions in your dashboard * Ask in the [KC7 Discord](https://docs.kc7cyber.com/community/getting-help) * Email space.vars.support\_email Start with "A Scandal in Valdoria" for your first event. # Templates and Materials Copy-and-customize templates for emails, scripts, checklists, and feedback Reference templates for invitations, day-of materials, host scripts, checklists, and follow-ups. Copy, customize, and use. ## Jump to a Section
📧 Email templatesInvitation, reminder, follow-up#email-templates
📣 Announcement templatesSocial, newsletter, organization-wide#announcement-templates
🗂️ Event materialsSign-in sheet, quick reference, certificate#event-materials
🎤 Host scriptsOpening, mid-event, closing wording#host-scripts
✅ Planning checklistTwo weeks out through day-of#planning-checklist
📝 Feedback formsParticipant survey, host self-eval#feedback-forms
## Email Templates
Invitation email (pre-event) Send when announcing the event to your invitee list. **Subject: You're invited to the \[Event Name] cybersecurity challenge** ``` Dear [Participant Name], You're invited to a cybersecurity challenge using KC7, a gamified platform for learning real investigation skills. - Date: [Date] | Time: [Start - End] - Location: [Physical location or "Virtual, link to follow"] - Duration: about [90 minutes / 3 hours / etc.] You'll investigate a cybersecurity incident in a fictional kingdom. No technical experience required. Bring a laptop with a modern browser (Chrome, Firefox, Safari, or Edge). RSVP by [Date]. Questions? Contact [Your Name] at [Your Email]. ```
Participant instructions (day before) Send the day before the event with the link and prep steps. **Subject: Tomorrow's KC7 event, here's everything you need** ``` Hi everyone, Quick note ahead of tomorrow's KC7 cybersecurity challenge. Game link: [Go Link] Start time: [Time] Location: [Location or virtual platform] Before tomorrow: 1. Open the game link to make sure it loads. 2. Create your KC7 account if you haven't. 3. Update your browser if needed. 4. Charge your laptop if attending in person. During the event: - Brief introduction - About [time] to work through the challenge - Individual or teams of [number] - Ask questions anytime [Your Name] ```
Follow-up email (post-event) Send within 24 hours of the event with results and next steps. **Subject: Thanks for participating in \[Event Name]** ``` Congratulations on completing the KC7 cybersecurity challenge. Final scoreboard: [Link or attached] Your progress is saved. Keep investigating at kc7cyber.com. Share your experience: [Feedback form link] [Your Name] ```
## Announcement Templates
Social media post Use on LinkedIn, X, Instagram, or Facebook to attract sign-ups. ``` 🔍 Join us for a KC7 cybersecurity challenge. Learn real investigation skills through an interactive game. No experience needed. 📅 [Date] ⏰ [Time] 📍 [Location] 🎮 Free to participate Register: [Link] #Cybersecurity #KC7 #Learning #TechEducation #CyberChallenge ```
Newsletter blurb Drop into a school, company, or community newsletter. ``` Upcoming: KC7 cybersecurity gaming event Join us for an interactive KC7 competition where you'll investigate a security incident in the Kingdom of Valdoria. Beginner-friendly. No technical experience required. Prizes for top performers. [Register] [Learn more] ```
## Event Materials
Participant sign-in sheet Print and bring to in-person events. ``` KC7 event: [Event Name] Date: _________ Location: _________ Name | Email | Organization | KC7 Username -----+-------+--------------+-------------- | | | | | | | | | ```
Quick reference card (print for participants) Hand out so participants have the link and tips at their seat. ``` KC7 quick start Game link: [Go Link] Event code: [Code] Getting started 1. Go to the game link. 2. Create an account or log in. 3. Read the scenario briefing. 4. Start investigating. Tips - Read carefully, details matter. - Take notes as you investigate. - Look for patterns in the data. - Ask for hints if stuck. Need help? - Raise your hand in person. - Use chat for virtual events. - Ask your neighbor. ```
Certificate template Fill in and print for participants who complete the challenge. ``` Certificate of completion This certifies that [Participant Name] has completed the KC7 cybersecurity challenge "A Scandal in Valdoria" Demonstrating skills in: - Digital investigation - Log analysis - Critical thinking - Cyber threat detection Date: _________ Event: _________ Host: _________ ```
## Host Scripts
Opening remarks (5 minutes) Read or paraphrase at the start of the event. ``` Welcome to our KC7 cybersecurity challenge. Today, you'll become cyber detectives investigating a security incident in the Kingdom of Valdoria. If you've never done anything like this before, that's fine. The game guides you through it. You'll analyze evidence, look for patterns, and piece together what happened. Like solving a digital mystery. The game runs about 90 minutes. Don't stress about finishing. Focus on learning and having fun. There's a live scoreboard if you want to compete, but everyone learns at their own pace. Your game link is [show or share]. Once you create your account and log in, you can begin. If you get stuck, raise your hand or use chat and I'll help. Any questions before we start? ```
Mid-event encouragement (30 to 45 minutes in) Use about a third of the way through to re-energize the room. ``` Nice progress on the scoreboard. Reminders: - There's no single path through the investigation. - If you're stuck, try approaching the problem differently. - Collaboration is allowed if you want to work with neighbors. - Points are a bonus. Learning is the goal. Keep going. ```
Closing remarks Read at the wrap-up. For the full closing flow, see [Close your event](/hosting-events/after-the-event/after). ``` Congratulations on completing your first cybersecurity investigation. Whether you finished or not, you practiced real skills that professionals use every day. [Share final scoreboard] [Announce winners if applicable] Your progress is saved. Keep going at kc7cyber.com. Thank you. ```
## Planning Checklist For the full timeline with links to each step, see the [prep timeline](/hosting-events/planning/planning#full-prep-timeline). ## Feedback Forms
Participant feedback survey Send after the event to gather participant input. ``` 1. How would you rate your overall experience? (1-5) 2. Was the difficulty level appropriate? [ ] Too easy [ ] Just right [ ] Too hard 3. What did you learn from this event? [Open response] 4. Would you participate in another KC7 event? [ ] Yes [ ] No [ ] Maybe 5. Would you recommend this to others? [ ] Yes [ ] No [ ] Maybe 6. What could we improve? [Open response] 7. Any other comments? [Open response] ```
Host self-evaluation Fill out within a day or two of the event to capture lessons. ``` Event metrics - Registered participants: ___ - Actual attendance: ___ - Completion rate: ___ % - Average score: ___ What went well: _________________ Challenges: _________________ Improvements for next time: _________________ Would I host again? [ ] Yes [ ] No Why? _________________ ```
# FAQs Common questions about hosting KC7 events and using your dashboard Quick answers to questions hosts ask most, about events and about the dashboard. For deeper guidance, follow the link on each topic. ## Getting Started
Do I need cybersecurity expertise to host? No. KC7 handles the technical instruction so you can focus on facilitation. See [What is a KC7 event?](/hosting-events/getting-started/what-is-kc7) for the host role and [Support participants](/hosting-events/running-your-event/supporting-participants) for how to coach without expertise.
How long does approval take? Most requests are approved within 1 to 2 days. See the [quick start](/hosting-events/getting-started/quick-start).
Can I run KC7 in my classroom or as part of a course? Yes. Use it during class, assign it as homework, or run it as enrichment. Your dashboard supports multiple sessions over a semester. See [Manage games](https://docs.kc7cyber.com/dashboard/managing-games) and [Organize classrooms](https://docs.kc7cyber.com/dashboard/classrooms).
## About the Experience
How long does a typical event take? "A Scandal in Valdoria" runs about 60 to 90 minutes self-paced. Plan 2 hours total to allow for intro, investigation, and wrap-up. See [Pick a format](/hosting-events/planning/planning#pick-a-format).
Do participants need technical knowledge? No. Modules are designed for complete beginners. If they can use a web browser, they can play. See [What is a KC7 event?](/hosting-events/getting-started/what-is-kc7).
How do participants sign up and join? No advance signup needed. Share the Go Link from your approval email. Participants can create a full account (recommended, saves progress) or play as a guest. See [Set up before the event](/hosting-events/running-your-event/pre-event-setup).
## During Your Event
How do I monitor what participants are doing? Use the live scoreboard for real-time rankings and the analytics page for challenge difficulty and success rates. You see progress and scores, not individual answers. See [Run event day](/hosting-events/running-your-event/event-day) and [Track performance](https://docs.kc7cyber.com/dashboard/analytics).
What if participants get stuck? Direct them to the in-game hint system first. For coaching strategies that don't spoil answers, see [Support participants](/hosting-events/running-your-event/supporting-participants).
Can participants work in teams? Yes. Each person needs their own account for individual progress, but pairs and small groups often learn better. Each person submits their own answers.
## Expanding Your Program
Is KC7 suitable for experienced professionals? Yes. "A Scandal in Valdoria" is for beginners, but more advanced modules challenge experienced IT and security professionals. See [Game module catalog](/hosting-events/event-resources/game-modules).
Can I run additional events after my first one? Yes. Your dashboard lets you add more games and create new classrooms without re-applying. See [Manage games](https://docs.kc7cyber.com/dashboard/managing-games).
What are the dashboard capacity limits? New dashboards start on the free Community plan, and every plan includes the full module library. Plans differ in capacity (seats and classrooms), and yours is shown in your dashboard under Settings & plan. See [plan capacity](https://docs.kc7cyber.com/dashboard/overview#plan-capacity). To upgrade: space.vars.upgrade\_with\_waiver
## After Your Event
What happens when my event ends? Participants keep access. You can view scores and analytics anytime. See [Wrap up after your event](/hosting-events/after-the-event/after).
How do I get help if I run into issues? For technical problems, see [Troubleshoot common issues](/hosting-events/event-resources/troubleshooting). For real-time help, see the [Discord community](https://docs.kc7cyber.com/community/getting-help). For account questions, email space.vars.support\_email.
How can I support KC7 after my event? Spread the word with #KC7Cyber, present at conferences or meetups, gift KC7 swag from the [KC7 Swag Shop](https://kc7.printful.me/), [donate to KC7](https://givebutter.com/kc7), or mentor new hosts in Discord.
## Your Dashboard
What is a dashboard? What is a tenant? Both names refer to the same thing: your organization's account on KC7. It holds your classrooms, games, participants, and analytics. See [Your KC7 dashboard](https://docs.kc7cyber.com/dashboard/overview).
What's the difference between a classroom and a game? A classroom is an organizational container. A game is one playable instance of a module inside a classroom. See [how your dashboard is structured](https://docs.kc7cyber.com/dashboard/overview#how-your-dashboard-is-structured).
Should I create a new classroom for each event? No. One classroom can hold many games. Create a new classroom when you want to keep distinct groups apart, like "Fall 2026" and "Spring 2027." See [Organize classrooms](https://docs.kc7cyber.com/dashboard/classrooms).
What does the "Visible to students" toggle do, and should I use it? When it's on, students see the game in their classroom and are registered in it automatically. Turn it on when everyone should play; leave it off to stage a game quietly and reveal it later. See [Manage games](https://docs.kc7cyber.com/dashboard/managing-games#join-and-access).
Can participants see each other's answers? No. Participants see only their own progress. Leaderboards (when enabled) show rankings without exposing answers.
How long is data kept, and can I export it? Indefinitely, and everything stays readable in your dashboard's analytics, so last term's numbers don't expire. Standings export to CSV, Excel, or PDF from the game's scoreboard. See [export data](https://docs.kc7cyber.com/dashboard/analytics#export-data).
Can KC7 integrate with my LMS? Some integrations exist. Email space.vars.support\_email with your LMS and use case.
Participants can't access the game. What do I check? The game link and its code, whether the game is visible to students, its scheduled open and close times, and classroom membership. See [common issues](https://docs.kc7cyber.com/dashboard/managing-games#common-issues).
## Still Have Questions? For real-time help, see the [Discord community](https://docs.kc7cyber.com/community/getting-help). Or browse: * [Quick start guide](/hosting-events/getting-started/quick-start) * [Plan your event](/hosting-events/planning/planning) * [Technical requirements](/hosting-events/planning/technical-requirements) * [Troubleshoot common issues](/hosting-events/event-resources/troubleshooting) # Troubleshoot Common Issues Fix common technical issues during a KC7 event Most KC7 issues have simple fixes, and the usual suspects are a wrong link, a stale browser cache, or a network filter. This page is organized by when problems show up so you can jump straight to a fix. ## Quick Fixes During an Event ### Participant Can't Access the Game 1. Confirm they're using the Go Link, not the intro link. 2. Try incognito mode to bypass cache and extensions. 3. Switch browsers, for example Chrome to Firefox. 4. Try a different network or a mobile hotspot if the institutional network is blocking. ### Game Won't Load 1. Hard refresh with `Ctrl+F5` or `Cmd+Shift+R`. 2. Clear the browser cache. 3. Disable ad blockers. 4. Confirm the internet connection. ### Lost Progress 1. Confirm the participant is logged into their account, not playing as a guest. 2. Verify they're using the correct game link. 3. Email with the username and game code if progress doesn't return. ## Pre-Event Issues ### Approval Email Hasn't Arrived After 72 Hours * Check spam and junk. * Verify the email address on the request. * Resubmit at [kc7cyber.com/gameon](https://kc7cyber.com/gameon). * Email with your request details. ### Intro Page Shows an Error * Verify the exact URL from the approval email. * Confirm you're not using the participant Go Link by mistake. * Check for extra characters in the URL. * Try a different browser. ### Network Blocks KC7 * Request that IT whitelist `*.kc7cyber.com`. * Provide an educational justification. * Use a guest network if available. * Plan mobile hotspots as backup. ## During-Event Issues ### Participants Can't Join | Symptom | Fix | | ---------------- | ----------------------------------------------------------------------------------------------- | | "Game not found" | Confirm the Go Link, check for typos, copy-paste from email | | "Access denied" | Verify the game date matches today, confirm the participant limit isn't exceeded, clear cookies | | Login problems | New users create an account first, existing users try password reset, fall back to guest | ### Performance Issues **Slow for one participant.** Close extra tabs, check for at least 3 Mbps, switch to wired, disable video in the call. **Slow across the room.** Stagger participant starts, check venue bandwidth, reduce concurrent users, switch to backup network. **Pages stop responding.** Hard refresh (`Ctrl+Shift+R`), clear the last hour of browser data, try a different browser, confirm JavaScript is enabled. ### Scoring or Progress * **Points not updating.** The scoreboard refreshes every 30 seconds. Refresh the page, confirm the answer was submitted, look for the green checkmark. * **Lost progress mid-game.** Progress auto-saves. Have them log back in with the same account. Note the username if you need support. * **Wrong team or individual setting.** Contact host immediately. Fixable in the dashboard. ## Post-Event Issues ### Can't Access Results * Results stay available indefinitely in your dashboard. * Badges only award on full completion. Partial progress doesn't count. ### Participant Wants to Keep Playing Games stay open after the event. Reshare the Go Link and progress continues to save. To offer a different module, add a new game in your dashboard and share the new Go Link. ## Browser-Specific Fixes | Browser | Symptom | Fix | | ------- | ---------------------------- | --------------------------------------------------------------------------------------- | | Chrome | "This site can't be reached" | Clear DNS at `chrome://net-internals/#dns`, disable QUIC, reset Chrome settings | | Firefox | "Secure connection failed" | Check date and time, clear cookies for kc7cyber.com, disable strict tracking protection | | Safari | Page formatting broken | Enable JavaScript, disable content blockers, update to the latest version | | Edge | Compatibility problems | Switch to Chrome compatibility mode, clear browsing data, check enterprise policies | ## Institution-Specific Issues ### School Networks * **Chromebook restrictions.** Work with IT for a policy exception, use guest mode if allowed, try teacher override codes. * **Content filter blocking.** Request approval under educational gaming, ask for a domain whitelist, or get a time-based exception for the event window. ### Corporate Networks * **VPN interference.** Disconnect VPN if possible, use split tunneling, or fall back to personal devices. * **Proxy issues.** Configure browser proxy settings, add a proxy bypass for KC7, or use a direct connection. ## Virtual Event Issues * **Screen sharing.** Share a specific browser tab rather than the whole screen, check platform permissions, have a co-host ready as backup presenter. * **Audio echo.** Mute when not speaking, use headphones, adjust audio settings, consider push-to-talk. * **Participants can't see the game.** Confirm you're sharing the right window, drop the Go Link in chat so they can play independently. ## Dashboard Issues * **Can't add new games.** Check your role permissions, verify a classroom is selected, clear browser cache, try a different browser. * **User management problems.** Bulk operations may take time. Confirm email addresses are valid, verify role permissions, export and import as a backup. * **Data export failing.** Reduce the date range, export smaller groups, try a different format, check browser download settings. ## When All Else Fails ### Get Help Fast 1. **Discord (fastest).** [KC7 Discord](https://docs.kc7cyber.com/community/getting-help) for real-time help from the community. 2. **Email support.** . Include the event code, issue description, and screenshots. Response within 24 to 48 hours. 3. **Backup activity.** Have an offline cybersecurity activity ready (discussion questions, video walkthrough, makeup session). ### Information to Send to Support * Event or game code * Number of affected participants * Browser and version * Exact error messages * Screenshots if possible * What you've already tried ## Prevent Issues Before They Happen **One week before.** Run a full test with real accounts, check network requirements, verify links work, line up IT support on standby. **Day before.** Send a reminder with the correct link, test from a participant's perspective, prepare a troubleshooting handout, charge devices. **Day of.** Arrive 30 minutes early, retest everything, keep your backup plan and support contacts handy. ## Tips from Experienced Hosts * Always have a backup plan in case internet fails. * Test with actual participants, not just your own account. * Document issues and solutions to build your own playbook. * Stay calm during problems. Participants follow your lead. * Treat troubleshooting as part of the cybersecurity lesson. # Your Dashboard Manage games, classrooms, users, and analytics from 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. Start with the overview if the pieces are new to you, or jump straight to the task you came for.
OverviewWhat your dashboard is and how it's structured./pages/P8PuN9KvzQlhMng8gT52
Open Your DashboardFirst-time walkthrough./pages/MDgMJtytdSYfY0bg3ZIJ
Manage GamesCreate games and get participants in./pages/vMNJXpH4LWjV8Xoc8VLC
# Your KC7 Dashboard What your KC7 dashboard is, how it's structured, and how it relates to your events. 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#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
# Open Your Dashboard Open your dashboard for the first time and learn your way around the screen. 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). ## 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
Do I need to do anything in the dashboard before my first event? No. Your game is set up. Check the link works, share it, and come back for results afterward.
Where do I find my game link? In your approval email, or on the game's card in your classroom's Games tab, as `kc7cyber.com/go/[code]`.
Can I add participants before the event? 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.
What if I delete something by accident? Deletion is permanent, which is why it lives in each classroom's Danger Zone. Email space.vars.support\_email if you need help, and prefer unlinking games over deleting them when in doubt.
Do I need a new classroom for each event? No. One classroom holds many games. Create new classrooms when you want to keep distinct groups apart, like "Fall 2026" and "Spring 2027."
How do I give someone else access? 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).
## Next Steps * [Add another game or a career path](/dashboard/managing-games) * [Organize classrooms](/dashboard/classrooms) * [Invite students and co-managers](/dashboard/managing-users) * [Track performance](/dashboard/analytics) # Manage Games Add games and career paths to a classroom, control what students see, and manage each game's access code and roster. 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#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) * [Add students and managers](/dashboard/managing-users) * [Track game analytics](/dashboard/analytics) # Organize Classrooms Create, customize, and organize classrooms inside your dashboard. Classrooms group games and students inside your dashboard. Use them to separate courses, cohorts, workshop groups, or terms. Each classroom has its own games, roster, leaderboard, and settings. Every dashboard starts with a default classroom named **My First Classroom**. You can rename it to anything in its settings, and many organizations run happily on that single classroom for a long time. ## The Classroom Screen Open a classroom from the **Classes** section of the sidebar. Every classroom has the same five tabs, with a **Join link** button and an **Add game** button always available in the header. | Tab | What it holds | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Home** | The at-a-glance view: quick actions, stat tiles (students, games assigned, average completion, needs attention), and a list of students who've gone idle. | | **Games** | Every game assigned to this classroom, with visibility controls and per-game join codes. Covered in [Manage Games](/dashboard/managing-games). | | **Roster** | The progress matrix (every student crossed with every game) plus the tools for adding students. | | **Leaderboard** | Students ranked by points across the classroom's games. | | **Settings** | Name, description, enrollment controls, classroom managers, and deletion. | ## Create a Classroom Two paths to the same place: * In the sidebar, click **New class** under your classroom list. * Or open your dashboard's **Classrooms** tab and click **Add Classroom**. This tab also lists every classroom with its game and student counts, and it's where you manage the full set as you grow. Give it a name and an optional description, and you'll land in the new classroom ready to add games. ## Classroom Settings The **Settings** tab has four sections. **Details.** The classroom's name, description, and an optional thumbnail image. This is also home to the **invite-only enrollment** toggle: when it's on, only people you invite by email can join, and the shareable join link, self-registration, and guest accounts are all blocked for anyone you haven't invited. Turn it on for closed cohorts where you control the exact roster; leave it off for open workshops where a shared link is the point. Click **Update** to save changes. **Classroom Managers.** Give someone admin access to this classroom without giving them your whole dashboard. Good for co-teachers and volunteer helpers. Roles are covered in [Manage Users](/dashboard/managing-users). **Tenant Info.** A reference card for the dashboard this classroom belongs to. **Danger Zone.** Deletion lives here, deliberately out of the way. {% hint style="danger" %} Deleting a classroom is permanent. Export anything you need from its analytics first. {% endhint %} ## Get Students In The **Roster** tab has an **Add students** panel with three methods: invite by email (paste addresses, send invites, and track them under pending invitations), share the join link, or add people who already have accounts in your dashboard. The full walkthrough, including advanced management for removing students and bulk password resets, is in [Manage Users](/dashboard/managing-users). ## Watch the Room The **Home** tab tells you how the classroom is doing without any digging: student count, games assigned, average completion, and a **Needs attention** list of students who've gone idle, with how long they've been away. The **Roster** tab goes deeper with the progress matrix: every student crossed with every game, each cell colored by progress (complete, on track, started, just began, not started, stuck) with week-over-week movement indicators. Every cell is clickable, jumping to that student's per-challenge drilldown or letting you assign a game on the spot. For analytics across your whole organization, see [Track Performance](/dashboard/analytics). ## When to Split Into Multiple Classrooms One classroom is right until it isn't. Common reasons to split: | Strategy | Example layout | Best for | | -------------- | -------------------------- | ----------------------------- | | By time period | Fall 2026, Spring 2027 | Schools and seasonal programs | | By audience | Beginner, Advanced | Multi-level training | | By group | Engineering, Sales | Corporate training | | By format | Weekly course, Competition | Mixed-format programs | Whatever you pick, use names that will still make sense when you have ten of them. "2026 Fall - Intro to Cybersecurity" ages better than "My Class." ## Troubleshooting **Students can't join.** Check whether invite-only enrollment is on (it blocks the join link for anyone not invited by email), and confirm you shared the current classroom join link. **A manager can't see the classroom.** Confirm they're assigned under Settings, Classroom Managers, and that they're looking at the right classroom. Have them log out and back in if a fresh assignment isn't showing. **Wrong people joined.** The join link traveled further than intended. Remove them via the roster's advanced management, and consider invite-only enrollment for the rest of the term. ## Next Steps * [Add games to a classroom](/dashboard/managing-games) * [Add students and co-hosts](/dashboard/managing-users) * [Review progress and analytics](/dashboard/analytics) # Manage Users Add students, classroom managers, and administrators, and control the policies that shape accounts in your dashboard. Three kinds of people live in your dashboard: **students** who play, **classroom managers** who run individual classrooms, and **administrators** who run the whole organization. Each is added in a different place, which this page walks through. ## Roles and Permissions * **Administrator.** Full control of the dashboard: every classroom, game, student, setting, and the plan. You became one automatically when your dashboard was created. Administrators are managed in the dashboard's **Settings** tab. * **Classroom Manager.** Admin powers inside assigned classrooms only, granted from each classroom's own settings. The right role for co-teachers and helpers who should run their room without seeing the rest of the organization. * **Student.** Joins classrooms, plays games, and appears on rosters and leaderboards. ## The Students Tab Your dashboard's **Students** tab lists everyone across all classrooms: username, email, account type, and registration date, with search and sorting for larger organizations. Classroom rosters are per-classroom views of this same population. ## Managed and Unmanaged Accounts The account type column reflects the **Managed Accounts** policy. Ordinary students own their accounts and show as **Unmanaged**. If you turn on Managed Accounts (in **Settings**, under Policies), accounts created through your dashboard's portal from then on are managed by your administrators instead, which some schools and youth programs prefer. ## Add Students Students join through a classroom, and the classroom's **Roster** tab holds all three doors: * **Invite by email.** Paste addresses (one per line or comma-separated) and send. Invitations you've sent wait under **Pending invitations**. * **Join link.** Share the classroom's link and students enroll themselves. A classroom with [invite-only enrollment](/dashboard/classrooms#classroom-settings) turned on blocks this door for anyone you haven't invited. * **Add existing.** Enroll people who already have accounts in your dashboard. Once in the classroom, students are registered automatically into every game that's visible to them; see [Join and Access](/dashboard/managing-games#join-and-access) for how game access works. For removals, bulk password resets, and guest accounts, follow the **Open advanced management** link at the bottom of the Roster tab. ## Add an Administrator In your dashboard's **Settings** tab, open **Administrators**. Type a username or email to search for an existing account, or paste a full email address and press Enter to invite someone who doesn't have an account yet. Their invitation sits under Pending Invitations until they accept, and the ✗ next to any listed administrator removes their access. Grant this role sparingly. An administrator can do everything you can, so most organizations need only a small handful. ## Add a Classroom Manager Open the classroom, go to its **Settings** tab, and choose **Classroom Managers**. Managers you add there get admin access to that classroom and nothing else. Assign the same person in several classrooms if their job spans them. ## Policies That Shape Accounts Your dashboard's **Settings** tab has a **Policies** section with four toggles that apply to all users created through your dashboard. Changes save automatically. | Policy | When it's on | | ---------------------- | ------------------------------------------------------------------------------------- | | **Show User Profiles** | Accounts created through your dashboard have visible user profiles. | | **Show Leaderboard** | Your users appear on KC7's global leaderboard, beyond your own organization's boards. | | **Show Help Links** | Help and support links (like Discord) are visible to users inside your dashboard. | | **Managed Accounts** | New accounts created through your portal are managed by your administrators. | Schools running younger students often turn the first two off and the last one on; adult programs usually leave the defaults. ## Transfer Ownership Add the new owner as an administrator, and once they've accepted, they can remove your access. For formal documentation of a handover, email space.vars.support\_email. ## Common Issues **An invited administrator can't get in.** Check Pending Invitations in Settings; the invite has to be accepted from their email before access exists. **A student joined the wrong classroom.** Remove them through the roster's advanced management, then send them the right classroom's join link. **A student shouldn't appear on the global leaderboard.** Turn off the **Show Leaderboard** policy, which controls global visibility for accounts created through your dashboard. ## Next Steps * [Organize classrooms](/dashboard/classrooms) * [Manage games and access](/dashboard/managing-games) * [Track performance](/dashboard/analytics) # Track Performance Read progress and performance at the organization, classroom, game, and question level. 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 space.vars.support\_email. ## 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) * [Manage users](/dashboard/managing-users) * [Organize classrooms](/dashboard/classrooms) # Community Get help with KC7 and get involved with the community. Help when you need it, and ways to give back when you're ready.
Get HelpDiscord, email, and troubleshooting, by speed and topic./pages/gzxaikpCoqOoeUNDyLIl
Volunteer with KC7Contribute to content, scenarios, or community./pages/SPHi4v4AMxM9ReDcmYEi
# Get Help Where to ask for help with KC7, by speed and topic. Pick the channel that matches your question. ## Discord (Fastest for General Questions) The KC7 Discord is the fastest way to reach hosts and staff. Use it for general questions, "is anyone else seeing this?", and quick troubleshooting. Join the KC7 Discord You'll find help from hosts who've run the same module, technical support from KC7 staff, stories from other events, and announcements about new modules and platform changes. ## Email Support (Account-Specific Issues) Write to [**events@kc7cyber.com**](mailto:events@kc7cyber.com) for anything tied to your account, your event approval, or a technical problem you can't resolve from the docs. Use email for: * Account and dashboard questions * Event approval status * Technical issues and bug reports * Billing questions Expect a reply within 24 to 48 hours on business days. ## Search the Docs Most common questions are already answered: * [FAQs](https://docs.kc7cyber.com/hosting-events/faq) * [Troubleshooting guide](https://docs.kc7cyber.com/hosting-events/troubleshooting) ## Share Feedback and Contribute Host feedback shapes the modules, the platform, and these docs. Tell us what worked, what didn't, and what you'd like to see next. * Post in the [KC7 Discord](https://kc7cyber.com/community) for quick questions and informal feedback. * Email for bug reports, account issues, or longer suggestions. When reporting a bug, include the game name, what you expected, what happened, and a screenshot if you have one. ### Help Other Hosts * Answer questions in Discord when you can. Hosts learn fastest from other hosts. * Share what worked at your event: photos, attendance, format, what you'd change. * Tell people about KC7 if it fit your group. ### Contribute to the Project Want to write modules, build scenarios, or moderate the community? See [Volunteer with KC7](/community/volunteer). # Volunteer with KC7 Contribute to KC7 through content, scenario design, operations, or community moderation. KC7 has been built by volunteers from day one. If you want to contribute real work to a cybersecurity education platform that thousands of people use, this page tells you how it works and what we expect. **Trying to break into cybersecurity?** Play KC7 first. Volunteering is the next step. It's how you build advanced skills, contribute something real, and work alongside people already in the industry. ## What KC7 Is KC7 is a cybersecurity education platform built around a detective game. Players investigate realistic cyber incidents using real data, real tools, and real analytical thinking. The platform reaches thousands of people, from students starting out to working security professionals. Volunteer-created content has been featured at **DEF CON**, **Black Hat**, and **SANS**. We're a non-profit that operates like a startup. Things move fast, we figure things out as we go, and we believe cybersecurity education should be more accessible and more fun than the industry typically makes it. ## Is This a Fit? We'd rather be honest upfront than waste your time. {% tabs %} {% tab title="A Good Fit: You..." %} * Want to break into cybersecurity and build skills past playing the game * Care about making cybersecurity education more accessible * Can commit **4 to 8 hours a month**, consistently * Communicate proactively, especially when plans slip * Are comfortable working with limited resources and figuring things out * Want real work, not a resume line * Will play KC7 to understand what you're contributing to {% endtab %} {% tab title="Not a Fit: You..." %} * Want something passive and low-expectation * Can disappear for weeks without warning * Need a lot of hand-holding to start * Are signing up for the credential, not the mission {% endtab %} {% endtabs %} {% hint style="info" %} What you get out of KC7 tracks directly with what you put in. Volunteers who engage, ask questions, and own their work come away with skills, connections, and a real portfolio. Volunteers who don't engage don't get much. {% endhint %} ## Pick a Track Volunteers contribute across four tracks. You'll be matched to one when you apply. | Track | What you'll do | | ------------------------------------ | --------------------------------------------------------------------------------- | | **Content development** | Write, review, and improve educational modules and learning materials | | **Game writing and scenario design** | Build investigation games. Storylines, clues, and realistic cyber scenarios | | **Administrative support** | Research, coordination, documentation, and the operational work behind the scenes | | **Community and Discord moderation** | Keep the KC7 community welcoming, helpful, and on-mission | ## What We Ask ### Time **4 to 8 hours per month** at minimum. How you spread those hours is up to you. We care about output and communication, not when you log on. ### A 30-day Trial Every volunteer starts with a scoped starter task matched to your track. It's a low-stakes way to confirm the fit before either of us commits further. ### Communication * Tell us upfront what you can take on, not after a missed deadline. * Reply to monthly check-ins within 5 business days. * If life gets busy, send a quick message. That's all we need. ### Four Core Expectations {% stepper %} {% step %} ## Know the Game Play KC7. The more you understand what we're building, the better your contribution. {% endstep %} {% step %} ## Communicate Honestly If you commit to something, do it. If you can't, say so early. Quiet missed commitments hurt the whole team. {% endstep %} {% step %} ## Give Real Feedback We've gotten this far by hearing hard things and acting on them. Tell us what we could do better, and help fix it. {% endstep %} {% step %} ## Treat People Well Everyone here is a volunteer. Bring empathy and respect to every interaction. {% endstep %} {% endstepper %} ## What You Get | Benefit | Details | | ------------------------------- | ----------------------------------------------------------------------------- | | 🤝 **Community access** | Direct Slack access to the KC7 team and volunteers from day one | | 🧠 **Real skill-building** | Portfolio-worthy work in cybersecurity, useful if you're early in your career | | 👕 **KC7 swag** | Sent after you complete your 30-day trial | | ✍️ **Contributor credits** | Your name on any KC7 content or game you help create | | 🌟 **LinkedIn recommendations** | Available from KC7 team members after 3+ months of consistent contribution | ## How It Works {% stepper %} {% step %} ## Apply Tell us your background, availability, and which track interests you. {% endstep %} {% step %} ## Get Matched To a track and a KC7 point of contact. {% endstep %} {% step %} ## Read and Sign The Volunteer Expectations document. {% endstep %} {% step %} ## Take Your Starter Task Scoped, clear, ready on day one. {% endstep %} {% step %} ## 30-day Check-In We talk about how it went and what comes next. {% endstep %} {% step %} ## You're In Assigned to ongoing work and part of the volunteer community. {% endstep %} {% endstepper %} ## A Few Honest Answers
What if I need a break? Pause for up to 60 days without losing your spot. Just tell us before you go quiet.
What if I want to leave? A quick heads-up is all we ask. We'll wrap up open work together.
What if you don't hear from me? After 3 weeks of silence or 3 missed check-ins, we'll reach out. If there's still no response, we'll close out your spot. You're always welcome to reapply.
## Apply If you've read this and you're still in, that's the kind of self-awareness we look for. Whether you're already in industry or just starting, there's a place here if you'll show up and do the work. {% hint style="success" %} Applications are open. We review on a rolling basis and usually respond within 1 to 2 weeks. {% endhint %} Apply to volunteer with KC7 Questions before applying? Email space.vars.volunteer\_email. ## Other Ways to Support KC7 Not ready to volunteer? You can still help. * [Join the Discord community](/community/getting-help) and connect with hosts and players * [Host a KC7 event](https://docs.kc7cyber.com/hosting-events/quick-start) to bring cybersecurity education to your group * [Donate to KC7](https://givebutter.com/kc7) to support platform development * [Shop KC7 swag](https://kc7.printful.me/) and support the project * Tell other people about KC7 *** [Back to home](https://docs.kc7cyber.com/)