Server-side authorization
Protected pages, server actions, uploads, and route handlers validate role and tenant context before sensitive work runs.
The platform keeps public access, school access, and platform-owner access separate, with sensitive actions checked on the server.
Security principle
Defense-in-depth for tenant data and operations.
Server-side checks, tenant scoping, and audit records protect sensitive school workflows.
Security controls
Security is not limited to hiding buttons in the interface. Tenant context, user role, workflow state, and privileged actions are validated before protected operations are completed.
Protected pages, server actions, uploads, and route handlers validate role and tenant context before sensitive work runs.
School-owned records carry tenant identifiers and are queried through tenant-aware access paths.
School approvals, school status changes, and platform role changes create auditable records.
Authentication uses email verification, password reset protections, and main-domain auth redirects.
First-owner bootstrap and learner portal index setup are explicit operations, not hidden request-time mutations.
Identity, tenant context, permissions, workflow state, and audit history work together instead of depending on one security layer.
Security principles
Different users require different levels of visibility and authority. The platform keeps those responsibilities separate while preserving one connected examination workflow.
School-owned data remains attached to the correct school tenant and is accessed through tenant-aware queries.
Verified authentication establishes who the user is before role and tenant permissions are evaluated.
Server-side checks determine whether a user can view, update, approve, or publish protected records.
Sensitive platform and school actions create records that can be reviewed later.
Production readiness
Secure application code still depends on correct domains, database configuration, backups, delivery monitoring, and deployment procedures.
Contact supportUse HTTPS for the app
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
Contact the platform team to discuss tenant isolation, authentication, deployment requirements, and operational safeguards.