What this module is for
Manage admissions, student profiles, lifecycle, documents, certificates, and identity print.
Prerequisites
- Academic session created
- Class and section configured
- Student admission permission assigned
Main screens
Step-by-step workflows
Add a student safely
- Open Admission & Students > New Admission.
- Enter the required student and guardian details.
- Save the admission record.
- Complete admission setup when the student is ready to become active.
- QR/barcode is generated only after admission status becomes active.
Review student profile
- Open the student directory.
- Search or filter the student.
- Open the profile.
- Use profile cards for attendance, fees, examination, documents, siblings, hostel, transport, and identity print.
Operational detail
Permission checkpoints
- Users need the relevant admission, student profile, document, certificate, or identity print permission before the matching action is visible or accepted.
- Profile cards may appear only when the linked module is enabled and the user has permission to open that destination.
- Lifecycle actions such as activating an admission are protected separately from ordinary profile editing.
Field guidance
Use the active session unless you are intentionally reviewing historical placement. Session selection affects class, section, fee, attendance, and exam visibility.
Select the configured class and A-Z section that represents the student placement. Sections with unsupported names are rejected.
Draft or incomplete records remain operationally limited. Permanent identity QR and barcode values are generated only after the student becomes active.
Enter parent or guardian contact data carefully because parent login, notifications, and emergency communication depend on it.
Upload only required school documents and keep document names clear. Sensitive values are not needed in public reports or support screenshots.
Use cards to open related records such as attendance, fees, examination, documents, siblings, hostel, transport, and identity print.
Validation and system feedback
- Admission number and student identity must be unique within the school rules configured by the application.
- The system validates school ownership, session placement, class-section relationship, required fields, and supported upload formats.
- QR/barcode generation is intentionally blocked before the admission reaches active status.
- Server validation runs even if a button or sidebar link is hidden or shown incorrectly.
Common mistakes to avoid
- Creating profile records in the wrong academic session.
- Trying to print permanent identity before admission completion.
- Using section names that are not simple A-Z section codes.
- Uploading screenshots or files that contain private document numbers when a safe synthetic file is enough for testing.
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.