#Classrooms

A classroom is a group of students who will work through the same set of modules. Modules are not assigned directly to students. They are released into a classroom, and every student in the classroom can run them.

#Creating a classroom

From your organization's home page, open the classrooms list and create a new classroom. You give it a name; the rest of the configuration (timer behavior, whether it is a contest, whether helpdesk tickets are enabled) is set on the classroom afterward.

A classroom belongs to one organization, runs on that organization's deployment zone, and is independent of every other classroom. Students can be in more than one classroom at a time.

#Adding students

Open the classroom and go to its users page. Today the platform supports one enrollment path: pasting a list of contestant identifiers (the per-student IDs your organization assigns) into the bulk-add field, separated by commas or newlines. Submit the list and the platform creates or attaches accounts for each ID.

There is no self-service signup, invite link, or CSV import in the UI right now. If you need a different intake (for example, importing from an LMS roster), talk to your organization admin.

#Releasing a module to a classroom

Modules reach students through a release. A release pins a particular version of a module to your classroom and produces a shareable link.

flowchart LR Module[Module in the library] --> Build[Stable build for your zone] Build --> Release[Release into the classroom] Release --> Link[Shareable link to students] Link --> Attempt[Each student gets a fresh VM clone]

From the classroom's management page, pick a module from the library you have access to and create the release. You can release the same module to multiple classrooms; each release is independent. Once a release exists, the management page shows the link you give your students.

A few rules:

The module must already have a stable build in your zone. If it does not, see The module library for how a build is promoted.
Releases are pinned. Updating the underlying module after release does not change what your current students see; you create a new release to ship the update.

#The gradebook

Each classroom has a gradebook that lists every student, every release in the classroom, and the score they earned (or are still working on). Scores come from the autograder when a student clicks I'm Done in the console. If a student opened helpdesk tickets during a module, those tickets and their per-VM responses appear in the gradebook entry alongside the score.

#Contest classrooms

A classroom can be marked as a contest. In contest mode, releases run with personal countdown timers and the gradebook surfaces standings. See Timers and Contests for the student-side experience and the configuration that drives it.