SemwakiBuilt with access control at its core
Every action in Semwaki is checked against a role, a tenant, and a permission — by design, not as an afterthought.
Multi-tenant data isolation
Every school's data is scoped to that school. A user at one school cannot read or write another school's records.
Role-based access control
Super Admin, School Admin, Principal, Deputy Principal, Registrar, Accountant, Teacher, Parent, and Student each see only what their role permits.
Server-enforced security rules
Access rules are enforced at the database level, not just in the app's interface — the same rule that governs what you see also governs what your browser is allowed to write.
Audit trail
Key actions across the platform are recorded with who did what and when, supporting accountability and traceability.
Semwaki does not currently hold a third-party security certification (e.g. SOC 2, ISO 27001) — this page describes the platform's actual architecture, not a compliance claim.