FAQ
The questions schools ask first
Straight answers on your data, weak connections, your existing records, languages and who can see what.
Can another school see our data?
No. Every record carries the school it belongs to, and the filter is applied in the query layer rather than in the pages, so a page that forgets to ask still cannot return another school's rows. When no school is in context the filter matches nothing at all: the failure mode is an empty screen, never a leak. A test suite creates two schools with full records in each and asserts that neither can read, reach or write the other through the API, the detail pages, the editing endpoints and every form dropdown.
What happens on a weak connection?
Pages are rendered on the server and compressed, and static files are cached for a year against a fingerprinted URL, so a repeat visit to a parent page is the HTML alone: about 4 KB. The parent portal carries no CSS framework and inlines the icons it needs rather than fetching a sprite.
We already have everything in Excel. Do we retype it?
No. Download a template, fill it or paste your existing sheet into it, upload, and you get a preview of what will be created or changed before anything is committed. Students, guardians, teachers, staff, subjects, class levels and classes are all importable, and the column headings are recognised in English and French.
Can we get our data out?
Every list page exports CSV. There is no export fee and no notice period.
Which languages?
English and French. The app itself is being translated portal by portal; these public pages and the parent-facing screens come first, because those are what families read.
Who can see what?
Permissions are a grid of twenty-six modules by five actions, editable per role and per school, so a bursar, a class teacher and a librarian each get what they need. On top of that, rows are scoped: a parent sees their own children, a student sees themselves. Hiding a menu item is presentation only; every page re-checks its own permission on the server.
Is there a mobile app?
The parent portal installs from the browser onto an Android home screen: its own icon, its own window, no address bar. There is no Play Store listing and no separate codebase. This requires the app to be served over HTTPS; on a plain HTTP address the browser declines to install it.
Who is behind it?
A small team building it against real Cameroon schools rather than against a spec. If something here is wrong about how your school works, tell us and we will change it.
Set up your school and look around
Registration creates an empty school that only you can see. Nothing is shared with any other school on the platform, and there is nothing to cancel.