Release notes

This page summarizes user-visible capability areas covered by the current documentation. It is not a pricing contract, service-level agreement, or replacement for the feature availability reference.

The public wiki covers the visitor journey, account security, school setup, daily teaching, Learning Plans, reporting, parents, API integrations, troubleshooting, and reference material in Arabic and English. Arabic pages use right-to-left presentation and preserve left-to-right display for code, URLs, and technical identifiers.

Schools can optionally configure destinations, policies, workload tracks, and Quran partitions; create or generate plans and assignments; review and publish work; record outcomes; replan safely; expose eligible work to linked parents; and use planning reports. Learning Plans remain opt-in and are not required for ordinary attendance and recitation tracking.

Authorized school users can work with overview, attendance, progress, session, planning, and audit-oriented reports. Supported downloads can include PDF, CSV, and XLSX depending on the report, role, plan, and enabled feature.

Invited parents can open linked-child overviews, attendance and recitation progress, and eligible published planning work. Parent access is relationship scoped and excludes drafts, private staff notes, and unrelated learners.

The current API documentation covers versioned school integration resources, authentication, scopes, pagination, errors, quotas, idempotent writes, and Learning Plans read resources. Read and write eligibility are separate. Write access remains default-off and requires explicit authorization.

• WhatsApp delivery is not currently released.
• Custom branding currently means supported school-logo treatment, not full white-labeling or a custom domain.
• A plan’s default does not override role, school, feature, limit, or controlled rollout checks.
• API read access does not imply API write access.
• A menu item, announcement, or old label is not proof that a feature is available to a particular school.

Future entries should describe the affected audience, what changed, whether an administrator must configure anything, and any availability condition. For an action you cannot find, check statuses and states, feature availability, and troubleshooting before contacting support.