ANABHIX DOCUMENTATION
Find the right Anabhix guidance for the task in front of you.
Browse public documentation by getting-started task, platform concept, module, role, developer topic, security question, or troubleshooting need.
Explore documentation
- Understand the platform boundaries before configuring a school.
Understand how Anabhix products use organization, institution, user, role, module, workflow, and integration context.
- Create the organization boundary before adding member schools.
Plan and create the organization context used to govern one or more Anabhix schools when that structure is part of the approved setup.
- Check for an existing school before starting a second setup.
Create a new school or recover an existing school association without duplicating an institution record.
- Establish the academic context before recording daily operations.
Prepare the academic year, periods, class context, and responsible owners needed by school modules.
- Invite users after roles and institution boundaries are defined.
Invite approved users into the correct Anabhix institution context and assign only the roles needed for their responsibilities.
- Tenant context defines the institution boundary for operational data.
Understand how Anabhix uses tenant, organization, school, identity, and service context to separate institution operations.
- A role represents responsibility; it is not a shortcut around authorization.
Understand how roles describe responsibilities within platform, organization, school, and module context.
- Permissions are evaluated in context, not inferred from a page label.
Learn how identity, role, institution context, service policy, and workflow state combine to authorize Anabhix actions.
- Organize admissions around stages, evidence, owners, and decisions.
Understand the admissions journey from enquiry and application through review, decision, and approved student-record handoff.
- Record attendance only after academic and assignment context is ready.
Understand attendance prerequisites, recording context, review, correction, and reporting responsibilities in Anabhix Education.
- Configure approved fee rules before creating operational finance records.
Understand fee structure, assignment, collection records, dues, receipts, adjustments, and review boundaries in Anabhix Education.
- Operate the school context without bypassing module owners.
Understand the school administrator responsibilities for setup, users, roles, modules, data quality, review, and support.
- Work from assigned classes, subjects, learners, and tasks.
Understand how teachers confirm assignments, work in the correct academic context, record authorized information, and request support.
- Begin an integration with an approved contract, not a guessed endpoint.
Prepare an approved Anabhix integration by defining the use case, data contract, identity, environment, test evidence, and operational ownership.
- Use environment-specific, least-privilege credentials through an approved flow.
Understand the public security model for authorized Anabhix API access without exposing credentials, private endpoints, or internal policies.
- Treat a webhook as an operational contract with failure handling.
Plan secure webhook delivery, verification, retries, idempotency, monitoring, and support before enabling an Anabhix event integration.
- Public API reference is released only from reviewed OpenAPI sources.
Review how public Anabhix API reference material is approved and request the correct integration documentation for an authorized use case.
- Connect systems only after ownership and data boundaries are clear.
Plan Anabhix integrations around system ownership, data contracts, authorization, validation, observability, failure recovery, and change control.
- Security depends on layered technical and operational controls.
Review public Anabhix security concepts for identity, authorization, tenant boundaries, data handling, delivery, operations, and safe support.
- Check identity, school context, role, route, and service state in that order.
Resolve common sign-in, school association, permission, stale-session, and setup issues without exposing credentials or creating duplicate records.
- Release notes publish customer-relevant change after review.
Understand the release-note policy and find reviewed public changes that affect Anabhix customers and documented workflows.
- Direct answers about using Anabhix documentation.
Find direct answers about documentation scope, account access, existing-school setup, roles, modules, APIs, and support.
Start with setup
Understand the platform, establish organization and school context, configure an academic year, and invite users through an approved onboarding path. Follow prerequisites in sequence so later module records use the correct institution context.
Browse by responsibility
Use module and role guidance to understand prerequisites, boundaries, expected results, and the next task without exposing private institution information.
Developer and trust guidance
Review the public integration, authentication, webhook, API-status, security, and troubleshooting guidance before requesting environment-specific access. Public documentation explains concepts and boundaries; private credentials and tenant-specific configuration use authorized channels.