What this module is for
Use the parent app for student dashboard, attendance, fees, exams, notices, events, timetable, transport, gallery, and homework.
Prerequisites
- Parent mobile number linked to a verified student
- Published or parent-visible records available
Main screens
Step-by-step workflows
Log in as a parent
- Open the parent app.
- Enter the registered parent mobile number.
- Verify OTP.
- Select school and child if multiple records are available.
Review student updates
- Open the dashboard.
- Use module cards to view attendance, fees, exams, notices, timetable, transport, gallery, and homework.
- Open details only from records visible to parents.
Operational detail
Permission checkpoints
- Parent app access depends on verified guardian contact details linked to an active student.
- Parents can view only records that the school has made parent-visible or published.
- The parent app must never call AI providers or internal admin endpoints directly.
Field guidance
The parent login flow starts from the mobile number saved in the student or guardian record.
Parents verify access through OTP before selecting a school or child profile.
When one guardian has multiple active students, the app should show a safe child selector.
Exam results, report cards, notices, homework, and fee details appear only when the source module allows visibility.
Operational cards should reflect active enrollments or allotments instead of showing unavailable internal setup data.
Parent-facing help should guide users to school support without exposing internal IDs or staff-only diagnostics.
Validation and system feedback
- OTP requests must validate the registered mobile and active linked student records.
- Parent data must be filtered by school, student, relationship, and publication status.
- Sensitive internal record identifiers should not be exposed in mobile responses.
- Offline or stale app views should refresh before showing critical fee, attendance, or exam details.
Common mistakes to avoid
- Expecting parents to see unpublished results or draft notices.
- Leaving guardian mobile numbers incomplete during admission.
- Showing admin-only module status in the parent app.
- Using screenshots with real parent mobile numbers or student identities.
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.