Platform foundation.

Every tenant in YESS is one school, isolated from every other by a school_id on every row and row-level security on every table. The foundation module is where a school sets the values those rules read from — its name and currency, its enabled languages, the roles its staff hold, the campuses it spans, and the plan that decides which features are switched on.

You will not visit these screens daily. You visit them at the start — to stand the school up — and then occasionally, to add a campus, mint a custom role, or change a plan. But every other handbook in this set quietly depends on the choices made here. A new tenant also arrives almost furnished: the moment a school is created, a single database function provisions its baseline roles, a default grading scale, the current academic year and its three terms, the three languages, the starter settings, and a thirty-day free trial — so the foundation is rarely a blank page.

The settings hub at /dashboard/settings is the discovery centre for everything school-wide, organised into seven tabs (plus a card that jumps straight to roles):

The roles surface at /dashboard/roles is the most powerful screen in the foundation. The catalogue defines sixteen standard role types — from school_admin and principal down to teaching_staff, accountant, librarian, student, and parent_guardian. A freshly created school is provisioned with a baseline set of these, each pre-granted a sensible slice of the platform's permissions ( school_admin gets all of them ); operational roles like the canteen manager, hostel warden, nurse, and proprietor are added as the relevant modules come online. On top of all that, you can create custom roles of your own.

A header KpiStrip counts the roles (system versus custom), permissions, assignments, and campuses. The left rail splits roles into system and custom — system roles wear a lock badge and cannot be deleted, though their permissions can still be tuned. Selecting a role opens its permission matrix: permissions grouped by module, each module collapsible with a “grant all” switch, every action toggleable individually, with a live granted-count. An Assigned-users tab on each role shows — and lets you assign or revoke — exactly who holds it.

Assignment is scope-aware, and the three scopes are real, separate ledgers. A grant can be school-wide (it applies everywhere), campus-scoped (the staff member holds the role only on a chosen campus, optionally with an allowance), or program-scoped (bound to a programme, carrying external credential numbers like an IB-coordinator or WAEC-centre code). On a multi-campus school the assign dialog offers a campus scope picker, so a vice-principal can be powerful on one campus and an ordinary teacher on another.

A school can be one site or a federation of many. The campuses surface at /dashboard/campuses lists each campus with its student and staff counts, exports to CSV, and — on a multi-campus school — carries the inter-campus mobility policy that governs how students move between sites. Open a campus to reach its own mini-world: an identity header, KPIs for students, staff, classes, and rooms, and a grid of room-cards that lead to its rooms, its attendance blocks, its campus-scoped roles, its per-campus settings, and its conduct — plus an inline announcement composer for that campus alone.

Campus-awareness runs deep: roles, finance, attendance, timetable, and reporting can all be scoped to a campus, so a campus manager sees and acts only within their own site while the proprietor still sees the whole school. Each campus can override its own bell schedule, attendance grace, fee scale, walk-in-admissions policy, and emergency contacts — and the campus role grants (campus principal, vice-principal, operations, admissions) make a manager powerful there and nowhere else.

The subscription screen at /dashboard/billing shows the school's current plan and status, its billing cycle and price, and — for a school still in its free trial — a countdown to the day it ends, turning urgent (the banner goes red) in the final three days. The features the plan unlocks are listed plainly.

The part schools actually need sits below: usage meters for students, staff, and campuses, each showing how much of the plan's ceiling is used, with a bar that warns from 80 % and badges when a limit is hit. A grid of available plans — Free Trial, Starter, Professional, Enterprise — shows what each tier costs and includes, with an upgrade/downgrade direction hint against the current plan. Changing plan and paying happens at /dashboard/upgrade, where a monthly/yearly toggle and a checkout dialog collect payment by card (Stripe) or mobile money (aggregators such as CinetPay, Campay, NotchPay, PawaPay).

The integrations hub at /dashboard/integrations connects YESS to the outside services a school runs itself — grouped by category: communication (Zoom, Microsoft Teams), services (Google Maps), and AI (OpenAI). Each is a card you open to enter its keys, test the connection, and switch it on, with a connected count at the top.

One deliberate absence: online payment collection is not configured here. Each school's payment gateway and its encrypted keys are managed centrally by YESS, never entered on a school dashboard — and the integrations page makes that explicit with a note rather than leaving a confusing gap. (Messaging providers like SMS and WhatsApp are managed centrally too.) Schools share secure payment links from the finance module instead.

Finally, identity made physical: the ID-cards surface at /dashboard/id-cards has two tabs — branded ID cards and official documents. For cards, you choose the audience (students, staff, or parents), bulk-select, and print or export to PNG or PDF, with an issuance ledger that tracks how many of a cohort still need one. The card itself is designed in the versioned /dashboard/id-cards/studio — an interactive canvas for the logo, photo, matricule, and a scannable code. The Documents tab generates enrolment letters, attendance certificates, leaving certificates, fee-clearance, and staff letters from the same place.

Every module inherits the foundation. A few feel its reach most directly.