Staff records, and the permissions that follow from them.
A staff list is the least interesting record in a school and the one that quietly determines whether the software is safe to use. Every person who signs in sees something, and what they should see differs sharply: a class teacher needs their own sections, an exam coordinator needs the whole assessment structure, an office administrator needs student and admission records, a principal needs the summary across all of it. Get that wrong in either direction and you have either a security problem or a system nobody can work in.
- Staff profiles and contact records
- Role-based access for office, teaching and leadership staff
- Subject and class assignments per teacher
Teaching and non-teaching staff in one record set
Staff profiles cover both teaching and non-teaching staff, with contact records held alongside. It is a directory the school actually uses rather than a list maintained for its own sake — the same record that identifies a teacher for subject assignment is the one the office reaches for a phone number, so there is no separate contact sheet drifting out of date in parallel.
Access decided by role, not by trust
Role-based access assigns office, teaching and leadership staff different views of the same system. A class teacher opens to their own sections rather than the whole school. Someone whose role does not include a category of information does not see it — including through the AI assistant, which answers only from records the asking staff member’s role already grants access to. Permissions are a property of the role rather than a set of individual exceptions somebody has to remember to revoke.
Subject and class assignments that drive the rest
Each teacher carries their subject and class assignments, and those assignments do real work elsewhere. They decide whose marks entry screen shows which subjects, which sections a class teacher marks attendance for, and who appears against a subject when the exam coordinator is checking coverage. Recording the assignment once means the rest of the system stops asking the same question in four different places.
What changes when someone joins or leaves
Because access follows the role and assignments sit on the staff record, onboarding a new teacher is a matter of creating the record and assigning their classes and subjects rather than configuring permissions by hand. The same is true in reverse at the end of a session, when responsibilities move between staff and the assignments move with them.
About staff.
The modules this one leans on.
- Structure
Classes & Sections
Define your school once — classes, sections, capacities and class teachers — and the rest of the system follows that structure for the whole session.
Learn more → - Curriculum
Subjects & Streams
Core subjects, electives and senior-secondary streams, mapped to the classes that take them — including the optional-subject choices that make marks entry messy elsewhere.
Learn more → - Records
Students & Admissions
Every student record in one place, from enquiry through admission to alumnus — with documents, guardians and contact details attached rather than filed separately.
Learn more →
See all eight modules on the platform overview.
Spend less time on administration. More on students.
Start with one class and see how the session works end to end — admissions through marksheets — before you commit to anything.