An education trust rarely starts with three campuses. It starts with one, adds a second when a neighbouring institute folds, and acquires a third when a family retires. By the time the group dashboard exists, four systems and three fee cycles need to agree with each other, and the newest campus is understandably nervous about who can read its student records.
Two levels, not one
The model that works has two boundaries. The tenant represents the trust and owns billing, staff identities and group reporting. The institution represents a campus and owns its sessions, admission numbering, fee plans and receipts. Every business record belongs to a tenant, and every institution-scoped record also carries its institution.
That second field is what most homegrown systems skip. They scope by trust, then filter by campus in the interface. The moment someone edits a URL or calls the API directly, the filter is gone.
Where isolation actually gets enforced
- In the query layer, where the tenant and institution are taken from the session rather than from the request body.
- In permission checks, where a principal’s role is valid only for their own institution.
- In file access, where documents are served through short-lived signed URLs tied to the requesting user’s scope.
- In exports, where a filtered report must not quietly widen to the whole tenant.
Hiding a menu item is a UI decision. Scoping a query is a security decision. Groups need both, in that order of importance.
What a group owner should be able to see
- Enrolment by campus and by class, with the same definition of enrolment everywhere.
- Attendance percentages computed from the same rule, not from three different exports.
- Collections and outstanding dues per institution, reconciling to numbered receipts.
- A drill-down to a single student or receipt, without needing a login to that campus.
The drill-down is where most reporting tools stop. A group total that cannot be traced to a receipt is a number the owner has to trust, and trust is not a reporting feature.
Shared templates without shared records
Groups want consistency: the same fee head names, the same grading vocabulary, the same notice structure. Publish those as templates from the group to selected institutions. What must not be shared is the data itself — a template sets the shape, while each campus keeps its own rows, numbering and history.
Test the boundary before you trust it
Ask two questions of any system before rollout: can a principal from campus A retrieve campus B’s fee ledger by changing an identifier in a request, and can a group export accidentally include a campus the user was not granted? If the answer to either is yes, the dashboard is the least of the problems.
Acadelogy team · 16 Oct 2026