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 access control
Every read and write is checked on the server — through database security rules or server-side functions — not just in the app's interface. What your role and school allow is verified again each time, never assumed from what buttons you can see.
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.