FOR SCHOOL ADMINISTRATORS
The setup checklist that gets a school from empty tenant to first working day.
School administrators own configuration. Setup shows progress against required steps — academic year, classes and sections, subjects, fee structure, and grading system — followed by roles and permissions and email and SMS settings.
Before you begin
- Current student and staff lists
- This year’s class structure, subjects, and fee heads
- A list of who needs which role
Five required setup steps
Setup tracks the academic year with its terms, classes and sections, the subject catalogue, the fee structure with heads and amounts, and the grading scale with GPA values. Each is marked required, so the overview shows what still blocks go-live.
Roles and permissions
Roles decide which modules and tabs each person sees. A teacher, an accountant, and a warden reach different screens, and actions such as ID-card printing, payroll approval, or campaign sending can be limited to named roles.
Getting data in
Students can be imported from CSV with a report of rejected rows, and admitted applicants flow into student records without re-entry.
Scope and limitations
- Administrator access does not replace the sign-off of the finance, HR, or examination owners for their own records.
- School profile and branding are edited in Configuration, separately from the setup checklist.
Related Anabhix guidance
- A school ERP implementation checklist that survives contact with a real school.
- One student record from admission to promotion, with every change on file.
- School management software for connected, accountable operations.
- Operate the school context without bypassing module owners.
- Invite users after roles and institution boundaries are defined.
- A role represents responsibility; it is not a shortcut around authorization.