Core School ERP
Admissions, Students, Staff, Attendance, Fees, Expenses, Reports, academic workflows, permissions, audit, backup/restore and related operational modules are available subject to edition and user permissions.
School MasterThis page separates completed School Master capabilities from external-provider or school-specific setup. “Code ready” never means a third-party provider is connected.
Status updated: 27 August 2026Admissions, Students, Staff, Attendance, Fees, Expenses, Reports, academic workflows, permissions, audit, backup/restore and related operational modules are available subject to edition and user permissions.
Verified parent login, linked children, attendance, fees, results, leave/service requests, PTM, notices, homework/classwork, consent, pickup pass, gallery, library/transport, calendar, surveys and feedback are available. School Admin/Super Admin has a unified Parent Management Hub for parent access and parent-service controls.
Enrolled school PCs can use Local SQLite for supported offline operations, then securely push/pull tenant-scoped changes. Device enrollment, protected local token storage, conflict review, retry/idempotency, local backup and cloud-authoritative security/edition rules are included.
The top-bar bell opens a centralized attention view for platform announcements, pending/failed sync activity, conflicts and recent audited actions.
Schools can upload an existing .xlsx workbook, map common/custom headers to School Master fields, then use the same preview, validation, duplicate protection and transaction-safe import pipeline as the official template.
English, Hindi and Gujarati are available with per-user screen language, independent document language, school default language, global quick switching and English fallback.
Role permissions, class/division scopes, tracked sessions, sensitive-action verification, tenant filters, audit, restore safety and import transactions are implemented. Release CI includes software regression, Local SQLite startup, disposable PostgreSQL tenant/RBAC/backup-restore/load gates, desktop/tablet/mobile browser smoke and Docker build.
A separate internal marketing control room is available from the Platform Admin portal for the Platform Owner only. Platform-marketing records remain separate from customer-school ERP records.
Recipient language routing and workflow code are ready. Real sending/delivery tracking still require Meta WABA ID, Phone Number ID, permanent access token, approved language templates, webhook verify token and App Secret.
Secure billing/payment verification code is ready. Public commercial prices must be finalized and published, then live Razorpay Key ID, Key Secret and webhook secret must be configured before real payments.
Every customer school supplies and verifies its own student/staff/fee data, official profile, logo, principal signature and stamp. No real reference-school data is bundled, seeded or treated as product backlog.