> 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/running-your-event/virtual.md).
# Virtual events
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](/running-your-event/event-day.md) and [Support participants](/running-your-event/supporting-participants.md).
## 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](/planning/planning.md).
## 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 it varies by tenant.
{% 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](/running-your-event/event-day.md)). 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
---
# 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/running-your-event/virtual.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.