Skip to main content
Admin and dean users drive most school-wide setup and operations. Both roles are school-management roles, but they are separate account classifications. They normally require the corresponding Dean or Admin group in addition to is_dean or is_admin. The API checks both the Django permission and the operation’s role gate.

​
Capabilities

Admin and dean access commonly supports:
  • school setup and configuration
  • academic structure management
  • student and staff management
  • school-wide academic workflows
  • attendance review and management
  • fee and communication workflows

​
Core areas commonly available

  • school profile and structure
  • students and archives
  • teachers and board-member records
  • classes, sections, and subjects
  • fees manager
  • broadcasts
  • SRMS
  • CBT
  • LMS
  • Classroom events, recordings, attendance, and whiteboards
  • attendance review and management
Admins additionally have the broadest access to school settings, academic years and terms, promotions, Access PIN inventory, and school subscription/billing records. Deans share the teaching bundle and receive the school-operation permissions needed for users, structure, broadcasts, fees, and academic oversight, but do not receive the Admin-only year, Access PIN, promotion, and subscription bundle by default.

​
Typical operating order

  1. confirm the current school setup is correct
  2. confirm users, classes, sections, and subjects exist
  3. create or review student records
  4. run academic workflows such as SRMS, CBT, LMS, or Classroom
  5. configure Classroom operational limits and recording notices
  6. manage attendance, communication, and fees as needed

​
Common admin-only concerns

  • school settings
  • Access PIN inventory
  • broader user management

​
Common dean concerns

  • academic oversight
  • fee workflows
  • broadcasts
  • operational review of attendance and student records
Both deans and admins can move students between classes. A teacher’s class-placement request is rejected by the API even when the teacher can update other permitted student fields.

​
Responsibility matrix

​
Frequent mistakes to avoid

  • entering scores before the academic structure is stable
  • promoting students before the next year exists
  • using class-bound sections with the wrong class
  • assuming a student-facing issue is unrelated to class, section, or year setup