Tracks & Scenarios
The Tracks & Scenarios page is your content management hub. Here you organize scenarios into learning paths and manage their lifecycle.
Accessing Tracks & Scenarios
From the Dashboard, click Tracks & Scenarios.
Page Overview
The page displays your tracks as expandable sections. Each track shows its name, scenario count, and can be expanded to reveal the scenarios inside.
Each scenario shows its status (Draft or Published) and action buttons (Open in Studio, etc.).
The toolbar at the top provides actions: Participant View, Scenarios Library, Open Studio, Import Track, and Create Track.
Header Actions
| Button | Description |
|---|---|
| Participant View | Preview how participants see your content |
| Scenarios Library | Manage all scenarios (tags, metadata) |
| Open Studio | Create a new scenario or continue editing |
| Import Track | Import a track from JSON file |
| Create Track | Create a new empty track |
Working with Tracks
Creating a Track
- Click Create Track
- Enter a name (e.g., "Kafka Fundamentals")
- Add an optional description
- Click Create
The new track appears in the list, ready for scenarios.
Track Actions
Click on a track header to expand it. Each track has these actions:
| Action | Icon | Description |
|---|---|---|
| Add Scenario | + | Add existing scenario from library |
| Import Scenario | ↑ | Import scenario from JSON or ZIP |
| Assign Users | 👥 | Select participants who can access |
| Export | ↓ | Download track as JSON |
| Edit | ✏️ | Change name, description, order |
| Delete | × | Remove track (scenarios are preserved) |
Track Settings
When editing a track:
| Setting | Description |
|---|---|
| Name | Display name |
| Description | What this track teaches |
| Order | Position in the track list |
| Default | Auto-assign to new organization members |
Default Track
Mark a track as "Default" to automatically give new members access. Great for onboarding content.
Assigning Users to Tracks
Control who can access each track:
- Click the Assign Users icon (👥)
- Check the users who should have access
- Click Assign
Only assigned users (participants) can see and run scenarios in that track.
Working with Scenarios
Adding Scenarios to a Track
From Library:
- Click + Add Scenario on the track
- Filter by tags if needed
- Select a scenario
- Click Add to Track
By Import:
- Click the import icon (↑) on the track
- Select a JSON or ZIP file
- Scenario is added to the track
Scenario Actions
Each scenario in a track has these actions:
| Action | Description |
|---|---|
| Open in Studio | Edit the scenario |
| Publish / Unpublish | Toggle visibility to participants |
| Export | Download as JSON or ZIP (with images) |
| Add to Tracks | Copy to other tracks |
| Remove from Track | Remove from this track (keeps scenario) |
| Delete | Permanently delete scenario |
Reordering Scenarios
Drag scenarios to reorder them within a track. The order determines how participants progress through the learning path.
Publishing Scenarios
| State | Visibility |
|---|---|
| Draft | Only authors can see |
| Published | Participants can run |
To publish:
- Click Publish on the scenario
- Scenario becomes available to assigned participants
To unpublish:
- Click Unpublish on a published scenario
- Participants can no longer start new runs
Active Runs
Unpublishing doesn't stop active runs. Participants currently in a lab can continue.
Scenarios Library
Click Scenarios Library to manage scenarios outside of tracks.
Library Features
| Feature | Description |
|---|---|
| Tags | Organize scenarios by topic, difficulty, etc. |
| Search | Find scenarios by name |
| Duplicate | Create a copy of a scenario |
| Export | Download as JSON or ZIP |
Managing Tags
Tags help organize your scenarios:
- Click Tags on a scenario card
- Add or remove tags
- Create new tags with custom colors
Tag Ideas:
- Difficulty:
beginner,intermediate,advanced - Technology:
kafka,postgres,kubernetes - Duration:
15min,30min,1hour
Import and Export
Exporting a Track
- Click the export icon on the track
- A JSON file downloads containing:
- Track metadata
- All scenarios in the track
- Component configurations
Importing a Track
- Click Import Track
- Select a JSON file
- If scenarios already exist, choose:
- Use existing: Link to existing scenario
- Create new: Import as new scenario
Exporting a Scenario
Two formats available:
| Format | Contents | Use Case |
|---|---|---|
| JSON | Scenario definition only | Simple sharing |
| ZIP | Scenario + instruction images | Full backup |
Importing a Scenario
- Click import icon on a track
- Select JSON or ZIP file
- Scenario is added to the track
Participant View
Click Participant View to see your content as participants do:
- Only published scenarios visible
- Only assigned tracks visible
- Run buttons instead of edit buttons
Use this to verify your content before announcing it to participants.
Best Practices
Track Organization
| Approach | When to Use |
|---|---|
| By topic | "Kafka", "PostgreSQL", "Kubernetes" |
| By progression | "Beginner", "Intermediate", "Advanced" |
| By course | "Data Engineering 101", "Kafka Certification" |
| By audience | "Developers", "Operators", "Data Engineers" |
Scenario Naming
Good names are:
- Descriptive: "Creating Kafka Topics and Partitions"
- Action-oriented: "Build a Real-Time Pipeline"
- Specific: "PostgreSQL Replication Setup"
Avoid:
- Generic: "Lab 1", "Exercise 3"
- Vague: "Kafka Stuff", "Database Things"
Version History
SnapBench automatically versions your scenarios. Each save in the Studio creates a numbered version. Use the History button (available in Advanced skill level) to browse all versions and restore a previous one if needed.
You can also export scenarios as JSON for external backup or version control.
Next Steps
- The Studio - Build and edit scenarios
- Writing Instructions - Create engaging guidance
