Security

Designed for tenant safety, role clarity, and accountable operations.

The platform keeps public access, school access, and platform-owner access separate, with sensitive actions checked on the server.

Server-side authorization

Protected pages, server actions, uploads, and route handlers validate role and tenant context before sensitive work runs.

Tenant-scoped data

School-owned records carry tenant identifiers and are queried through tenant-aware access paths.

Platform audit trail

School approvals, school status changes, and platform role changes create auditable records.

Verified account flow

Authentication uses email verification, password reset protections, and main-domain auth redirects.

Operational scripts

First-owner bootstrap and learner portal index setup are explicit operations, not hidden request-time mutations.

Production readiness checklist

These operational requirements keep school domains, data writes, and recovery paths predictable.

Use HTTPS for the main app and wildcard school domains

Keep Better Auth origins on the main app domain

Run MongoDB as Atlas or a replica set for transaction support

Create database indexes through deployment or admin scripts

Monitor email delivery, uploads, backups, and audit records