School administrator checklist

Use this checklist when setting up a new school. Complete the structural steps before recording live teaching data so that sessions and reports are assigned correctly.

Sign in and select the intended school. Check the school name shown in the navigation before making changes. If you administer multiple schools, the same account can switch between them; each school’s data remains separate.

Open Settings and confirm the school name, type, city, and timezone. The timezone affects how school dates are interpreted. You may upload the supported school logo; this is branding inside supported views, not full white-labeling or a custom school domain.

Also review the displayed plan, limits, and enabled features. A role alone does not bypass a student, staff, feature, or export limit.

Open Semesters and confirm the current reporting period. Archive a semester only after reviewing its data and exports: archiving changes its status and is an administrative action, not a filter for hiding a temporary record.

Open Manage → Teachers or Manage → Administrators. Send each invitation to the person’s own address and assign only the role they need. Invitations are sensitive, time-bound access links; review their pending/expired status and revoke an obsolete link rather than forwarding it. Remove a teacher or administrator membership when access is no longer required; teacher removal clears current halqa assignments while retaining historical teaching records.

Create each halqa, assign the appropriate sheikh, and enter its schedule. Then add students and place them in the correct halqa. Confirm names and assignments before sessions begin because these records feed daily work and reports.

Parent access is separate. Create a parent invitation from the intended student’s record so the accepted account is linked to that child.

Learning Plans are optional. In Settings, choose whether the feature is enabled and configure defaults before creating plans. School, halqa, and student policies can override one another; do not enable automation until you understand which effective policy a student inherits.

Create a session for the correct date, halqa, and sheikh. Record attendance, add a test recitation, review the result, and end the session. Then confirm the result appears in the expected student and school reports. Remove test data before using the workspace for real records if your operating policy requires a clean history.

• Review the dashboard and notifications.
• Check memberships, pending invitations, and capacity limits.
• Review session completeness and data quality.
• Reconcile learning-plan exceptions before publishing future work.
• Export required reports through authorized product controls.
• Keep account recovery information and personal sessions secure.