Skip to main content
Version: Next

Schools, branches, and access

Definition​

A tenant is your organization or group (for example a trust or multi‑school group). A school is the operating unit inside the tenant. Some schools have multiple campuses or branches, but they still roll up to one school record.

Why it matters​

Your school structure affects:

  • Who can see what
  • Where students are registered
  • How reporting is grouped
  • Which modules are visible (some modules require a school selection)

What you should decide first​

  • Do you operate as one school or multiple schools within a tenant?
  • Which users can access which schools?
  • Which teams need cross‑school views (oversight or multi‑school executives)?

How access works in the system​

  • The sidebar and modules are built from tenantNavigation and filtered by audience, permissions, and school selection.
  • Some areas are tenant‑wide (Foundation, Identity & Access), others require a school (People, Finance, Attendance).
  • When a school is required, you must select it in the top bar switcher.

Routing and workspace behavior​

  • The app is tenant‑aware. URLs are mapped to your tenant and school context.
  • If your tenant uses the default workspace path, URLs start with /workspace and are rewritten to your tenant context behind the scenes.

Common misunderstandings​

  • A branch is not a class.
  • A tenant is not a school.
  • A school account is not the same as an individual staff member’s login.