Integrations

Works now: Teacher question drafts from lesson content, step-by-step help for students, progress summaries for guardians. Every request is logged.

To enable we need: ANTHROPIC_API_KEY on the server and a usage policy approved by the school.

Works now: Inside the platform now: scheduling against the timetable, join link, who joined through the platform, manual recording link.

To enable we need: Provider account and OAuth app, meeting-creation APIs, attendance reports (webhooks), cloud recordings.

Works now: No connection. Student data is entered directly in On Campus; the student number is stored for later matching.

To enable we need: Official approval from the Ministry of Education or an accredited integration channel, and an agreed scope and direction of data exchange. Not assumed to exist.

Works now: In-app notifications are live and tied to real events.

To enable we need: An email provider (e.g. SES), a licensed SMS provider in KSA with a registered sender ID, and a push service.

Works now: No amounts are shown.

To enable we need: A fee data source (school finance system), a payment gateway (mada/Apple Pay), and ZATCA e-invoicing.

Works now: Email and password sign-in with secure sessions and rate limiting.

To enable we need: The school's identity provider (Microsoft Entra / Google Workspace), or Nafath with official approval.

Works now: Files are stored outside the public folder and served only after a permission check (server disk).

To enable we need: An S3-compatible bucket hosted in KSA, encryption keys, and malware scanning.