The format sets the starting rules
“Standard”, “Lecture” and “Council” are sets of starting values. You set the rules in the new class form and change them later: in the panel, from “Settings” in the class menu, or in the room itself with the lock button, “What you can do in this room”. Changes apply at once and participants don't need to rejoin; the server checks the rules on every action. The teacher can open a single cell to the group and keep the rest of the notebook locked.
What you can set
| Setting | What it means |
|---|---|
| Open cell | Shared text everyone can edit, or a separate sheet for each student in a Council. |
| Edit cells | Everyone or only the teacher. |
| Run code | Everyone, “One at a time” or the teacher. “One at a time” allows each participant at most one cell in the queue; “Run all” and running all cells above stay with the teacher. The rule also covers running files and the terminal. |
| Change notebook structure | Everyone, “Add only” or the teacher. With “Add only”, a student cannot delete even their own cell. |
| Show documents to the room | Who controls the shared screen; everyone can still browse documents on their own. |
| Create and edit files | Everyone or the teacher. Downloads are not affected by this rule; deleting, renaming and replacing an existing file by upload stay with the teacher. |
| Oracle edits files directly | “Act” mode for everyone, for the teacher or for nobody. |
| Actions per request | The limit on oracle actions per request in “Act” mode: each read, edit and run counts separately. 0 means no limit, an empty field means the server setting; if the server sets a limit, a class can only lower it. |
| Oracle questions per hour | Limit per participant, no higher than the server's. Does not apply to the teacher. |
| Time between questions | No shorter than the server's interval. Does not apply to the teacher. |
| View version history | Who sees earlier versions of the notebook and who made each change. |
| Restart kernel | Resets the shared variables; cell text and files are kept. |
| Clear shared output | All outputs, the terminal and the oracle feed. Clearing a single cell depends on permission to edit it. |
The cell lock
The teacher picks one of three states: Closed — the teacher edits and runs the cell; Open to all — the group types in this cell and runs it, even if the room rules keep that for the teacher, but can't delete or move it; Council — separate answers from each student. The “Open cell” setting decides what a click on the lock does; all three states are in the menu that opens when you press and hold the lock button or right-click it.
Action rules and Python execution
Running Python has access to the room's files. Blocking uploads or edits in the interface does not stop code that is allowed to run from writing a file with open(...). Interface rules do not give each participant a separate file system.
Ending a class and moderation
“End class” leaves all actions to the teacher for now and keeps the settings and materials. “Resume class” brings back the previous rules. An empty room only means nobody is connected; it does not mean the class has ended.
To remove a participant, use “Remove from class…” in the “People” panel. Their access is blocked for 24 hours, tied to a marker in the browser; another browser or a private window can get around it. The participant's oracle questions and the answers to them are deleted, and version history won't bring them back; their Council attempts and run requests are deleted too. To lift the block early, click “Restore” in the “Removed from the class” list; deleted content is not restored.
This is a tool against disruption, not identity verification or exam proctoring.