What this module is for
Help parents sign in with OTP, select school and child, and manage mobile app sessions safely.
Prerequisites
- Parent mobile number exists on verified student records
- Parent app installed
- Network access available
Main screens
Step-by-step workflows
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.
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 checkpoints
- 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.
Field guidance
Keep the guardian mobile number accurate during admission and profile updates because it is the parent login identity.
Parent access should link to active student records that belong to the school.
Parents see notices, exam results, homework, timetable, fees, and attendance only according to module visibility rules.
When one mobile number belongs to more than one student, the parent app should show a child selector.
For login issues, verify the mobile number, active student status, and published source records before escalating.
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.
Recommended next steps
Screenshot plan
Final public screenshots will use synthetic QA data only. Sensitive values such as names, phone numbers, emails, admission numbers, document numbers, credentials, cookies, tokens, and internal IDs must be removed or redacted.
Important safety notes
Use normal Schoolixa workflows
Public docs explain user workflows only. They do not expose internal IDs, direct database operations, credentials, provider prompts, or private system configuration. Permission visibility in the interface does not replace server-side permission checks.