FOR SCHOOL GROUPS
Give a school group shared governance without erasing school ownership.
Coordinate organization-level governance and school-level operations with explicit tenant, role, reporting, and rollout boundaries.
Before you begin
- Defined organization and school hierarchy
- Named central and school-level owners
- Approved cross-school data and reporting rules
Organization and school boundaries
Group governance may need shared policies and reporting while each school retains its own users, academic context, operating records, and accountable leaders.
Phased rollout by readiness
A group rollout can establish common identity and governance first, then onboard schools in controlled waves based on data, training, integration, and support readiness.
Cross-school reporting needs explicit scope
Organization-level views should only aggregate approved information and must preserve source-school context, metric definitions, and access authorization.
Scope and limitations
- Cross-school access is not granted automatically.
- Data migration and module readiness can differ by school and must be validated separately.
Related Anabhix guidance
- See Anabhix in action
- School management software for connected, accountable operations.
- Reporting that keeps source context, scope, and responsibility visible.
- School people operations with explicit ownership and approval boundaries.
- Tenant context defines the institution boundary for operational data.
- Create the organization boundary before adding member schools.
- Permissions are evaluated in context, not inferred from a page label.