Separate, not just partitioned
Every school runs on its own database rather than sharing one store with other schools.
- Tenant isolation
- Independent records
- Controlled provisioning
Security and data
Each school's data sits on its own database
XULE gives every school its own database, role-based access, OTP verification, a full audit trail and clear ownership of its data.
XULE for Kenyan schools
Secure · Cloud-hosted · Mobile-ready
A database per school
Access by role
OTP verification
Full audit trail
How it fits together
How this fits into the rest of XULE.
Every part of XULE shares the same roles, the same learner records and the same reporting, so nothing sits on its own.
You only reach what your role needs
Each user gets the functions and records that go with their job, and no more.
- Role permissions
- Parent OTP links
- Jurisdiction controls
A trail for the things that matter
Audit records let leaders see what changed and who changed it.
- User activity
- Sensitive changes
- Security review
Frequently asked
Questions about security and data.
Answers for school leaders and the teams who run the day to day.
Can one school see another school's data?
No. Each school's operational database is isolated from the rest.
Does robots.txt protect private data?
No. Private data is protected by authentication, permissions and database controls. robots.txt only affects indexing.
Who owns the records?
The school does, subject to the service agreement and the law.
Start with your school
Ready to run your school from one system?
Register your school for guided onboarding, or ask for a demo before you decide.