GETTING STARTED

Understand the platform boundaries before configuring a school.

Anabhix connects product experiences to shared identity and organization context while each service remains responsible for its own operational data.

View documentation

Before you begin

  • A confirmed Anabhix product and onboarding path

Core concepts

An organization can provide group-level context. A school or tenant provides an institution boundary. Users receive roles and permissions within that context. Modules organize operational capabilities such as admissions, attendance, fees, academics, and communication.

How requests are scoped

A signed-in request carries identity and authorization context. Services validate the relevant tenant or institution scope before returning or changing operational information.

Recommended starting sequence

Confirm the organization and school, establish the academic structure, assign accountable roles, enable approved modules, validate data, test workflows, train users, and review launch readiness.

Scope and limitations

  • Available products, modules, and roles depend on the approved environment and plan.

Related Anabhix guidance