Tenant vs Events

The confusion: "I thought I was just requesting an event. Why do I keep seeing 'tenant' everywhere?" This page clears that up.

The Short Version

• Event = A single game session you run for participants

• Tenant = The platform account that lets you create and manage events

You requested an event. We gave you a tenant so you can create that event (and more if you want).

The Relationship Explained

Your Tenant
    └── Contains one or more Classrooms
            └── Each Classroom contains one or more Games
                    └── Each Game is an Event you run

When you "run an event," you're actually:

1. Using your tenant's dashboard

2. To access a classroom

3. Where you create a game

4. And share that game link with participants

5. That game session IS your event

Why This Confused You (And That's Okay)

The event request form at kc7cyber.com/gameon intentionally focuses on the simple question: "When do you want to run your event?" It doesn't bombard you with platform terminology because you don't need to understand tenants to run your first event.

But once approved, you receive access to a tenant dashboard, and suddenly you're seeing terms like "tenant," "classroom," and "game" when you thought you were just running a simple event. This can feel more complex than expected.

Here's the reassurance: you can ignore most of the tenant features and still run successful events. The platform terminology exists for people who eventually want to run multiple events or build programs, but it doesn't need to affect your first event at all.

The Evolution Most Hosts Experience

First Event

How you think about it: "I'm running a KC7 event on Friday."

What's actually happening: You're using your tenant to access the classroom that contains the game link you'll share with participants.

What you care about: The game link and event day.

After 2-3 Events

How you think about it: "I want to run another event next month."

What's actually happening: You're logging into your tenant, accessing your existing classroom, and creating a second game.

What you care about: How to add another game without requesting approval again.

After Building a Program

How you think about it: "I run monthly beginner sessions and quarterly advanced workshops."

What's actually happening: You're managing a tenant with two classrooms ("Beginners" and "Advanced"), each containing multiple games for different dates.

What you care about: Organizing groups, tracking long-term progress, managing co-instructors.

Practical Comparison

Concept	Event Perspective	Tenant Perspective
What am I doing?	Running a cybersecurity game	Managing an organizational account
Who are my users?	Participants playing the game	Everyone (participants, co-hosts, managers)
How long does it last?	One session (45 mins - 3 hours)	Indefinitely (as long as you want)
What do I share?	A game link	Access to various resources
Where do I go?	Share the GO link with participants	Log into tenant dashboard
What can I create?	One event	Unlimited classrooms and games

When to Think About Tenants vs Events

Think "Event" When You're:

• Planning event day logistics

• Inviting participants

• Running the actual game session

• Talking to participants

• Focused on the learning experience

Think "Tenant" When You're:

• Adding new games

• Creating classrooms for different groups

• Managing co-hosts or instructors

• Reviewing analytics across multiple events

• Planning your program's structure

The Documentation Reflects This Split

You might have noticed the documentation has two major sections:

🎪 Hosting an Event → Everything about event day: planning, running, supporting participants

🏢 Using the Tenant System → Everything about the platform: dashboards, users, analytics

This split exists because these are genuinely different activities:

• Hosting an event is about the human side - logistics, facilitation, participant support

• Using the tenant is about the platform side - configuration, data, management

You might be great at one and never touch the other. That's completely fine.

Common Scenarios Clarified

"I just want to run one event"

What you need to understand about tenants: Almost nothing. You'll use your game link to run the event. The tenant dashboard exists in the background.

What you should know: Your tenant preserves all your event data and lets you run another event later without requesting approval again.

"I want to run this event again for a different group"

What you need to understand about tenants: How to create a second game in your existing classroom.

What you should know: Takes about 30 seconds. Go to dashboard → classroom → add game → copy new link.

"I want to run monthly events for different audiences"

What you need to understand about tenants: Classroom organization, game settings, user management.

What you should know: Time to read the tenant documentation and learn the platform features.

Bottom Line

Event = What participants experience Tenant = What hosts use to create and manage events

You'll naturally learn more about tenant features as you need them. For your first event, you can mostly ignore the platform complexity and focus on event day. The tenant capabilities are there when you're ready to use them.

---

Next Steps

Focus on Your First Event

Plan your event day →

Explore Your Dashboard

Understand the tenant interface →

Add Another Game

Create your next event →

---

Back to Tenant Overview