Safe by default
Security & Roles
Tenant isolation, server-enforced permissions, session control, audit history, and honest provider boundaries.
The problem it solves
Role checks hidden only in the interface do not actually protect sensitive records.
Who uses it
Reports included
- Audit log
- Login history
- Session history
How it works
- 1Isolate every tenant to its own database and private storage
- 2Enforce permissions on the server for every request
- 3Manage sessions and revoke access immediately
- 4Record an audit trail for important changes
Frequently asked questions
Is tenant data ever shared?
No. Each institution is resolved to exactly one database and one private bucket per request.
Are permissions enforced server-side?
Yes. Role and relationship checks run on the server, not only in the interface.
Explore related modules
Administration & Setup
Set up academic years, boards, levels, programs, sections, rooms, and buildings, then control access and audit every change.
ExploreStudent Information System
A complete student profile with guardians, documents, enrollment history, awards, and health records, scoped to the institution.
ExploreAdmissions & CRM
Capture inquiries, assign follow-up, track consent, and convert qualified leads into enrolled students with a full audit trail.
Explore