Questions schools usually ask before they trust an ERP with daily operations.

School Master is a multi-school product. Each customer school operates inside its own SchoolId-scoped workspace. The product is generic; no real data from a reference school is bundled into a new customer's workspace.

Not automatically. Teacher and staff accounts can be controlled by module permissions and class/division scope. A school owner or authorized admin decides which modules and classes a user can access.

No. Parent access is intentionally separated from teacher and office access. A verified parent identity opens only approved child links and parent-facing services.

Depending on enabled school features, a linked parent can view relevant attendance, fee information, finalized results, school notices and related parent services. Parent Portal does not provide general ERP administration rights.

Yes. Schools can use the official template or the flexible column-mapping flow. Custom headers are mapped to School Master fields, then the file passes through preview, duplicate checks, validation and transaction-safe import.

No. Mapping changes how incoming headers are interpreted; it does not disable duplicate protection, required-field validation or permission checks.

For an enrolled trusted PC, supported core ERP workflows can run in Local mode against SQLite. Local changes are queued and synchronized when connectivity returns. Cloud security and subscription entitlement remain authoritative.

No. Subscription edition is cloud-authoritative. Local devices cannot grant themselves a paid plan or alter cloud-managed user permissions.

Hybrid sync does not silently overwrite a detected disconnected conflict. The operator is shown a decision such as Keep Local or Use Cloud so the chosen version is explicit.

The cloud restore flow validates school identity and is designed to reject a cross-school restore. The release QA includes a synthetic School A/School B restore-block test.

The software workflow and language-routing logic are ready, but real delivery requires the school's or platform's approved Meta configuration, including WABA/Phone Number credentials, access token, webhook configuration and approved templates.

No. Core school operations are separate from optional commercial payment-provider setup. Online pricing and real Razorpay payments should only be presented as active after live credentials and webhook verification are configured.

No. Every customer school supplies and verifies its own logo, principal signature, stamp and official profile details. This avoids mixing one school's identity into another school's documents.

Usually no. A safer rollout is to standardize master data, import a verified sample, test daily workflows, and then bring in the remaining data in controlled batches with backup checkpoints.

Start with the School ERP implementation guide, then follow the topic guide for admissions, fees, attendance, results, parent access or Excel migration.