School ERP
Run a school — or a trust of several campuses — on one system. Admissions, attendance, fees, timetable, exams and report cards, built multi-campus from the first table. Every permission is enforced in the database, not the interface.
Structure & Access
A trust with four campuses is one workspace, not four accounts — and who can see what is decided per campus.
Multi-Campus from Day One
One school, many campuses, each with its own classes, staff, timetable and fee structure — under a single trust.
Why it matters: A trust sees every campus together; a campus head sees only theirs.
Academic Years & Terms
Every record belongs to an academic year. Last year stays exactly as it was when this year opens.
Why it matters: A 2024 report card still reads as it did in 2024.
Fifteen Role Templates
Principal, vice principal, class teacher, accountant, exam controller and more, across 38 permissions you can adjust per school.
Why it matters: An accountant never sees marks; a teacher never sees fees.
Permissions Enforced in the Database
Access is decided by row-level security, so a permission holds whether the request comes from the app, the API, or anywhere else.
Why it matters: The rules cannot be bypassed by talking to the API directly.
Guided Setup
A resumable wizard walks a new school through campuses, years, classes, sections, subjects and staff.
Why it matters: Get a school configured without a consultant.
School ERP FAQ
Ready to try School ERP?
Start free — school erp and every other SurveyKar service are part of the same account.