Skip to main content

Getting started: teacher and school

This guide describes the current workflow for organization owners and teachers. The owner configures the school and delegates access; a teacher works only with assigned classes.

1. Enter the correct organization​

Open app.tutoride.dev. After signing in, check the context bar for the expected organization and role. If you belong to multiple organizations, switch context before opening student data or settings.

A person joining through an invitation uses the received link/code. An owner creating a new organization accepts the current required agreements during onboarding.

2. Understand the role boundary​

  • The owner manages teachers, classes, seats, settings, security, audit and organization billing.
  • A teacher sees assigned classes, their students, materials and work queues.
  • The platform superuser uses a separate CEO console; a school owner is not a platform administrator.

Navigation is not the only protection. The API checks authority again for every operation.

3. Create classes and assign teachers​

The owner opens class management, creates a class and selects its teacher. A teacher sees only classes assigned to them. Prepare at least one class for each teacher before adding students.

Names that include the schedule or level, such as “Monday 16:00 — HTML”, make scope selection clearer on the dashboard and assignment screens.

4. Add students​

There are two primary routes:

Staff-created account​

Choose Add student in student management and enter the required details. A teacher must select one of their own classes. An owner may intentionally create an ungrouped student and assign a class later.

Identity, organization membership and class enrollment are created as one operation, so a partial student account should not remain after an error.

Choose the student role and class in invitations, then create a link. Tutor IDE generates a link and code but does not send an email. Copy the link and share it through your school email, student system or another approved channel.

A teacher can create, view and revoke only student invitations for their own classes. The owner creates invitations for new teachers.

5. Prepare and assign content​

The owner can delegate organization content to teachers. A teacher sees content they created and content delegated by the owner. Platform-global curriculum is read-only.

Then:

  1. open Assign materials;
  2. select a class or permitted students;
  3. choose the lesson/task;
  4. set publish and due dates when needed;
  5. verify the scope shown in the confirmation.

6. Use the class dashboard​

Select one class or All my classes on the teacher dashboard. The selected scope covers all of these together:

  • live roster and activity;
  • work awaiting grading;
  • moderation alerts;
  • approaching deadlines;
  • invitations and recent projects.

Summary links preserve the selected class. “All my classes” never means every class in the organization.

7. Review assignments and attempts​

Add scores, points and comments in the student's assignment or attempt workflow. Automatic results are an aid, but the teacher should inspect the solution and scope before confirming a grade.

8. Inspect projects without changing code​

Open a project from the project list or class dashboard. The editor displays a read-only marker. You can navigate files, run the preview and inspect the live site, but cannot save, add, move, rename or delete student files.

A standalone project does not yet have a dedicated feedback field. If it is linked to an assignment/attempt, add the comment and score in that workflow.

9. Use AI and moderation responsibly​

Teacher Copilot searches permitted content only, and student-related answers are limited to students visible in the active organization. Moderation alerts and student logs also respect class scope. Organization-wide AI/RAG policy is controlled by the owner.

10. First-class checklist​

  • The context bar shows the correct organization and role.
  • The class has its teacher assigned.
  • Students belong to the correct class.
  • Invitation links were manually delivered to the intended people.
  • Content is visible to the teacher and assigned to the correct class.
  • Publish and due dates are correct.
  • The class dashboard shows the expected roster.

Start with one class, a few students and one lesson. Expand to more classes only after checking the complete journey.