Frequently asked questions

Waqar is a bilingual web application for Quran-school operations. It supports schools, staff, halqas, students, attendance, recitations, progress, optional Learning Plans, parent visibility, reports, notifications, and controlled API integrations.

Yes. The application and this wiki support Arabic right-to-left presentation and English left-to-right presentation. Use the language control to switch. Names and content entered by a school are shown as entered.

Navigation follows your role, active school, available features, and record relationships. A school administrator, sheikh, and parent have different workspaces. See the role and permission reference.

Yes, when each school has granted a membership or parent link. Select the correct school before working. A membership in one school never grants access to another school’s records.

The usual causes are role permission, the selected school, assignment or parent link, record status, feature configuration, plan availability, a capacity limit, or controlled rollout. Follow feature availability and permission troubleshooting.

Ending a session locks the normal teaching record. Review attendance and recitations first. If a correction is necessary, use the school’s authorized correction process rather than starting a duplicate session. See end a session.

No. Learning Plans are optional and must be enabled and configured by the school. Daily attendance and recitation work can operate without them. Start with the Learning Plans overview.

A parent sees only linked children and parent-visible records. For Learning Plans, only eligible active published work is shown when the school enables parent visibility. Drafts, private staff notes, and internal planning details are excluded. Read parent visibility and privacy.

The available report and format depend on your role, the report, and the school’s enabled features. Supported outputs can include PDF, CSV, or XLSX. Check exports and downloads before sharing a file.

Waqar provides a controlled school integration API. Access requires an eligible school, enabled API access, an active school-issued key, the required scopes, rollout eligibility, and available quota. Begin with the API overview.

No. Write access is independent, default-off, and requires explicit feature enablement and separate rollout eligibility. Each operation also requires its documented scope and, for writes, an idempotency key where specified.

No working WhatsApp delivery channel is currently released. Do not promise WhatsApp delivery based on an old label or entitlement. Use the notification channels actually displayed in the application.

No. Current custom branding means the supported school-logo treatment in approved views. It does not mean full white-labeling or a school-owned domain.

Include your role, the affected page, the action you attempted, the approximate time, and the visible message. A screenshot is useful after hiding learner and account details. Never send passwords, session cookies, recovery or invitation links, or API keys.