From one shared password to an answerable trail
Representative scenario — illustrativeA well-regarded 1,600-student school runs its office software on a single “admin” login that half the staff room knows, because setting up individual users was “too much bother”.
When marks were changed after publication, or a bonafide was issued to a student who had left, nobody could say who did it — the login was “admin”, and admin was everyone. A departing accountant’s access lived on for months because no one remembered to disable a password only a person, not an account, ever had. Reviews turned into arguments, because there was nothing on the record to settle them.
The cheap ERP technically supported users, but every real role needed a workaround — the fee desk could see student marks, the class teacher could see other sections — so the school gave up and shared one powerful login again. There was no meaningful audit trail, no per-user override, no session or password policy. Six months in, “security” was still one password on a sticky note under the keyboard.
ez.school makes governance the way the platform works, not a feature you switch on. Roles match responsibility with per-user overrides for the genuine exceptions, so the fee desk sees fees and a class teacher sees their sections. Every consequential action — publishing results, issuing certificates, changing a role, unlocking marks — is logged with who, when and what, and password, session and sign-in policy are yours to set. Disputes end with a query, not a quarrel.
| By hand | Ordinary ERP | ez.school | |
|---|---|---|---|
| Who logs in | One shared “admin” | Roles that don’t fit | Per-person, role + overrides |
| Who did it | Unknowable | No real trail | Actor, time and action logged |
| Leaver access | Lives on for months | Manual, forgotten | Provisioned and revoked per user |
| A dispute | Ends in argument | Nothing to check | Settled by the audit log |
- Per userAccess provisioned
- Every actionOn the record
- YoursPassword & session policy
| Actor | Action | When |
|---|---|---|
| Admin | Published marksheet — Term I | 2m ago |
| Teacher | Marked attendance — IX-A | 14m ago |
| Accounts | Recorded fee receipt | 31m ago |
| Registrar | Issued transfer certificate | 1h ago |
The activity trail — every result publish, certificate issue and role change carries who, when and what, so a review is a query not a quarrel.