By responsibility

The same school.A different desk.

A principal needs the whole operational picture. A teacher needs assigned classes. A parent needs linked children. Everyone stays in one system without everyone getting the same system.

Who sees what
School owners and principalsCross module health, approvals, risks, people and institutional performance.Broad oversight
Academic leaders and teachersCurriculum, assigned classes, lesson planning, attendance and review.Teaching context
Registrars, finance and HRFocused workspaces with access limited to their responsibilities.Task focused
Parents, guardians and learnersOnly linked academic, attendance, fee and communication context.Personal scope

Four workspaces, one source of truth.

Each role receives a workspace shaped to the work in front of them. The record underneath is the same one.

Leadership

See health, risk and decisions across enabled modules.

Leadership receives a connected operational picture while record level access still follows policy.

AttendanceToday and emerging patternsFinanceCollection and exceptionsAcademicsPlans, progress and review
Academic

Plan, teach and review with shared learning context.

Curriculum, classes, lesson plans, attendance and assessment stay together for the people responsible.

CurriculumUnits and standardsTeachingAssigned classes and plansAssessmentGradebook and review
Operations

Complete focused work without losing school context.

Admissions, finance, HR, library and transport each receive precise tools and controlled access.

AdmissionsApplicants and documentsFinanceInvoices and paymentsPeopleStaff, leave and payroll
Family

See only the information relevant to you.

Linked learners receive clear progress, attendance, fee and communication views without administrative complexity.

ProgressGrades and feedbackAttendancePersonal recordMessagesRelevant school updates

Permissions, not role assumptions.

Access follows granted responsibility rather than a role name. Two people with the same job title can hold different permissions, and the interface reflects that difference honestly.

Built for one campus or a whole network.

School scoped records stay isolated even across multi school groups, so central policy never flattens the individual campus.

Single campus

Independent school

One campus, one calendar, one team. Enable the essentials and grow into the rest.

School group

Multi school network

Shared standards with local control, network wide analytics and central permission policy.

Foundation

Tenant isolation

Every school stays its own school. Records and actions remain scoped by institution.

Show us how your school is organised.

A demo follows your operating priorities and permission model, not a fixed script.