School MasterThese terms summarize the operational rules built into the product. Schools remain responsible for verifying official records, assigning appropriate access, protecting local devices and configuring optional providers correctly.
Last updated: 27 August 2026Use School Master only for legitimate school administration and only with accounts, permissions and data you are authorized to access. Do not attempt to bypass tenant boundaries, role permissions, security verification or audit controls.
Each school is responsible for verifying official student GR numbers, class/division assignments, staff identities, fee references, opening balances and other authoritative records before importing or publishing them.
Parent accounts should be linked only after the school verifies the parent identity and child relationship. Parents may view linked-child data and submit only school-approved parent workflows; Parent Portal access remains separate from staff ERP access.
Column mapping is a compatibility tool, not a data-guessing tool. Schools must verify that each source column is mapped to the correct School Master field before preview/import. Required-field, duplicate and transactional safety checks still apply.
Schools using Local mode are responsible for physical access to the enrolled PC and secure storage of local backups. Offline changes should be synchronized regularly, and surfaced conflicts should be reviewed rather than bypassed.
Paid status must not be confirmed unless payment is actually verified. Online pricing should be published only after the platform owner has finalized commercial values. Provider credentials and webhook secrets must be configured securely.
WhatsApp automation depends on Meta approval, credentials, approved templates and webhook setup. A code-ready integration is not the same as an active provider connection. Schools are responsible for appropriate recipient data and lawful messaging use.
Preview and validate imports before writing production data. Restore is consequential and should be used only with a verified backup and intentional recovery plan. Invalid or incomplete authoritative data should be corrected rather than guessed.
Some functions depend on hosting, database, email, Google, Meta, Razorpay or other third-party services. Their availability, approval and service terms can affect the corresponding School Master feature.
Feature availability can depend on the active School Master edition, permissions and platform flags. A feature may be present in the software but remain unavailable until the required plan, permission or provider setup is active.