One guardian, however many children, one account.
A guardian with three children in the school does not need three logins. They sign in once and switch between their children, and a second child is linked to their existing account by a verified code rather than by creating a duplicate.
Msomi identifies people at platform level rather than per school, so a teacher at one school who is a parent at another has a single identity and a single sign-in, with a school picker rather than two accounts.
The school creates the guardian record; the guardian claims the account with a one-time code sent to their phone or email and sets their own password. The school never holds a parent's password.
Guardian records are where school databases usually become duplicated. A family with three children ends up as three parent records with slightly different spellings, and a message intended for one household goes out three times.
Msomi links guardians to learners as a relationship rather than as a copied field. One guardian record can carry any number of children; one learner can have any number of guardians, with a designated primary contact for notifications.
Underneath, Msomi identifies a person once across the whole platform rather than once per school. That sounds like an implementation detail and is in fact one of the system’s most useful properties: a teacher at one school who is also a parent at another has a single identity and a single sign-in, and simply chooses which school they are looking at.
The school enters the guardian’s details; the guardian receives a one-time code by SMS or email, verifies it and sets their own password. Adding a second child later uses the same verified mechanism. The school never sees or sets a guardian’s password.
A demo runs about forty minutes and uses your own class lists, frameworks and grading — so you are looking at your school rather than a sample database.
Or try it first — the Trial tier gives you a full term, free, with every module unlocked.
