ZSchool4u Docs
Open app

Getting started with ZSchool4u

ZSchool4u is a multi-tenant school ERP for Indian schools: attendance, academics, fees & salary, parent communication, and staff ops — one product, many schools, each isolated by school_id.

You use it on:

  • Web portal — full school operations (/portal/...)
  • Android APK — day-to-day for leadership, teachers, parents, and students (subset of web menus)

This documentation is written for school owners and staff. After one pass through Getting Started, you should know who logs in as what and where money / approvals / attendance sit.

Who this is for

| You are… | Start here | | --- | --- | | School owner / School Admin | Who does whatSchool Admin | | Fee counter / Accountant | Who does whatAccountant | | Principal / Vice Principal | Principal · Vice Principal | | Class Teacher | Class Teacher | | Parent / Student | Parents & students |

Your school tenant

ZSchool4u is multi-tenant: the platform creates your school record. After that, school_admin owns day-to-day setup inside that school only — employees, students, fees, and menus never leak to another school.

What school_admin does first week:

  1. School & print setup — profile, logo, receipt layouts.
  2. Classes, fee structure, and staff logins (especially an Accountant).
  3. Enroll students and hand parents their login.

You do not need a separate “create tenant” screen in the school portal — provisioning is handled when your school is onboarded onto the platform.

How schools are isolated

Each school is a tenant. Users, students, fees, wallets, timetables, and salaries never mix across schools. Staff always work inside their own school context.

Suggested reading order (one sitting)

  1. This page — what the product is and how your tenant works
  2. System requirements — browsers, HTTPS, printers, APK
  3. Login — web + Android sign-in
  4. Who does what — capability matrix + maker-checker (read this fully)
  5. Roles & permissions — every seeded role + guide links
  6. Your role guide (Admin / Accountant / Principal / Teacher / Parent)
  7. Fee collection workflow — cash, wallet, promises, receipts

Golden rules for school owners

  1. Do not share the School Admin login with the fee counter. Create an Accountant user for daily collect.
  2. Accountant proposes sensitive finance changes; School Admin approves (maker–checker).
  3. On web, Principal / VP do not get Account Section or Approvals — fees stay with Accountant + Admin.
  4. Staff menus can be customized with menu ACL when adding/editing employees — defaults are a starting point, not a hard ceiling (except a few hard blocks such as accountant cannot delete students/employees).

App access

Open the live ERP from the header Open app button. Set NEXT_PUBLIC_APP_URL to your web portal origin so links point at the right host.

Next

System requirements · Login · Who does what