Parent Login Documentation

Overview

Help parents sign in with OTP, select school and child, and manage mobile app sessions safely.

Before you start

Parent mobile number exists on verified student records
Parent app installed
Network access available

Main screens

Login OTP Verification School Selector Child Switcher Device Sessions

Step-by-step workflows

1

Sign in with OTP

Open the parent app.
Enter the registered parent mobile number.
Request OTP.
Enter OTP before it expires.
Select school and child if more than one record is available.

2

Switch child or school

Open the school or child switcher.
Select the intended school/student.
Confirm the dashboard refreshes for the selected child only.

Operational detail

Permission requirements

Parent access is controlled by the student/guardian relationship and published module data, not by admin sidebar permissions.
School staff manage parent visibility through the source modules such as notices, exams, homework, fees, and attendance.
Parent login support must not reveal OTP values, tokens, credentials, or internal IDs.

Guardian number

Keep the guardian mobile number accurate during admission and profile updates because it is the parent login identity.

Active student

Parent access should link to active student records that belong to the school.

Published records

Parents see notices, exam results, homework, timetable, fees, and attendance only according to module visibility rules.

Multiple children

When one mobile number belongs to more than one student, the parent app should show a child selector.

Support cases

For login issues, verify the mobile number, active student status, and published source records before escalating.

Privacy

Public help docs should never include real student names, phone numbers, OTPs, or admission numbers.

Validation and system feedback

Parent lookup validates guardian contact and active school relationship.
Source modules decide whether specific data is visible to parents.
Parent app responses should remain scoped to the selected child.
Support users should use masked data when troubleshooting access.

Common mistakes to avoid

Trying to fix parent login without checking the guardian mobile number.
Expecting draft notices or unpublished results to appear in the app.
Using staff/admin credentials to test parent-only views.
Sharing OTP screenshots in support channels.

Safe use

Keep documentation and support privacy-safe

These guides explain normal user workflows only. Do not share passwords, OTPs, tokens, cookies, private student identifiers, payment details, raw internal IDs, provider configuration, or stack traces in support messages or screenshots.

Trying to fix parent login without checking the guardian mobile number.
Expecting draft notices or unpublished results to appear in the app.
Using staff/admin credentials to test parent-only views.
Sharing OTP screenshots in support channels.