Metroskool Suite

Digital excellence

Architecture for Campus Excellence

Metroskool is one school workspace with optional modules. Activate Pulse, Vote, Archive, Monitor, or the full suite — shared people stay shared; clinic, ballot, library, and attendance data stay private.

The suite

Five products. One tenant.

Each hosted app opens in its own origin. School Owners start in Metroskool Admin, then open the modules they have activated.

How schools work

One school. One workspace.

The first verified official school email becomes School Owner. Officers apply by module and wait for approval. Learners and campus structure live once in Admin.

  1. 01 Register in Admin

    Verify the official school email. That person becomes School Owner.

  2. 02 Activate modules

    Turn on Pulse, Vote, Archive, Monitor, or keep Admin only.

  3. 03 Approve officers

    Nurses, electoral officers, librarians, and teachers apply and wait.

  4. 04 Operate in the module

    Clinic, elections, library, and attendance stay isolated from each other.

Built to be trusted

Calm, precise, and school-scoped.

  • One database, many tenants

    Every school-owned record carries a school id, enforced in Postgres.

  • Authorisation from membership

    Roles come from membership tables and RLS — not mutable user metadata.

  • Secret ballots

    Vote keeps eligibility apart from stored selections. Students vote on the web only.

  • No privileged keys in clients

    Web, Windows, and Android never ship a service-role key.