One wall of pigeonholes.
Every module gets a slot.
Main Office Works is one codebase and one database, many tenants. Districts, schools, staff, students, and school years live in a shared Core; modules sit on top of it, governed by the same roles and the same audit trail. Nothing is bolted together after the fact.
Every slot reads and writes the same wall. No module keeps its own copy of a student.
Shared identity, so the data lives in one place.
Teacher mailboxes work because there's one wall and everyone knows it. The Core is that wall: one set of identities every module trusts, instead of five apps with five copies of the same student.
Every slot reads and writes the same wall. No module keeps its own copy of a student.
One install serves many districts; each district has its buildings. Data is isolated by district and school.
One identity per person, shared by every module. A student is entered once, ever.
Operations are scoped per year, so each year's record stays clean and comparable.
An authorization matrix maps each role to exactly the actions and screens it should have.
Schools enable the modules they need; the admin console tracks what's licensed where.
Districts, schools, users, students, years, branding, and settings managed in one place.
Claims your IT director can interrogate.
School operations software touches student data, so access control is architecture here, not a compliance checkbox. Each line below is how the platform is actually built — bring your technology team and we'll go as deep as they want.
Student-data paperwork: districts will want a signed data privacy agreement and a written security summary before a pilot touches anything real. That paperwork is in progress — ask where it stands in your demo, and we'll tell you plainly. See also the privacy page.
- Referral 2027-0398 resolved — resolution shared with counselorOct 8
- Fine cleared — charger returned at Station BSep 30
- Cut slip 2027-0311 excused — attendance note attachedSep 22
- Chromebook CB-1102 assignedSep 3
A complete school you can poke at — with nobody real inside.
The platform ships with a self-contained demo district: realistic, fully anonymized data, isolated from any real school. Demos run there, always. Your walkthrough never touches live student information, and neither do we.
It's also how the record above works: conduct, devices, and coverage writing to one student, one staff member, one year — so the history is a timeline, not an export.
Bring your IT and operations teams.
We're happy to go deep on architecture, access control, and what a rollout actually looks like.