Parent & student portals.

A portal is not a cut-down version of the admin app — it is a purpose- built window. Each one shows only what its audience needs, gated by the same permissions that protect the rest of YESS, and each one is built to read cleanly on the device its audience actually uses: a parent on a phone between errands, a teacher on a tablet in the staffroom, an owner on a laptop on a Friday afternoon.

There are four: the student portal, the parent portal, the teacher portal, and the owner portal. They share a design language and a login, but each answers a different question — and which surfaces a family sees is itself controlled by the school in settings.

A student opens /portal to a profile header and a snapshot of today — the next class, what is due, how attendance and grades are trending. From there the whole of their school life is a tap away: /portal/grades and /portal/report-cards, /portal/timetable, /portal/assignments and /portal/courses, /portal/attendance, and /portal/fees.

The portal is not only consumption. Students take online exams, message teachers, join clubs, vote in elections, submit their own enrolment and subject choices, and reach the AI study room — all from the same shell. With dozens of surfaces behind one home, it is the busiest portal in YESS, and the one that most shapes how the school feels to the person living it.

The promise is one login per family. A guardian linked to more than one child switches between them with a single tap; no second account, no second receipt stream. The home portal gives a single-child view; the cross-child overview at /portal/parent shows every child side by side — pending logbook approvals, assignments due this week and overdue, recent grades, and last activity, one row per child.

From there a parent reaches the fee portal at /portal/fees (balance, invoices, payments, and a request for a payment plan), their child's grades and attendance, announcements and messages, and logbook approvals at /portal/parent/logbook-approvals. The link between guardian and child — made in the student record — is what makes all of this appear.

A teacher's portal at /teacher is a working surface, not a viewing one. It gathers the classes they carry at /teacher/classes, the gradebook at /teacher/grades, daily attendance at /teacher/attendance, the lesson logbook at /teacher/logbook, conduct at /teacher/conduct, the schedule, assignments, quizzes, and messages — everything the teaching day needs.

Crucially, every staff member is also a first-class employee here. The same portal carries self-service: a teacher reads and acknowledges their payslip at /teacher/my-payslip, checks balances and requests time off at /teacher/my-leave, reads their contract at /teacher/my-contract, and browses professional development at /teacher/development.

The proprietor's portal at /owner is deliberately not a dashboard — it is a calm, letter-like State of the School briefing a time-poor owner reads in thirty seconds: a plain-language health verdict, a short list of the few things that need them personally, the headline numbers each shown against last period and against their target, and quiet doorways to the detail.

Those doorways are strategic, read-only views — the owner reads the margin, they do not process the invoice. Financials at /owner/financials, academics at /owner/academics, attendance, a per-staff radiography at /owner/staff, enrolment, conduct, compliance at /owner/compliance, and a board-pack of saved and scheduled reports at /owner/reports. On a federation, the owner sees the whole school while each campus manager sees only their own.

Every portal runs on the web and as a native mobile app on Android and iOS, with the same experience and the same data on each. Every screen reads in English, French, or Arabic — with right-to-left layout for Arabic — and money always shows in the school's own currency.

The school decides the front door. In settings, the Portal-login tab configures how families sign in — including QR and school-code login, handy where families share devices or are new to apps — and the Portals tab switches individual portal surfaces on or off. A portal is powerful precisely because the school controls exactly what it shows.

A portal is a window onto data the rest of YESS produces. These modules feed them most directly.