Trainer & admin guide

Open Sessions and click New session. Pick the lab and a published version, set the capacity, and either schedule a start time or start immediately. Under Slot settings you can set the timezone, recording, and the pace (free, or step-locked to keep the class together).

EduShell warms one ready seat per learner ahead of time, so nobody waits on a booting machine. You can extend the running time or add seats later without interrupting anyone.

There are two ways in, and you can use both for the same session:

• Invite link: copy the session link and send it however you like. Learners click, sign in by email, and land in their seat.
• Join code: a short code you can read out loud. Learners open the join page, type the code, and they are in, with no account to create first.

You can import a roster of emails ahead of time, or let learners self-serve with the code. Either way there is nothing to install.

The live monitoring view is your cockpit. For every seat you see presence, how far the learner has progressed step by step, and their state (active, waiting, struggling). EduShell watches for learners who are stuck and raises an AI alert before they even ask, so you can reach the right person first.

A message box lets you talk to the whole class at once, and the roster reorders itself to float whoever needs you to the top.

From the roster you have several ways to help:

• Take control: open a learner's terminal and drive it yourself to unblock them, then release control back.
• Send a hint: push a targeted hint to one learner without giving away the answer.
• Chat the class: send a message every learner sees, useful for a correction that affects everyone.
• Raise hand: learners can raise their hand and appear in the help queue, so nobody is missed.

Everything happens in the browser, in real time, without the learner sharing their screen through a third-party tool.

If a lab turns out to need more CPU or memory than planned, you can change the resources of the running seats from the monitoring view, without restarting the session. EduShell admits the new size against available capacity, then applies it. Size up when a workload is heavy, or down to fit more learners.

Open Labs and create or edit one. A lab has three parts:

1. Instructions: written in Markdown, with syntax-highlighted code and copy buttons. You can author bilingual content (FR and EN) that follows the learner's language.
2. Environment: choose the tier and base image, add containers, a per-learner cluster or a VM, attach volumes and networks, and set a setup script that runs once at boot.
3. Checks: automatic verifications that confirm each step, so a learner gets instant feedback and you see progress on the dashboard.

Labs are versioned: edit a draft, preview it in a real sandbox, then publish. Sessions always run a published version.

The Administration console is where an owner or admin runs the org:

• Members & roles: invite people, change roles, transfer ownership.
• Settings & visibility: rename the org, and choose whether usage and billing are visible to all members or to admins only.
• Authentication (SSO): connect OIDC, SAML or LTI so your people sign in through your identity provider.
• API keys & webhooks: issue programmatic credentials and subscribe to events (see the API reference).
• Activity log: an audit trail of who did what.

Sensitive actions (closing the org, transferring ownership) are guarded, and reversible where they can be.

Billing is metered by the credit-hour (see core concepts). From Billing, an owner or admin can see the current plan, this month's usage against the included allowance, and invoices, and can subscribe or change plan. Usage and billing visibility for non-admin members is configurable in Settings. The meter stops when a session ends, so you never pay for idle seats.