From first setup to everyday school operations

Understand the ERP.
Work with confidence.

A practical handbook for school administrators, teachers, finance teams, HR, students and parents. Begin with setup, follow your role, then open a module for its complete working sequence.

21 practical guides7 core rolesOriginal diagrams retainedReviewed 01 Oct 2026

Before following a guide: confirm your school, academic year and role. Module access and available actions depend on your installed version, permissions and configuration. Examples are illustrative; this guide does not change school records.

Your first setup sequence

Prepare the foundation first.

Complete the dependencies in order. This is a reading/planning checklist for this visit, not a live report of your school setup.

0/8 planning items checked

The connected school record

Understand what depends on what.

  1. 01

    Academic setup

    The year, class and section tell the ERP where school activity belongs.

  2. 02

    People and enrollment

    Staff access and student enrollment connect people to the working school structure.

  3. 03

    Daily activity

    Attendance, homework, fees and exams use those existing people and academic references.

  4. 04

    Review and reporting

    Reports summarize saved records. Always compare the same period, scope and statuses.

Example: a student may exist in the directory but be absent from a class attendance list if enrollment is missing for the selected year. Check the relationship before recreating the student.

A daily review routine

  • Teachers: check timetable, mark attendance and review homework.
  • Finance: reconcile collections and review outstanding assignments.
  • HR: inspect pending requests and staff attendance.
  • School Admin: review exceptions and unfinished tasks across modules.
Learn for your responsibilities

Your role, your starting point.

These are learning paths, not a permission guarantee. Your school’s role and access settings remain the source of truth.

SUPER ADMIN

Platform owner

  • Manage all schools (create, activate, codes) from platform scope.
  • Use "Open as context" to work inside a school as that school's admin.
  • Platform SaaS dashboards: Subscriptions & tenants, Finance, Analytics, and Alerts.
  • PrimaryRole-based navigation changes with/without school context.
SCHOOL ADMIN

Principal / operations

  • Dashboard and full school configuration: academic years, promotion, timetable.
  • Students: directory, registrations, ID cards, attendance, exams, homework.
  • Finance: fee structures, assignments, finance module, expenses.
  • HR: staff records, leave, employment forms, incoming job applications.
  • Communication, open enrollment & employment landing pages, support.
  • Data migration tracker under Administration → Data migration.
TEACHER

Class & subject teacher

  • My classes: roster and section-aware views.
  • Timetable, attendance for assigned sections.
  • Exams: create/marks for permitted sections; AI-assisted online exam builder.
  • Homework assign and track; student profile where allowed.
  • Messages; personal HR self-service where enabled.
ACCOUNTANT

Finance office

  • Financial module, fees (structures, collection, reporting), expenses.
  • ID card operations tied to fees/cards where applicable.
  • Academic year visibility and promotion roster for fee-linked promotion steps.
HR

Human resources

  • HR module: manage employees, leave cycles, payroll/letters, and HR workflows.
  • Department & job title model: pick from catalog or enter Custom labels.
  • Employee records store department and designation strings.
STUDENT

Learner portal

  • Dashboard, personal ID card preview, timetable.
  • Attendance view, fee balance and payments (where enabled).
  • Exams schedule and results; homework; optional online exam taking.
PARENT

Guardian portal

  • Linked children: results, report cards, timetable, homework.
  • Fees: pay or view receipts across children.
  • Messages with school; school-wide announcements.

Moving from another ERP?

Inventory your source data, prepare academic structure, validate a small batch and reconcile the resulting records. Bring current-year data first, plan historical data separately and agree on a cutover date before wider rollout.