A school is one community: its office, its teachers, its students and their families. Schoolak gives them one place to work together, where each person sees what is theirs to see.
Many schools run on a patchwork: a student system here, a fee ledger there, timetables in spreadsheets and conversations scattered across personal phones. Each tool works on its own, and the child, the class and the family fall into the gaps between them. Schoolak puts that work in one place, in Arabic, English and French.
InsteadOne record for each child, seen by the people who should see it
Four kinds of people share a school’s information. Each one opens Schoolak to their own part of it.
Enrol students, review applications, and keep fees, staff and the timetable in one place. Decide who may see and do what, role by role. Term results reach families only once you approve and publish them.
Take the register, set homework, and watch marks from homework and exams gather in one gradebook. Mark a submission and leave feedback that the student and their family can read.
See what is due, hand homework in and read your teacher’s feedback. Sit exams on a computer or a phone: answers save as you go, and the exam keeps its own time. See your results once the school publishes them.
Follow your own child’s attendance, homework and published results — never anyone else’s. If your child is marked absent, the app tells you, and you can send the excuse from there. Notices and messages from the school arrive in the same place.
A future where every school can operate clearly, educators can focus on teaching, and families remain connected to each student’s journey.
To give schools a practical, secure, multilingual platform that replaces fragmented daily work with one connected system.
The rules the product is designed by, and what each one means for your school.
Administration, communication, safety, transport and family engagement run on one platform.
Every school is kept logically apart from every other, while the platform itself is run centrally.
A school changes its own settings, workflows and permissions — without anyone writing code.
No page, action, export or sensitive field opens on a job title alone: every access is checked against a permission.
Who made the change, when, and what changed.
Above all for students, photographs, transport, medical notes and guardians’ details.
Each module and feature can be switched on or off, limited, tried out, or offered as part of a plan.
What families, students and teachers do every day works in the Schoolak phone app as well as on the website; a few office tasks, such as admissions and hiring, are on the website only.
The platform’s protections, grouped by what they protect. Open a group to read how each one works.
Multi-tenant isolation
Every school is an isolated tenant. A record that belongs to another school answers “not found” — never a hint that it exists.
Permission, scope and relationship
Access is a permission, a scope and a real relationship — a teacher sees only assigned sections, a guardian only linked children.
A delegation ceiling
The platform caps which permissions a school’s own administrators may hand out; a school cannot grant what it was never allowed to delegate.
Search within your authority
Search only finds what you could already open; health, behaviour and message bodies are never indexed.
Live session checks
Every request re-checks that the session and the account are still live, so revoking a device or disabling an account takes effect immediately.
Session policies
Schools set inactivity timeouts, maximum session age and concurrent-session limits; refresh tokens rotate and reuse is detected.
Lockout without enumeration
Repeated failed log-in attempts lock the account without letting a stranger lock out its owner, and no response reveals whether an address has an account.
Rate limiting
Log-in, password reset, invitation and token endpoints are rate-limited per address and per subject, with an honest Retry-After.
A Login ID, email optional
Everyone signs in with an 11-digit Login ID, so an email address is optional; someone without one gets a reset code from staff at their school.
Single-use links
Reset and invitation links are single-use, expiring and stored only as hashes; invitation mail is queued durably and retried, and delivery is reported truthfully.
Malware scanning
Every uploaded file is scanned before anyone can open it; an infected file is quarantined, and a scanner error is never treated as clean.
File access through the record
A file carries no authority of its own: access is decided by the record it belongs to, links are short-lived and signed, and every download is logged.
Audit inside the transaction
Important changes are audited in the same transaction that makes them: if the audit cannot be written, the change does not happen.
Explicit support access
Schoolak staff have no back door: support access is explicit, time-boxed, read-only, limited to one school and a small set of read keys, and audited on every request.
Lifecycle enforcement
A suspended or archived school stops answering on the next request, for its users, for background jobs and for support access alike.
Modules enforced on the server
Modules are enforced on the server, not hidden in the interface, and a feature that is not built cannot be switched on or billed.
A separate integration credential system
Integrations use their own hashed, tenant-bound API keys with daily quotas, and webhooks are signed and protected against server-side request forgery.
Engineering gates
Migration history is immutable and replayed on every build; secrets are scanned, dependencies checked and static analysis runs on every change.
See each part of the product in the room where it is used, or walk through the school in 3D — every door opens onto a part of Schoolak.
