Transport and hostel operations
Enable the modules, load dependencies and keep route or room allocations accurate.
Transport and hostel are the two currently switchable modules. An institution administrator must enable them and the organization must meet applicable subscription entitlement rules. The operational role still needs the relevant module permissions.
Set up transport
Prepare vehicles, then routes and their stops, then student assignments. Supported import pages follow this order. Confirm the student’s session and chosen route before assigning them.
Use the saved route and vehicle records to keep the institution’s operational lists consistent. These records support school transport administration; they do not imply live GPS tracking or a separate driver-navigation service.
Set up a hostel
Create hostels and rooms before allocating students. The supported imports cover hostel records, rooms and session allocations. An allocation refuses a full room and a student who already has a room in the relevant context.
Where hostel applications are used, decide the application before completing the accommodation work. Review capacity and existing allocations when a room appears unavailable rather than creating a duplicate student.
Connect the operational and financial work
Check the intended session for allocations and any related fees. Recording a room or route does not replace finance review of the applicable bill. Graduation hostel clearance is also its own signing-office decision.
Turn a module off
Disabling a module gates its pages and API routes while keeping existing data. It does not delete transport or accommodation history. Re-enabling still depends on the administrator’s setting and applicable entitlement. If the menu is missing, check module state, subscription and role permissions before assuming the records were lost.