Use this layout for a real docs site (each card can link to a separate page later).
Roles, permissions, departments, academic years, and governance setup.
Applications, enrollment workflows, IDs, documents, and transcripts.
Programs, curricula, timetables, attendance, grading, and results.
Fee structures, invoices, receipts, sponsors, reconciliation, and reports.
Courses, content, assignments, quizzes, gradebook, and publishing.
Cloud vs on‑prem, backups, environment setup, and hardening checklists.
If you share your modules and workflows, we can generate full docs pages and link them properly.
Use this page as a complete structure for your real docs. You can keep everything as static pages or later move it into a docs generator.
For a clean rollout, keep your docs aligned with departments: Registrar, Bursary, Academic Affairs, HR, ICT, and Students. Each section below includes what that team needs day-to-day.
What to do in the first week so you don’t waste time later.
Recommended approach for moving from spreadsheets or legacy systems.
Fix duplicates, ensure unique student numbers, normalize program codes, and agree on naming conventions before import.
Students → programs → courses → balances → historical results. Validate each stage with department sign‑off.
Record who approved imports and changes. This reduces disputes later and supports internal audits.
For institutions that want deeper integrations, we support structured APIs and event notifications.
Payment received • Admission approved • Results published • Invoice generated • Student enrolled • User role changed. These can trigger external systems (SMS gateways, finance exports, BI dashboards).
We can publish a branded knowledge base (staff + student) with your policies, steps, and support contacts.