Reference
The feature catalogue
The six standardized features the platform recognises, what enabling one means, and why the key is the only name accepted.
A school does not have a menu of modules. It has six standardized features, each with a stable key, and the platform either gives it one or does not. This page is the catalogue, and it is short on purpose.
| Key | Feature | What it covers |
|---|---|---|
students |
Students | Student records, enrolment and student numbering |
staff |
Staff | Teacher and staff records and their assignments |
classes |
Classes | Academic structure: years, terms, classes and subjects |
assessments |
Assessments | Assessments and the grading configuration behind them |
results |
Results | Grade capture, result calculation and publication |
promotion |
Promotion & ranking | Ranking and end-of-year promotion decisions |
What enabling a feature means
A feature is a capability, not a screen. A school without results cannot publish a result set; a school without
promotion has no ranking. The keys are what the boundary accepts: a value outside the catalogue is refused as a
validation failure rather than stored for later interpretation, which is why the list is closed rather than open.
Why the list is standardized
An open list of feature names would be six names in one school and six different names in the next, and a support question
would start with a translation exercise. A closed list means every deployment means the same thing by assessments.
The platform console reads this catalogue rather than hard-coding it, and a change to a school's features is recorded with the version of the school's settings that was read, so two operators editing at once cannot silently overwrite each other.