AdagioX

In development: not yet available to schools

School management where every school’s data stays its own

AdagioX is a multi-school platform for secure sign-in, granular permissions, an audit trail, timetables and family records. Everything shown below already exists in the product; what is still to come is listed at the end of the page.

Get in touch See what it does

  • Sign-in page of a school, with the school's own name, logo and colours above the email and password fields.
    The sign-in page shows the school’s own name and logo.
  • Weekly timetable grid of a class group from Monday to Friday, with every slot filled in with its subject, teacher and room.
    Weekly timetable of a class group, with subject, teacher and room in every slot.
  • Weekly timetable of a class group where moving a lesson to another slot is refused with a notice that the teacher already has a lesson at that time.
    Moving a lesson is refused when the teacher already has a lesson at that time.
  • Permission editor for a custom role in the academic management module, where each permission is allowed, explicitly denied or left ungranted, with its scope.
    Role editor: each permission is allowed, denied or left undefined, with its scope.
  • Audit log listing who did what and when in the school, such as changes to timetable sessions, students, facilities and role permissions, with filters by date, operation, user, module and entity, and an export option.
    Audit log of who did what and when, with filters and export.
  • Family unit with its guardians, its students and the links between them, including relationship, legal representation and access level.
    Family unit linking guardians and students, with relationship and access level.
  • Front desk screen where staff search a student by name before handing the child over to an authorised person.
    Front-desk search before a child is handed over to an authorised person.
  • School branding settings with the logo, favicon and sign-in background, each with its format and size limits.
    Each school sets its own logo, favicon and sign-in background.

Browse the screens by scrolling sideways, with the arrow keys or with the buttons and dots; if your browser runs scripts, they also advance on their own and you can pause them. They show a test school with fictional data.

What already works

Each block below describes functionality that is implemented today. Screens show a test school with fictional data.

Secure access, with several ways to sign in

People sign in with a local account or through an external identity provider. A second factor protects the account, and every user can review and close their own active sessions.

  • Local accounts with password sign-in
  • Two-factor authentication by authenticator app or email, which a role can make mandatory
  • Single sign-on with an external provider, through OIDC or SAML 2.0
  • List of active sessions, with remote sign-out
Sign-in page of a school, with the school's own name, logo and colours above the email and password fields.

Several schools on one platform, each with its own brand

The data of each school is isolated from every other school. Each school presents the platform with its own identity and enables only the modules it needs.

  • Data isolated between schools
  • Own logo, favicon and sign-in background
  • Modules enabled school by school
  • User invitations and bulk user import
School branding settings with the logo, favicon and sign-in background, each with its format and size limits.

Roles and permissions, down to the scope

A permission combines a resource, an action and a scope, and anything not granted is denied. School administrators create their own roles in an editor and check the effective permissions of any user.

  • Custom roles alongside the default ones
  • Each permission is allowed, denied or left undefined
  • When a user has several roles, a denial prevails over an allowance
Permission editor for a custom role in the academic management module, where each permission is allowed, explicitly denied or left ungranted, with its scope.

An audit trail of who did what

Creations, changes and deletions are recorded with the user, the moment and the record affected. Administrators search the log and export it when they need to.

  • Filters by date, operation, user, module and entity
  • Export of the log
Audit log listing who did what and when in the school, such as changes to timetable sessions, students, facilities and role permissions, with filters by date, operation, user, module and entity, and an export option.

Timetables that refuse conflicts

Each class group has a weekly timetable with the subject, teacher and room of every slot. A change that would put a teacher in two places at once is refused, and spaces can be booked.

  • Teacher conflicts detected before a change is saved
  • Booking of rooms and other spaces
  • A weekly view for each class group
Weekly timetable of a class group where moving a lesson to another slot is refused with a notice that the teacher already has a lesson at that time.

Families, guardians and who may do what

Students and their guardians are grouped into family units. Each link records the relationship, legal representation and level of access, so access can be restricted for one student without affecting the rest of the family.

  • Guardians and students in a family unit
  • Custody restrictions applied per student
  • Consent for the use of images recorded with the family
Family unit with its guardians, its students and the links between them, including relationship, legal representation and access level.

A controlled hand-over at the front desk

Staff look up a student and see who is authorised to collect them before the child leaves. The authorised persons are managed for each student.

  • Front-desk search by student name
  • Authorised pickup persons recorded for each student
Front desk screen where staff search a student by name before handing the child over to an authorised person.

And also

Coming next

These parts of the first phase are not built yet. They are listed without dates and in no promised order.

  • Student enrolment and class lists
  • Attendance
  • Grades and report cards
  • Communication with families
  • Portals for families, teachers and students

How it is built

AdagioX is developed with Claude Code.

Contact

AdagioX is not yet available to schools. If you are evaluating the project, write to us.

founders@adagiox.com