Skip to content
Omni

For IT, data and business admin

Every school walled off in the database, two-step verification, and leavers switched off in one step.

Arrange a demonstration

Ten ways IT teams keep data safe with less admin

  • Isolated by design

    Every school's data is isolated at the database level, with access rules held in the database itself rather than only in application code.

  • Two-step verification with an authenticator app

    Any user can set it up from their account page, and platform administrators must use it. Where an account has set it up, the database enforces it as well as the sign-in screen.

  • Deactivate a leaver in one step

    Their sessions end at once, their responsibilities end, and everything they recorded stays on pupils' records. Reactivate them if they return.

  • Sensitive changes tracked

    Changes to sensitive records are logged in the same transaction as the change, so the audit cannot fail while the change succeeds. Free-text notes are redacted from the log.

  • Import your school from spreadsheets

    Pupils, staff, class lists and a timetable export, each matched on identifiers before names and previewed before anything is committed.

  • Roles that match how a school is organised

    School admin, depute head, principal teacher, pupil support, teacher and support assistant, plus pupil and parent, each seeing only their own remit.

  • Hosted in London

    The database and application servers are in London, with every school's data isolated at the database level. Backups with point-in-time recovery are planned before any live data.

  • A setup checklist for a new school

    Eight steps with live counts: staff, rooms, subjects, faculties, houses, timetable, pupils and class lists.

  • Locks itself on a shared machine

    After five minutes without activity a countdown appears and the screen locks until the user enters their password.

  • Targeting WCAG 2.2 AA, with the gaps published

    Omni is partially compliant with WCAG 2.2 AA and its public accessibility statement lists each known failure. Page titles and table headers are checked automatically on every change.

  • + 17 more featuresGet in touch to find out more →

Set up the way your authority works

Each school's records are kept apart inside the database, so one system can serve a single school or a whole council.

  • School by school

    Each school runs Omni with its own staff, pupil and parent accounts, set up and administered by the school.

    Available now
  • Council-wide

    One Omni for the whole authority, every school kept separate and administered locally, with an overview account for central staff at the civic centre that we would design with you.

    Shared instance: nowOverview: planned
  • Glow sign-in

    We would be happy to consider options for integration with Glow, so staff keep a single login and accounts follow them as they join, move and leave.

    Open to integration