Staff & Organisation
The right people with the right access, and a clean handover when staff change.
- Head teachers
- Owners
- Boards
- Administrators
Reporting line
What it does
The right people, the right access, a clean handover.
Bursar → post fees
granular, without a checkbox wall
Roles map to capabilities
A role resolves to named capabilities, each one auditable.
pending → approved → executed
two people, or it stays pending
Two-person approval
A sensitive action waits for a second authorised signer. Ownership included.
Unheld capabilities: 0
the studio checks, seat by seat
Org studio
Model your school’s real structure, then check that nothing critical is unheld.
teaching_set · class_teacher · hod
atomic: all of them, or none
Responsibility handoff
A leaver’s teaching sets and HOD duties move to a successor together.
How it works
From start to settled, in three beats.
- 1
Model
Roles are designed to fit your real structure and resolve to granular, auditable capabilities.
- 2
Grant
Access is a grant with a start and an end; the dangerous actions need a second signer.
- 3
Hand off
When staff leave, their teaching sets and posts transfer atomically to a successor.
Why it’s different
Episodic, audited role grants.
A grant has a beginning and an end, both recorded, so “who held what, when, why” is answerable long after the fact. Authority stays accountable.
Role grants have a beginning and an end, both recorded.
Every grant has a recorded beginning and end, so “who held what, when, and why” always has an answer.
Roles → capabilities
Granular and auditable. The org studio checks coverage, so nothing critical is left unheld.
The artifact
Roles to capabilities.
Each role and the capabilities it actually carries. Coverage you can verify by reading down a column.
See staff and org in a walkthrough.
See staff on your own school’s data in a guided pilot. Import, training and a full term of support are included.