Understanding Tenants
If you just finished your first event, you might be wondering: "What's this 'tenant' thing I keep seeing mentioned?" Here's the good news: you already have one. When you got approved for your first event, we gave you a complete platform for running unlimited games. You're not locked into just one event - you can build an entire cybersecurity program if you want.
What Just Happened When You Got Approved
When you requested your first event at kc7cyber.com/gameon, you probably thought you were signing up for a single game session. But behind the scenes, we did something more: we created a full organizational account called a "tenant."
Think of it like this: you asked for a classroom, and we gave you the whole school building. You can run as many classes (events) as you want, organize them however makes sense, and grow at your own pace. Some hosts stick with one event and never touch their tenant dashboard. Others discover they can build ongoing programs and start exploring the platform's full capabilities.
Neither approach is wrong. Your tenant exists whenever you're ready to use it.
What's a Tenant, Really?
Your tenant is your organization's home base in KC7. It's where you:
Run multiple events (not just one)
Organize different groups (different classes, departments, or skill levels)
Track long-term progress (see how participants improve over time)
Build your cybersecurity education program (if you choose to expand)
Good news! Your tenant is already set up with your first event ready to go. You automatically received a full KC7 tenant when your event was approved. This isn't just for one event - it's your platform for running unlimited games and building a complete cybersecurity program if you want!
The Structure (If You're Curious)
Your tenant organizes everything using a simple hierarchy:
Right now, you have one classroom with one game. That's all you need for your first event. But when you're ready to add more - maybe a second session of the same game, or trying a different module, or organizing a new group - the structure is there to support it.
π― From First Event to Full Program
Most hosts' KC7 journeys follow a natural progression:
First Event β Add More Games β Create Classrooms β Track Progress β Build Community
You don't need to plan this all out now. Many hosts run their first event with no plans to continue, then participants ask "Can we do this again?" and suddenly they're running regular sessions. The tenant grows with you as your needs change.
Starting Simple
After your first successful event, you might:
Run the same game for different groups
Try a different module
Get comfortable with the platform
Not think about "tenant management" at all
Example: Run "A Scandal in Valdoria" for three different classes, using the same basic setup each time.
What you're learning: How KC7 events work, what participants respond to, basic platform navigation
Organizing Groups
As you grow, you might create classrooms to organize:
Different skill levels (Beginner/Advanced)
Different departments or grades
Special programs or camps
Ongoing vs one-time events
Example: Create separate classrooms for "Intro to Cyber" (monthly beginners) and "Advanced Security" (quarterly experienced folks).
What you're learning: How to structure ongoing programs, participant tracking, classroom customization
Building a Program
With experience, you might:
Track student progress across semester
Run concurrent events for different groups
Delegate to co-instructors
Create learning pathways
Think strategically about skill development
Example: Full cybersecurity curriculum with progression from basics to advanced, multiple instructors, regular schedule.
What you're learning: Program management, analytics interpretation, curriculum design, team coordination
π What You Can Do With Your Tenant
Immediate Actions (After First Event)
β Add another game to your existing classroom β Invite co-hosts to help manage future events β Export results from your first event β Schedule your next event (if participants want more)
Next Level Actions (After 2-3 Events)
π Create new classrooms for different groups π Track participant progress over time π Try different difficulty modules π Build a regular schedule (weekly, monthly, quarterly)
Advanced Actions (Experienced Hosts)
π Manage multiple concurrent programs π Create learning pathways (beginner β intermediate β advanced) π Generate progress reports for stakeholders π Build a community of learners with returning participants
π Real-World Examples
High School Teacher
How they use it: Same curriculum for two class periods, plus after-school club with different focus. Three classrooms keep things organized.
Corporate Trainer
How they use it: Different audiences get different experiences. Analytics show which departments need more support.
Community Organization
How they use it: Seasonal programs with different structures. Historical data helps plan next year.
β‘ Quick Start: Your Next Steps
Based on where you are in your journey:
Just finished your first event?
Review results in your tenant dashboard
Decide if you want to run another event
If yes, schedule your next game (same or different module)
If no, that's fine - your tenant will be here if you change your mind
Ready to expand?
Create a new classroom for a different group
Explore the module catalog for different content
Set up a regular schedule if you want ongoing events
Invite co-hosts if you want help managing
Building a program?
Map out your semester/year plan
Assign co-instructors with appropriate permissions
Create progression pathways across difficulty levels
Use analytics to track long-term skill development
π Learn More
Ready to maximize your tenant's potential?
What is a Tenant?
Tenant vs Events
Dashboard Basics
Add Games
Manage Users
Track Progress

Last updated

