Security
Security designed around institutional boundaries.
Institutional information stays within tenant, role and permission boundaries. Principles, not exploitable implementation details.
We do not claim ISO/SOC/government certifications unless documentary evidence exists — see verified disclosures only.
Tenant isolation
Institutional data boundaries enforced by design. No cross-tenant visibility.
Authorization
Every action checked against role and permission scope — campus, department, function.
Role-based access
Granular permissions by function, not just role name.
Permission architecture
Scopes include campus, department, programme and period.
Authentication
Secure, policy-driven access for every user.
Auditability
Administrative actions preserve actor, time and before/after context.
API security
Server-side boundaries keep institutional data protected and controlled.
Data handling
Institutional ownership boundaries respected; operational monitoring where confirmed.
Backups & recovery
Explained only where operationally confirmed — no unverified claims.
Tenant boundary visual (principles only)
Tenant A
Tenant B
No cross-tenant visibility. Public page explains principles — no IDs, secrets or internal architecture exposed.
