> For the complete documentation index, see [llms.txt](https://docs.kc7cyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kc7cyber.com/getting-started/request-event.md).

# Request your event

This page covers how to submit your event request and what arrives in your approval email.

## Before you begin

You need a rough sense of four things. Nothing has to be final.

* An event timeframe ("mid-March" is fine)
* An expected headcount (a range works)
* Your organization name and type
* Who your participants are

{% hint style="info" %}
First-time hosts often overthink the form. The request starts a conversation. Most details get nailed down after approval.
{% endhint %}

## Submit the request

Open [kc7cyber.com/gameon](https://kc7cyber.com/gameon) and complete the form. It takes about two minutes. The form asks for:

* Your contact information
* Organization name and type
* Approximate event date
* Estimated number of participants
* A short description of your audience

No proposals, no lesson plans, no technical specifications.

## Wait for approval

Most requests come back within 1-2 days. If you need a faster turnaround for a time-sensitive event, mention that in the request and the team prioritizes it.

While you wait, sketch out the format. Decide whether you want in-person or virtual, pick a duration, and identify a venue or video platform. The [Planning guide](/planning/planning.md) covers the full sequence.

## Read your approval email

When the request is approved, an email arrives with the links you need. Save it.

### Host dashboard

The host dashboard at `kc7cyber.com/intro/XXXX` is your private control center. From here you:

* Watch the intro videos you'll show participants
* Read the host guide
* Monitor live participant progress and analytics
* Open the scoreboard
* Find troubleshooting resources

{% hint style="warning" %}
Keep the host dashboard link private. It's for you and your co-hosts, not participants.
{% endhint %}

### Participant link

The participant link at `kc7cyber.com/go/XXXX` is what your group uses. From this single link, participants:

* Create a KC7 account
* Open the scenario
* Start investigating
* Track progress on the scoreboard

Share it however you communicate with your group. Email, slide, chat, anywhere.

### Tenant dashboard

You also get a STARTER tier tenant. STARTER includes:

| Resource                       | Limit                                                          |
| ------------------------------ | -------------------------------------------------------------- |
| Classrooms                     | <code class="expression">space.vars.starter\_classrooms</code> |
| Sessions (game instances)      | <code class="expression">space.vars.starter\_sessions</code>   |
| Students across all classrooms | <code class="expression">space.vars.starter\_students</code>   |

That's enough for many events in a row. The tenant gives you room to add more games, set up classrooms for different groups, track performance over time, and add co-hosts. PROFESSIONAL and ENTERPRISE tiers exist if you outgrow STARTER. The [Tenant guide](/your-tenant/overview.md) goes deeper.

## Get ready after approval

{% stepper %}
{% step %}

### Explore your host dashboard

Open the host dashboard, watch the intro videos, and read the host guide.

**Time:** 15 minutes
{% endstep %}

{% step %}

### Test the participant experience

Use the participant link to create a test account. Walk the sign-up flow, read the opening scenario, and try a few questions.

**Time:** 15 minutes
{% endstep %}

{% step %}

### Finalize event details

Lock in the date and time, the venue or video platform, your invitation plan, and any extra logistics. The [Pre-event setup guide](/running-your-event/pre-event-setup.md) walks through this.
{% endstep %}
{% endstepper %}

## Common questions

<details>

<summary>Can I request multiple events at once?</summary>

Start with one. After your first event, you can create more games yourself from the tenant without a new request.

</details>

<details>

<summary>What if event details change after approval?</summary>

Date, count, and format changes are flexible and your links stay valid. For larger changes, email <code class="expression">space.vars.support\_email</code>.

</details>

<details>

<summary>Is there a cost?</summary>

KC7 events are free for educational and community purposes.

</details>

<details>

<summary>What if I don't know all the details yet?</summary>

Submit anyway. You work out specifics during planning.

</details>

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Run your first event</strong></td><td>The fast path from request to event.</td><td><a href="/pages/Nqy40PvdTEQISumx9CYV">/pages/Nqy40PvdTEQISumx9CYV</a></td></tr><tr><td><strong>Plan your event</strong></td><td>Walk through planning week by week.</td><td><a href="/pages/BEfCPNIZZyPgo4r5OpkS">/pages/BEfCPNIZZyPgo4r5OpkS</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kc7cyber.com/getting-started/request-event.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.