Joining
Your teacher gives you a six-character code. Go to /join, type it in and press Join. That is the whole thing. Capitals do not matter, and spaces and dashes are ignored.
If your teacher shared a join link, or put a QR code on the board, open it or scan it: there is no code to type. You see your class's name and one button, Join, and after it You're in, with the first piece of work your teacher set. If you are not signed in yet, you are asked how you sign in first, and you are in as soon as you have.
If your teacher gave you a login card, you do not need an email address. Scan the QR code on the card, or go to /class and press Sign in with your login card. Type the class code, your name as it is on the card, and your password.
The code is upper case and has no O, I, L, 0 or 1 in it, so if you are looking at something that could be a letter O it is a zero, and it is not.
If your teacher is running a live session, type its code and a nickname on /join and you are in the editor on the class's circuit with no account at all. Your nickname goes when the session ends. If your teacher keeps your work, you get your own copy of the circuit to keep, and the teacher keeps the original.
You need an account to join a class itself, because a class is a roster and a roster needs names. You do not need one to use Mokxi: the simulator works signed out and always will. See signing in.
Your class page
/class/<id> lists the work your teacher has assigned: each assignment with
its title, its due date if it has one, and a Start button.
Starting one puts you in the editor with the circuit or the lesson already loaded. Once you have submitted it, the button says Continue and opens your own copy, so your work is where you left it; Open the starter beside it opens your teacher's starter again.
Parts that will not move
Some assignments come with part of the circuit held in place. A held part wears a small padlock, a held wire is drawn a shade back, and the cursor over either one is a no-drop. Select one and the properties panel shows its fields switched off over a line saying Locked. Only the person who set this work can unlock it.
That is on purpose, and it is only the starter. You can still do everything the work asks of you: add parts, wire into a locked part's pins, name nets, change anything you added, run it and read all of it.
Sometimes the code is held too. The file strip says Locked by whoever set this work. You can read it and run it.
Copying a locked part gives you one of your own. A copy is yours, so it pastes unlocked. Forking the assignment into your own project does not unlock it: the copy is the same work, and owning it is not being the person who set it. Ask your teacher if something is held that should not be.
Submitting work
Build the thing, then open the Save menu in the editor's header and press Submit to my class. It saves your project and hands it in. The item is only there when you opened the work from your class page.
Submitting hands in the project as it is at that moment. If you keep working on it afterwards, your teacher still sees, checks and grades what you handed in, and the class page says it was edited after hand-in. You can submit again whenever you like: the latest one is what your teacher sees.
For a lesson, your progress goes with it, so passing seven of nine steps shows as seven of nine rather than as nothing.
Checking your own work
Some work is set with checks on it: things your teacher expects your circuit to do, written once and run on everybody's. Where there are any, your class page has a Check my work button under that piece of work.
Pressing it runs your own circuit, here in your browser, on the same simulator the editor uses, and tells you how each check went with the number it measured beside the number that was wanted: it blinked every 1462 ms; expected every 1000 ms, within 50. That is a thing you can go and fix. You can press it as often as you like, and what it finds goes to your teacher with your submission, so they see what you saw.
It is grading the simulation, which is not a bench: the timing is ideal and there is no analog noise, and the panel says so. And it never shows you your teacher's circuit or anybody else's, only your own.
What your teacher can see
The work you submitted to that class, and how far through a lesson you got.
Not your other projects. While you are in a class, every project you make is private and stays private: it cannot be opened by link or put in the gallery, and you can keep as many as you like.
AI help
Mokxi AI, Mokxi's helper, is off for a class until your teacher turns it on for that class. Until then the Circuit Doctor still checks your wiring and code and offers its fixes, with no Explain more button. With Mokxi AI on, Checkup answers through Mokxi AI, and the class shares its questions: five a day for each student, and no student more than ten. Mokxi AI is always off for class logins and younger children. For anything else, ask your teacher.
Leaving
Leave this class on the class page. Your own projects stay in your account. The submissions you made to that class do not.
Getting your work out
Any project saves to a file and opens again anywhere, with no account. That is worth doing at the end of a course, so what you built does not depend on a class you are no longer in.
Earning something for it
Passing a lesson step earns XP, and the steps the simulator actually checks are worth more than the ones you tick. See XP and levels and streaks and badges. Joining a class is itself a badge.