Roles and permissions

A school workspace in ClassPods has three roles. Each one sees what they need and nothing more.

School admin

The school admin is the named person responsible for the school's ClassPods rollout. They can:

• Invite or remove teachers
• See cross-classroom admin reporting (department-level accuracy, completion, weak spots)
• Update billing details and contact information
• Set school-wide defaults (e.g., default locales available to teachers)
• Speak to ClassPods support on behalf of the school

What a school admin cannot do: see individual student emails, override a teacher's content, or alter a class without the teacher's consent. They see aggregates, not surveillance.

Teacher

Each invited teacher gets full Pro features inside the school workspace. They can:

• Create classes, quizzes, lesson packs, and assignments
• Host live sessions
• See per-student progress in their own classes
• Invite students by class code

A teacher's view is scoped to their own classes — they don't see other teachers' classes by default. (Department-wide content sharing is opt-in.)

Student

Students join classes by code or by clicking a teacher's invite link. They see:

• The classes they're a member of
• Assignments and due dates
• Their own XP, streaks, and badges
• Practice and flashcards for content they've engaged with

Students do not see other students' emails, scores compared to specific named classmates (outside the live leaderboard, which the teacher can hide), or any school admin reporting.

Why there's no parent role

ClassPods is teacher-led and classroom-centric. Parent visibility is something teachers manage outside the product today — usually a screenshot of progress or a printed report. A dedicated parent role is on the roadmap but isn't a v1 capability.