Set the shared frame.
Coordinate standards, access, and platform administration at the group — without turning every school into the same office.
Group viewOversight without mixing school records
School dataEach campus keeps its own boundary
Local workWorkflows stay with the school that runs them
Local identityName, mark, and colors per school
Built for groups and trusts
Central where it must be. Local where it should be.
Education groups have to balance oversight with campus independence. The multi-tenant model is the point: group administration on a shared platform, school operations in their own boundary.
Keep each school’s record its own.
Multi-tenant boundaries mean one school’s students, invoices, and staff do not spill into another.
Let campuses run the day.
Academics, teachers, calendars, billing, and purchasing stay in the school workspace that owns them.
Add a school without flattening the last one.
Onboard a new campus on the same platform. Branding and data stay local from the first day.
What the group model includes
Oversight, isolation, and a workspace per school.
These are the controls a group actually needs. We do not collapse every campus into one shared school record.
Group-wide operational viewSee how the group is organized without opening one school’s private record to another.
School-level data and permissionsEach school keeps its own tenant boundary and role-aware access.
Local workflowsClasses, finance, and work queues stay with the campus that runs them.
Distinct workspace identityEach school can present its own name, mark, colors, and themes.
Shared platform servicesAuthentication, storage, notifications, and audit sit on the common foundation.
Scoped rolloutA group quote can name the schools in sequence, not a single flattened tenant.
Lead the group. Leave each school room to be itself.
How it fits
The group holds the platform. The school holds the day.
Campuses still run academics and operations. Teachers still work from their school record. The quote can name the schools you will bring on, in order.
01What a school still ownsAcademics, operations, branding, and day-to-day work stay in the school workspace.See the school platform 02What teachers still useClasses, curriculum, lesson plans, and calendars remain a campus path — not a group inbox.See the teacher workspace 03How pricing follows the groupA quote can cover the schools in scope, shared governance, and the planned rollout sequence.Read how quotes are built
A responsible group foundation
Visibility without a shared pile of records.
The architecture is the product promise: group governance, school isolation, and room to add a campus later.
Oversight is not a shared database
Group leaders need visibility. They do not need every school’s records in one pile.
Identity stays local
A trust can share a platform without asking every campus to wear the same digital uniform.
Growth does not rewrite the last school
Adding a campus should not flatten branding, permissions, or data the first school already earned.
Scale your group on one platform
Request a demo to see multi-school oversight without flattening campus identity or mixing school data.