ShuleMetric
FeaturesSecurityPricingContact
Sign inGet started
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.

Tenant-aware data access
Server-enforced permissions
Auditable administrative actions
Security

Security principle

Defense-in-depth for tenant data and operations.

Server-side checks, tenant scoping, and audit records protect sensitive school workflows.

Security controls

Protection is enforced through the platform architecture.

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.

Discuss security
01

Server-side authorization

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

02

Tenant-scoped data

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

03

Platform audit trail

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

04

Verified account flow

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

05

Operational scripts

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

Defense in depth

Multiple controls protect every sensitive operation.

Identity, tenant context, permissions, workflow state, and audit history work together instead of depending on one security layer.

Server-enforced controls

Security principles

Clear boundaries between platform, school, and learner access.

Different users require different levels of visibility and authority. The platform keeps those responsibilities separate while preserving one connected examination workflow.

Tenant boundary

School-owned data remains attached to the correct school tenant and is accessed through tenant-aware queries.

Identity boundary

Verified authentication establishes who the user is before role and tenant permissions are evaluated.

Authorization boundary

Server-side checks determine whether a user can view, update, approve, or publish protected records.

Accountability boundary

Sensitive platform and school actions create records that can be reviewed later.

Production readiness

Operational safeguards matter after deployment.

Secure application code still depends on correct domains, database configuration, backups, delivery monitoring, and deployment procedures.

Contact support
01

Use HTTPS for the app

02

Keep Better Auth origins on the main app domain

03

Run MongoDB as Atlas or a replica set for transaction support

04

Create database indexes through deployment or admin scripts

05

Monitor email delivery, uploads, backups, and audit records

Security and governance

Build confidence into every school operation.

Contact the platform team to discuss tenant isolation, authentication, deployment requirements, and operational safeguards.

Talk to support
ShuleMetric

Secure, auditable, tenant-aware examination operations for schools and operators.

Product

FeaturesPricingSecurity

Company

AboutContactCareers

Contact

support@example.com

+1 (555) 123-4567

© 2026 ShuleMetric. All rights reserved.

Built for examination workflows, role clarity, and tenant safety.

PrivacyTermsSecurity