> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/admin-guide/classroom-for-instructors.md).

# Classroom for instructors

![Classroom instructor dashboard](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FRw3ahEYmO4RxfPtreAES%2Fve20261112v5-classroom-dashboard.png?alt=media)

## Goal

Run a shared class on one appliance without chaos.

## Before class checklist

1. Size the host for concurrent nodes ([Sizing and upgrades](/admin-guide/sizing-and-upgrades.md))
2. Activate Enterprise if you need **class timers**, PDF, Proctor, and auto-grade (Licence)
3. Create student users (Users, roles, and quotas)
4. Import required images before class ([Bulk folder import](/images/bulk-folder-import.md))
5. Build a gold lab; share it per Sharing labs and class timers
6. Confirm FRR/Alpine seeds if using FOSS starters (`sudo vexnx-seed-docker`)
7. Confirm `/dev/kvm` for QEMU labs

## During class

| Task                           | Where                                                      |
| ------------------------------ | ---------------------------------------------------------- |
| Share / timer                  | Lab -> workspace **Classroom**                             |
| Broadcast, grade, PDF, Proctor | [Instructor dashboard](/classroom/instructor-dashboard.md) |
| Prefer Stop vs Wipe            | Timer **Then** action, or Operate Stop all                 |
| Watch capacity                 | Home Launch Budget / disk free                             |
| External consoles              | Client Pack for SecureCRT/PuTTY when students need it      |

## After class

* Stop labs; optionally wipe student nodes
* Export useful topologies as lab packs when your edition supports it
* Use Classroom **Export PDF** for a printable session snapshot when needed

## Expected result

* Students open the shared lab without rebuilding
* Timers enforce Stop/Wipe at the deadline
* Dashboard lists only shared or timed labs

## If it fails

* No Classroom feature -> Student edition; share may still work without timers
* Dashboard empty -> share the lab or start a timer
* Host pressure -> reduce concurrent QEMU nodes; see sizing guide

## Related

* Sharing labs and class timers
* [Instructor dashboard](/classroom/instructor-dashboard.md)
* [Maintenance](/admin-guide/maintenance.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vex-nx.com/admin-guide/classroom-for-instructors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.