Invite Guests
Every lab in Rogue Arena is isolated per user by default. Your deployment belongs to you, with its own state, snapshots, and curriculum progress. When you want company, you can invite guests in.
When to Invite Guests
Section titled “When to Invite Guests”- Team red-team CTFs: run a mock red-team operation against one shared scenario, with each operator working from their own machines. It’s like running a shared C2 operation, with the whole range already stood up around you.
- Pair work and over-the-shoulder help: debug a tricky exploit together, or have a teammate watch your session live.
- Instructor support: let an instructor on your team see what’s happening in your lab and step in when you’re stuck.
- Demos and walkthroughs: show teammates your work without handing over your environment.
Opening the Share Dialog
Section titled “Opening the Share Dialog”From your deployed scenario, click the Share icon in the deployment toolbar to open Manage Scenario Sharing.
Manage Scenario Sharing, shown empty. The list shows everyone you’ve already shared with. Click Share with Teammates to add someone.
Inviting a User
Section titled “Inviting a User”Click Share with Teammates to open the Share Scenario with Teammates form. Select one or more teammates from the Team members list on the right, then choose their level of access on the left. You can only share scenarios with members of your team.
The Share Scenario with Teammates form. Select teammates on the right, set the permissions on the left, and click Share.
Permissions
Section titled “Permissions”Two permissions control what each selected teammate can do:
- Can control host/root VMs: the teammate can open and control the deployment’s host/root VMs and generate their own VPN configs. Caution: host/root VM access may expose sensitive scenario state, and a teammate with it can warp VM windows to other teammates. Grant it only when the teammate needs that access.
- Own VMs: pick up to 2 of the machines the scenario author marked User Controllable. Each selected teammate gets their own copy of those machines to work in, and everything else stays shared. Use this when each teammate needs their own machines to drive, for example in team red-team work where every operator wants their own Kali or Windows box inside the same deployment.
If you leave both off, the teammate joins your deployment but has no VMs to open.
- Curriculum progress depends on the scenario settings. By default, progress is tracked per user, so your guest’s answers don’t advance your progress and yours don’t advance theirs. If the scenario author turned on Team Collaboration, chapter unlocks are shared by everyone in the deployment, and the team progresses together.
- Teammates you share with work inside your deployment and its slot. Sharing doesn’t use another deployment slot.
- To revoke a guest, open Manage Scenario Sharing again at any time. Their access ends immediately.
- Several guests can share the same VM at once. See Operating a VM → Simultaneous viewing & control for how multiple operators work together.