Create and manage students

A student is a school-owned learner record. Create it in the correct school and semester, then assign the intended halqa before daily sessions begin.

1. Confirm the active school and semester.
2. Open Students and choose Add student.
3. Enter the student’s full name and required identity fields.
4. Choose the correct halqa or deliberately select No halqa.
5. Enter only necessary contact or guardian information and student notes.
6. Save, then open the new student profile.
7. Confirm the registration date, halqa, and current Quran position.

Waqar warns when a normalized name resembles an active or archived same-school record. Review the candidates and choose Use existing student or explicitly confirm Create a separate student with a reason. A warning is not proof: two different students may legitimately share a name.

The profile can bring together the student’s current position, recent recitations, attendance or progress links, Learning Plan when enabled, parent invitation action, report, coverage and milestone views, and supported PDF certificate.

Availability varies by role, feature, current data, and plan. A missing panel does not prove that the student’s history was deleted.

Use Archive student with a reason to remove a learner from future session and attendance rosters. Archive does not delete recitations, attendance, reports, plans, invitations, parent links, or audit history. Administrators can open the Archived list and reactivate an unmerged record. Reactivation checks likely duplicates again.

An administrator can select a canonical target and review a merge preview. The preview shows transferable counts and blocks the merge when attendance statuses, active plans, planning policy, verified parents, semester lineage, merge history, or preview versions conflict. A successful merge transfers only supported relationships, archives the source, and retains its immutable link to the canonical student. Old authorized source links redirect to that target. Do not merge solely because names match.

Use Edit student details to correct supported fields, change the halqa, or change active status. Explain a halqa change to both sheikhs so future sessions use the intended group.

Notes are shared school records. Record objective, necessary teaching information only. Do not store passwords, invitation links, unrelated family details, or sensitive information that the workflow does not require.

Changing or deactivating a student must not rewrite completed sessions, recitations, reports, or assignment history. Semester carry-forward creates the new period’s active record while retaining earlier evidence.

If a conflict blocks a merge, leave both records unchanged and resolve the identified relationship through the supported owner. Do not transfer rows manually or delete the source record.