People — students, guardians and staff

Everybody the school holds a record for.

Registering someone is one transaction

Creating a student creates the student, their guardian links and their enrolment together, or creates nothing. There is no half-registered state to clean up afterwards.

The same applies to staff: the person, the employee record and their login are created together.

A login is separate from a record

Being enrolled or employed does not create an account. Somebody has to invite the person, which sends them an email to set their own password.

Nobody — not you, not ShikshaFlow — can see or set another person's password. If somebody cannot get in, re-send the invitation or have them reset it.

APAAR ID

A student's profile has an APAAR ID row. APAAR is created only with the parents' consent, so the registrar records the state as well as the number: Generated (with the 12-digit ID), Waiting for parents' consent, or Parents declined. The number is stored encrypted and shown by its last four digits. The same number cannot be recorded for two students.

Guardians

A guardian is a person in their own right, not a field on the student. The same guardian can be linked to several students, which is what makes one family login cover several children.

If a parent says they cannot see one of their children, the missing thing is that link.

A parent who is also a teacher

One human, two person records, two logins. That is deliberate and correct — keeping them separate is what keeps what they see as staff apart from what they see as a parent.

Nothing is deleted

Student and staff records are never hard-deleted; they are marked inactive. A school has to be able to answer a question about a student who left four years ago.