Franchises & school groups
One platform for every campus you run
Most school software is built for one school and later stretched across several. Nuxused was multi-tenant from the first migration: a school is the unit of isolation, and a franchise is a first-class object that owns many of them.
How it works
Separate where it matters, joined where it helps
Each campus runs its own school — its own students, staff, timetable, exams and fee ledger. The group sits above them with a consolidated view and control of plans and limits.
Hard tenant isolation
Every request is scoped to a school before it touches data. A user in one campus cannot read another campus’s students, staff or announcements, and the check lives in the API rather than in the interface.
Campuses and education groups
Campuses and education groups are part of the data model, not a naming convention. Adding the eleventh school is the same operation as adding the second.
Per-school plans and limits
Plan, student limit and enabled modules are set per school, so a small new campus is not billed like an established one.
Consolidated reporting
Roll up enrolment, attendance, results and fee collection across the whole group, then drill into one campus without switching accounts.
Trackable referral links
Give each franchise or campaign its own signup link. Registrations are attributed to it, so you can tell which advert actually opened a school.
One rollout, every role
Staff, students and guardians at every campus get the same web dashboard and the same mobile apps — nothing is per-campus custom software to maintain.
Why isolation matters
Tested, not assumed
Multi-tenancy is easy to claim and hard to get right. The boundary is enforced on every request against the signed-in account, and access to an individual student is decided by the actual relationship — a guardian reaches the children linked to them and nobody else.
- Scoped per school on every API request, not per screen.
- A parent or student can never read another family’s child.
- Staff access stops at their own campus.
- Permissions are data; the relationship check is code, so re-granting a permission cannot open a hole.
Bringing a group across?
Tell us how many campuses, roughly how many students, and what you run today. We will size the plan against your actual roll and walk through migrating the first campus.