Choose the right guide

Waqar uses roles to keep each school workspace and child record private. Choose the guide that matches how you use the product.

Role	Primary work	Start here
School administrator	Configure a school; manage staff, semesters, halqas, students, features, learning plans, and reports	Administrator checklist
Sheikh	Work with assigned learners; run sessions; record attendance and recitations; manage permitted learning-plan tasks	Sheikh checklist
Parent	View linked children, attendance, progress, coverage, milestones, and published assignments	Parent checklist
API integrator	Read or, when explicitly enabled, write school data through scoped API keys	Integrator checklist

After sign-in, Waqar may ask you to select a school. The selected school determines both the workspace and the role used for that visit. Use Switch school to move to another membership; do not share accounts to move between schools.

A person can hold different roles in different schools. For example, a user may be a sheikh in one school and an administrator in another. Actions available in one workspace are not automatically available in the other.

• School administrators can perform school-level management actions, but their authority does not extend beyond the selected school.
• Sheikhs can run teaching workflows but cannot change protected school, staff, plan-entitlement, or API-key settings unless they separately hold an administrator membership.
• Parents can view only children linked through accepted parent invitations.
• API keys are not interactive user roles. Their scopes, feature availability, and controlled rollout state define API access.

If the wrong workspace or role appears, sign out and verify the email address used for the invitation. Ask an administrator to inspect the membership; never solve a permission issue by borrowing another person’s account.