Teacher guide
Use the management portal to define a challenge, publish it, assign it, and read each session. This guide covers those screens in the order you use them.
How to use this guide
This guide is divided into numbered workflows. Each workflow is a task made of numbered steps, and workflows appear in the order you first need them.
Workflow 1
Open the management address from your institution. It sends you directly to the sign in form.
Enter both in the sign in form. The portal never sees or resets your password.
The tab returns to the portal by itself and lands on the dashboard. Nothing needs to be clicked in between.
Read the privacy policy and terms of use, tick both boxes, and choose Agree. You are asked again when either document changes.
Workflow 2
A teacher sees Templates, Assignments, Sessions, Open Safeguards, Completion, and Rosters. Users and Institutions appear only for institution and platform administrators. The linked tiles open their lists, and the panels below show open safeguards and recent sessions.
The drawer links to Dashboard, Templates, Rosters, Assignments, Reports, Safeguards, and About. About links to the privacy policy, terms of use, and third-party notices. User accounts and institution settings belong to institution administrators.
Lists provide search, a New button, and row actions. Select a record to open it; dialogs confirm actions such as archiving or removing.
Workflow 3
A template is a reusable reasoning exercise, and it has two layers. The fields on the template itself, Title, Type, Visibility, Locale, Subject, Age rating, and Description, say what kind of challenge it is, who may use it, and how it is filed; none of them reach the agent. The challenge itself, the scenario, constraints, goal, and evaluation criteria, lives in a published version, covered in the next workflow, so it can be frozen and revised without the record of past sessions changing underneath it.
Search templates by title, and narrow the list with Show, Type, and Subject above it. Show starts at My templates: yours, plus any your institution shares with its teachers. Platform library switches to the ready-made library covered in workflow 6, and All templates lists both. Use Show archived to find retired work.
Enter a title, and a Description written for the student rather than for you: it is the short summary shown in lists and on the student's card, saying what the challenge is about. It is not read by the agent, and it is not the narrative the agent speaks in, that is the assignment's Theme, set per assignment and covered in workflow 8. Type sets the rules the agent runs the conversation by; see the challenge types reference for what each of the five does and how it is graded. Socratic Constraint is the default. Locale records the language the challenge is written in.
Visibility is filled in as Personal, and a template you create is saved as Personal: only you see it, assign it, and change it. Templates your institution administrator shares at Institution visibility appear to every teacher in that institution, who can assign and clone them but not edit them. Platform library templates (Visibility System) are read-only, but every teacher can browse them, assign them directly, or clone one into a template of their own.
Subject files the template under a topic (Everyday reasoning, Philosophy and ethics, AI and technology, Science, and so on) for the Subject filter on the Templates list. Both fields are optional. Age rating (13+, 16+ or 18+) marks content that is not for every age: a rated template blocks a student under that age, or one with no recorded date of birth, from starting it. Leave it empty for a challenge any student may start.
Save creates the template. It cannot be assigned until it has a published version.
Workflow 4
The version form opens. Publishing creates a version that cannot be edited later, so the form opens only from this action.
These fields are what the agent and the judge actually read. The Scenario is what the student is given, and what the agent works from turn by turn. Constraints, one per line, are rules the agent holds the student to, and the judge reads them too. The Goal is where the agent steers the conversation, and the judge reads it as well. The Evaluation criteria, one per line, are what the judge grades the student's messages against. Time limit (minutes) is optional: leave it blank and the session runs untimed, or set 1 to 240 minutes and the session closes at the limit and is graded on the work done, showing as Timed out. Only time between turns counts towards it, capped at fifteen minutes per gap. Challenge title defaults to the template title; goal and criteria default to values for the chosen Type, listed in the challenge types reference.
Under the fields, the portal checks the content as you type. Ready to publish means nothing is missing. A red chip names something that would stop the publish, such as an empty scenario, and Publish stays disabled until it is fixed. An amber chip flags content that is only thin, such as a very short scenario, no constraints, or no goal (the type's default is then used); it never stops you publishing.
Publishing adds an assignable, immutable version. Later versions leave earlier versions and their sessions unchanged.
Each new version starts from the previous fields. Assignments keep the version they were created with.
Workflow 5
The Teacher assistant panel sits to the right of the template form, on a new template and on any template you can edit. It does not appear on a template you can only read, such as a platform library template.
Type the topic, the class, and what students should reason about, then choose Send, or press Enter (Shift+Enter starts a new line). The assistant can suggest a challenge type and say why, compare types, and ask you one question at a time. Ask it to draft the challenge when you are ready.
A draft arrives as a Proposal card under the conversation: a one-line summary, the title, description, and type it would set, and the scenario, constraints, goal, time limit, and evaluation criteria of the version it would publish. The same readiness chips as the publish form flag anything that would block publishing or is thin.
Nothing is saved until you choose Confirm and save. On a new template that creates the template and publishes the proposed content as Version 1, the same as Save followed by Publish. On an existing template it updates the title and description if they changed and publishes the content as a new version. Discard drops the card and changes nothing. A template's type cannot change once it exists, so for a different type start a new template.
After a confirmed save the assistant reviews the saved version: a score out of five each for the scenario, constraints, goal, and criteria, whether any field gives the answer away, what is missing, and suggested fixes. Act on it by asking for a revised proposal, or by publishing a new version yourself.
The assistant never saves, publishes, or changes anything by itself; only your click on Confirm and save does. It will not write a worked answer, a solution, or the conclusion students should reach into any field: the scenario sets out the situation, and the student does the thinking. It sees only this template and your unsaved form, and the conversation is not kept once you leave the page.
Workflow 6
On Templates, set Show to Platform library. The library is a set of ready-made, published challenges, several of each type, maintained by the platform. Each row is marked System - read only.
Type and Subject filter the list, and the search box matches titles. Each row shows its type, subject, locale, and latest published version.
A 13+, 16+ or 18+ chip marks a template for older students. A student under that age, or one with no date of birth on record, cannot start it. The assignment form warns you when you add a rated template to a challenge chain, but does not stop you saving, because the age check happens when each student starts.
Select its title. A library template opens read-only: its description, its subject and age rating, and its version history with the full scenario, constraints, goal, and criteria. The one action is Clone this template.
You do not have to clone a platform library template to use it: it can be assigned as it is. Clone it when you want to edit it into your own version.
Clone is available on any published, non-archived template you can read: on its row in the list, or with Clone this template on a library template's page. It copies the title (with " (copy)" appended), description, type, locale, subject, age rating, and the source's latest published content, and lands you on the new template's own page. The copy is Personal and yours to edit.
A clone always publishes Version 1 from the source's latest content, so it is assignable immediately. Editing and publishing again adds Version 2, leaving the clone's own Version 1 unchanged.
The archive action on a template's row hides it and stops it being chosen for new assignments. Existing sessions and reports remain available. Turn on Show archived to find it again and restore it. Platform library templates cannot be archived.
Workflow 7
A roster is a named group for repeated assignments. Assignments can also target one student directly.
Enter a roster name and select one of the institutions you teach in. If you teach in one institution, it is already selected. The institution cannot be changed after the roster is saved, because the roster's enrollments and assignments belong to that institution. Add students on the roster's page after saving.
Search with Add student, choose a person, and select Add. Each student must belong to the roster's institution. Remove a person from the table.
Save applies enrollment changes. Leaving without saving discards them.
The key icon on a roster's row opens its class join code. Choose Generate code to make one, or Rotate code to replace an existing code with a new one - the old code stops working the moment you rotate. Copy the code or share the join link it fills in for students, and set an optional expiry and a max use count. Disable revokes the code immediately without issuing a new one.
A student signs up with the code, or opens your join link, which fills the code in for them; see Signing up and signing in. Either way lands them on your roster as a Student, with no admin involvement. A student who already has an account and opens the join link instead sees a "class code waiting" card on their dashboard and joins from there; see Joining another class.
Workflow 8
An assignment connects a student or roster to one or more published challenge versions, an optional theme, a limit on student turns, and an availability window.
If you teach in more than one institution, choose the Institution first: the student or roster, and every template in the chain, must fit it. If you teach in one, it is already chosen. Then set Assignee Type to Student or Roster, and search for the person or group.
Add published template versions in sequence: your own templates, your institution's shared ones, or platform library templates. Use the arrows to reorder, Add challenge to extend, and the bin to remove a row. A row whose template carries an age rating shows the rating and a warning that younger students, or students with no date of birth on record, cannot start it.
Max student turns is filled in with the platform's default. A session closes, with its report, after that many student messages if it has not finished sooner. The highest value accepted is the platform's ceiling, or a lower one your institution sets; the field names the limit if you go over it. A change made later applies only to sessions started after saving.
Theme re-skins the narrative the agent speaks in, without changing the task or the grading. The same reasoning challenge can be set in a harbour for one class and a hospital for another, and the reports stay comparable because only the surface changed.
Description and Theme are both prose you write, and it is easy to mix them up. Description is set on the template, is the same wherever the template is used, is shown to people in lists and cards, and never reaches the agent or the judge. Theme is set per assignment, wraps the narrative the agent speaks in on every turn, never changes the constraints or the goal, and never reaches the judge or scoring, so grades stay comparable across themes. The conversation itself is configured by Type, plus the Scenario, Constraints and Goal on the published version, plus this Theme.
Open At and Close At are optional but enforced. The student sees Opens, Due, or Closed, and cannot start or continue outside the window. Close At must follow Open At.
The page lists sessions, turns, dates, and report links. The institution, assignee and chain are read-only; title, theme, turn limit, and dates remain editable.
Cancel assignment stops new starts and marks open sessions Cancelled. Completed sessions keep their record and report. The assignment leaves the list until you select Show cancelled and archived; create a new assignment if the work should continue.
Workflow 9
Use Reports filters for institution, student, roster, assignment, template, status, or start date. Choose Apply filters, then View on a row; Clear filters restores the list.
The report shows the student, status, turn and hint counts, dates, and links to related assignment, template version, and roster.
Pending sessions show no evaluation. A finished session shows an overall score, a written summary, and, when enabled, four fixed dimension scores with a rationale each: conceptual accuracy, communication clarity, problem-solving approach, and completeness. See the challenge types reference for how the judge and the score are produced. Checkpoints list the milestones the judge tracked for the challenge type, whether each was met, and at which turn; the transcript marks a milestone where it happened.
The transcript is the student-visible conversation, labeled by speaker. Internal instructions and grading rules are excluded.
Workflow 10
A flag is raised when the AI sees a disclosure of self-harm, abuse or serious distress in a student's message. The student gets a short supportive reply, the session pauses, and the student sees a paused message in place of the response box until the flag is reviewed. Flags appear in the Safeguard flags list, in the dashboard's Open Safeguards count, and as a notification on your Notifications page.
Opening a flag shows its context and the student-visible transcript.
Clear and Escalate both require reviewer notes and a reason. The notes and reason are saved with the flag. Clearing the last open flag on a session lets the student carry on where they left off; escalating leaves the session paused until someone clears it.
Not yet available
Detection covers safeguarding disclosures only, not inappropriate language or academic-integrity concerns. The beta sends no email, so watch your Notifications page and the Safeguard flags list.
Workflow 11
The bell in the app bar shows how many notifications you have not read, and opens the Notifications page, also in the navigation drawer. It reports work you set being published and students finishing a challenge you assigned. Opening the page marks what it shows as read. There is no email, and no way yet to choose which notifications you receive.
The top-right icon switches the portal between light and dark themes.
On a narrow window the drawer hides. Choose the menu button to open it over the page.
There is no delete button for your own account or your students'. Your account owns your classes, templates, and assignments, and your students' records belong to your institution. Send any request to erase an account to your institution administrator, who can erase students and teachers from Institution users after moving any of your classes still in use. Independent learners can delete their own accounts.
The sign-out icon ends your session. Use it on a shared machine.
Define, publish, assign, and review challenges, draft them with the teacher assistant, or start from the platform library. Build rosters, set turn limits and availability windows, cancel assignments, and clear or escalate safeguard flags.
Programs, bulk operations, exports, LMS integration, and additional challenge types are planned. User accounts and institution settings belong to institution administrators.
