Phase 5: Publish

Publishing is the final phase — it makes your templatized scenario available for students to deploy. This phase covers documenting what changed, setting who can access the scenario, and flipping the visibility switch.

Note

This phase unlocks after templatizing. You must have a saved template before you can publish.

Step 1: Write a Changelog

Click Changelog in the top-right control panel to document what changed in this version.

Good changelogs help both students and collaborators:

• Students see what’s new or different in this version
• Co-builders understand what was modified and why
• Your future self remembers why changes were made

Each canvas version gets its own changelog entry, building a history of your scenario’s evolution.

Step 2: Configure Permissions

Set who can access and deploy your scenario. Permissions can be scoped to:

• Specific users — Individual Rogue Arena accounts
• Teams — Entire team groups
• Courses — Students enrolled in specific courses
• Subscription tiers — Users at certain subscription levels (Standard, Premium, Enterprise, etc.)

This gives you fine-grained control over who sees and uses your scenario.

Step 3: Make Visible

Click Make Visible in the top-right control panel to publish your scenario.

The status indicator in the control panel shows whether your build is currently visible (published) or hidden (draft). You can toggle visibility at any time — hiding a published scenario removes it from student-facing listings without deleting it.

After Publishing

Once visible, students can find and deploy your scenario from the Arena. Each deployment creates a fresh copy of your templated VMs.

Updating a Published Scenario

The workflow is iterative — you can update a published scenario at any time:

1. Make changes on the canvas (add/remove plugins, adjust params)
2. Redeploy to build from the last checkpoint with your changes
3. Verify the updated build
4. Templatize the updated build
5. Update the Changelog with what changed
6. The scenario remains visible — students deploying after the update get the new version

Each version is tracked, so you maintain a full history of changes.

Trusted Builder

To publish scenarios to the broader Rogue Arena community (beyond your own team), you need the Trusted Builder endorsement. Apply from your user profile — no prior experience is required. A Rogue Labs staff member will review your application.