Always included
Core & Students
The student record every other module reads from.
Every school already has a register. The question is whether the rest of the software agrees with it.
Core holds the student record, the houses, the staff accounts and who may see what. Every other module reads from it rather than keeping its own copy, so a corrected spelling or a change of house is corrected once and is right everywhere — on the gate board, in the clinic, on an application.
It is always included, because a module that had to be told who the pupils are would be a second register to keep in step.
HOW IT CONNECTS
A shared institutional foundation.
The student register is the foundation other modules build on. Add connected workflows without creating another institution or rebuilding the register.
KEY CAPABILITIES
What changes in the workflow
One student record every module reads from
Houses, year groups and sections, as your school uses them
Staff accounts, roles and per-module access, set by your own administrator
Bulk import from a spreadsheet, with a preview before anything is written
An audit trail on every change a parent could dispute
YOUR WORKFLOW IN CAMPUSOS
Show us how your institution works.
We’ll focus on this workflow in the live product and show you how it connects to the rest of the institution.