How it works
Three steps, start to finish.
- 1
Batches and semesters
A batch's dates decide which semester it's in, and its course pack decides what it studies. Promote, transfer and enrol in bulk.
- 2
People and powers
Admins, teachers, students and parents, with approvals for teachers and parents. Heads of department act for their department; teachers see their own batches.
- 3
Your words, your switches
Call a course a subject or a student a learner, everywhere. Turn features on or off; off means off.
What you get with school administration.
Dates decide
Semesters follow each batch's calendar; a daily job keeps them current.
Departments
Heads review plans, maintain batches and see their results.
Audit log
Every change is logged with who, what and when.
A bin
Deleted things go to a bin first and can be restored.
APIs and webhooks
Connect your other systems, behind switches.
Your own deployment
Each school runs separately, with its own address and data.
How it compares.
Fair, sourced comparisons with the tools schools weigh this against, checked on their own sites.
Questions about school administration
Can we use our own terms?
Yes. Schools can rename words like course, batch or student, and the app uses them on screen, in print and in email.
Can we turn features off?
Yes. Every feature has a switch, enforced on pages and on the server.
Is every action logged?
Yes. Changes are written to an activity log with the person, the action and the time.
Is our data separate from other schools?
Yes. Each school runs its own deployment with its own address.
Goes well with.
Across SparkMentis
See it with your school.
Tell us about your school and we'll walk you through a term with your own classes and papers.