Skip to main content

Tutor IDE roles and workspaces

Tutor IDE gives each access level a focused workspace: students learn, teachers run assigned classes, organization owners operate their school, and the platform superuser works in a separate CEO console.

How the levels connect​

PJ CEO / superuser — platform and all organizations
└── Organization / school
    ├── Owner — organization, teachers, classes, content and security
    ├── Teacher — assigned classes, students, assignments and grading
    └── Student — learning, projects, progress and portfolio

A user can belong to multiple organizations. Switching organization changes the active role, class and visible data. The context bar shows where and as whom you are currently working.

Student​

The student workspace goes straight to everyday learning:

  • dashboard with assignments and deadlines;
  • lessons, challenges, quizzes, CSS Battle and optional modules;
  • projects and the live-preview code editor;
  • AI tutor, progress, XP and achievements;
  • account and public portfolio.

Students cannot see organization administration or other students' data. A clear confirmation explains that publishing makes the running site public; source code stays private until the student shares it separately.

Teacher​

Teachers see only the classes assigned by an owner and the students in those classes. Their core workflow is:

  1. select a class on the teacher dashboard;
  2. check active students, grading work, alerts and approaching deadlines;
  3. choose content in Assign materials;
  4. optionally set publish and due dates;
  5. review assignments, results and student projects.

Teachers can create their own content and use organization content delegated by the owner. Project, chat, moderation and progress views stay scoped to their classes. Teachers cannot access school billing, owner-only settings or the platform console. They can change their general account settings, while the owner controls organization AI/RAG policy, security, audit and billing. Student projects are reviewed read-only and teachers cannot alter the source code. Scores and comments belong to the assignment/attempt workflow when the work is linked to one. Standalone projects do not yet have a dedicated teacher feedback field.

Class dashboard​

The class selector scopes the live roster, projects, moderation, grading work, invitations and deadlines together. All my classes means only classes assigned to that teacher, never the whole school. Summary links preserve the selected class.

Teacher Copilot​

Copilot searches permitted lesson plans, helps plan a class and prepares quizzes. Student-related answers are limited to students visible to that teacher. See Teacher Assistant.

Organization owner​

An owner may also teach, but is responsible for the whole organization:

  • school overview and activity;
  • teachers, seats, invitations and classes;
  • teacher access to organization content;
  • all students within the active organization;
  • settings, security, audit, analytics/AI usage;
  • plan and billing.

The owner delegates organization content to teachers, and teachers assign it to their students. An owner never gains access to another organization.

PJ CEO / superuser​

/dashboard/founder sits above organizations and is visibly separated from the owner workspace. It covers platform health, organizations and global operations. A normal organization owner has no access to it.

When a superuser enters an organization context, the UI displays that context so platform-wide and tenant operations are not confused.

Classes, invitations and materials​

  • A class belongs to one organization and can have an assigned teacher.
  • A teacher creating a student account must select one of their classes.
  • Tutor IDE creates an invitation link and code; it does not send an email. Copy the link and share it through your school's normal channel.
  • Using the invitation link/code can place the student in the correct class.
  • Teachers can view and revoke only student invitations for their own classes; teacher invitations are owner-only.
  • An owner can delegate challenges and lesson plans to a teacher.
  • A teacher assigns available content to a class or selected students.
  • Bulk actions display their scope and ask for confirmation.

Grading and insight​

Teachers/owners can use attempts, assignment queues and available automatic results. Analytics, projects, chat logs and moderation always respect role scope. Features tied to higher plans are marked or hidden according to the active organization plan.

Access safety​

The menu is only the first layer. Every page and API call checks role, organization and class scope again. Switching role/organization immediately applies the new scope.

See Security and Teacher first steps.