School ERP settings that fit how your campus runs
Set the academic year, school calendar, and module rules, and decide exactly who can see and do what. Each school in a group keeps its own settings.
Included in Orbit at no extra cost, along with every other module.
What changes when School Settings moves into Orbit
- Off-the-shelf software forces the school to work its way.
- Everyone shares one admin login, so nothing is traceable.
- Each campus in a group needs different rules.
- Every action has a name. People sign in with their own role, not a shared login.
- Fits your school. Rules are set per school and per module.
- Least-privilege access. Staff see only what their role needs.
Two campuses, two sets of rules
A trust runs a junior school and a senior school on Orbit. The junior school works Monday to Friday; the senior school also works Saturdays. Each school keeps its own calendar and module settings.
Accountants can see fee data but not exam marks. Teachers can mark attendance but not change fee structures. Each person signs in with their own role, so every change can be traced back to someone.
What the School Settings module does
Academic year and calendar
Set the academic year and the calendar policy that drives the timetable.
Per-school settings
Schools in a group each keep their own configuration.
Roles and access control
Roles, permission hierarchy, scopes, and access lists decide who sees what.
Module settings
Library loan rules, transport contacts, and other module-level options.
Email and payment setup
Save SMTP details and send a test email; set payment gateway defaults.
System status
Check platform status from the settings area.
Up and running in 3 steps
- 01
Set the basics
Add your school profile, academic year, and calendar.
- 02
Define access
Create roles and permissions for every type of staff member.
- 03
Tune the modules
Adjust library, transport, communication, and payment settings.
Built for each role
- Admin
Manage school settings, the academic year, and module options.
- Super admin
Manage roles, permissions, and access across schools.
Yes. Settings are stored per school, so each campus keeps its own configuration.
Orbit combines roles, a permission hierarchy, scopes, and access lists, so you decide who sees and edits what.
Yes. Save your SMTP settings and send a test email to confirm they work.
Modules that connect with School Settings
See Orbit against your school's week.
Tell us your role and institution. We will walk the jobs your office repeats every week — not a generic slide deck.
- Attendance, diary, and same-day parent alerts
- Fees, dues, and the modules your office actually uses
- Admin, teacher, student, and parent portals — not a generic deck
form
