Modules and supported boundaries
Plan onboarding around enabled capabilities and clearly identified workflow limits.
Institution profile, module state, subscription entitlement, country settings and user permissions each affect availability. They are related controls, not interchangeable switches.
Profiles and modules
The school and higher education profiles select the appropriate workspace and defaults. They do not replace programme award rules or determine GPA merely from the institution label.
Transport and hostel are the current switchable modules. An administrator enables or disables them; disabling keeps their data. Paid subscriptions can require the matching add-on entitlement. Other documented feature areas are not automatically independently installable modules.
Limits to include in your rollout
| Area | Current supported boundary |
|---|---|
| New institution access | Marketing routes new institutions to a demo while self-registration is closed |
| Online exams | Built-in online exam delivery is retired; assessment and mark entry remain |
| Generated school report cards | Generation currently grades session-wide rather than an isolated selected term |
| Public API | v1 is read-only; no general public write API |
| Course fees | No automatic per-course or per-credit-unit billing |
| External admissions | Mapped files and status tracking, without live CAPS or ministry APIs |
| Transcript payment | Staff-confirmed payment; no transcript-specific online checkout |
| Refunds | Accounting workflow; actual disbursement is handled separately |
| SIWES participation | Institution-entered records; no employer portal or student logbook editing |
| Affiliated programmes | Institution’s own approval ladder and manual partner remittance |
| Accreditation returns | Configurable exports; official mappings require institution confirmation |
Confirm specialized requirements
NCE and nursing award rules have editable defaults requiring institutional confirmation. Dedicated teaching-practice, clinical-posting and council-examination workflows are not built. A programme award entry is not evidence that every profession-specific process exists.
Part-time enrollment load is supported separately from programme delivery mode. Regular and sandwich modes are modeled; dedicated distance or part-time programme delivery modes are not.
Use the guides as an implementation reference
These pages describe code reviewed on 23 October 2026, not a guarantee that every provider or production tenant has been configured. Agree required integrations, payment setup, result policy and specialist workflows during onboarding. Ask the Takadar team about a missing requirement before designing a process around it.