Multi-school operations
Run separate school workspaces with tenant-aware roles, domains, profiles, and approvals.
The platform connects tenant governance, academic setup, mark entry, approval, result calculation, and learner access without mixing school data.
Core capability
Connected workflows from setup to published results.
Tenant-aware governance, role boundaries, and auditability are built-in across the platform.
Core platform capabilities
Instead of treating school setup, mark entry, permissions, and results as separate tools, the platform keeps them within one controlled operational flow.
Run separate school workspaces with tenant-aware roles, domains, profiles, and approvals.
Create academic years, terms, streams, learning areas, exams, mark sheets, and result cycles.
Teachers enter marks by assignment, submit complete sheets, and administrators approve final records.
Track active learners, enrollments, guardians, portal access, published results, and transfers.
Platform owners review school applications, suspend tenants, manage support access, and audit decisions.
Separate permissions for owners, admins, exam teams, teachers, class teachers, learners, and guardians.
Operational workflows
Each area has a clear owner, status, and server-side permission boundary before sensitive school data can change.
Governance is built in
The platform validates roles, tenant context, and workflow state before protected actions are completed.
Control how schools enter the platform and how privileged access is granted.
Build the academic structure that every examination workflow depends on.
Move examination work from configuration to reviewed and approved marks.
Publish approved academic records to the correct learners and guardians.
Academic records, users, marks, approvals, and published results remain connected to the correct school workspace from setup to learner access.
Approved schools receive a dedicated workspace with tenant-aware academic, examination, and user-management controls.