Role-Based Access
Operational permissions reflect real school responsibility boundaries across teachers, bursars, registrars, administrators, campus leaders, and HQ oversight.
Security & Software Trust
Indelo protects the credibility of academic records, financial transactions, audit trails, synchronization packages, recovery paths, and software distribution.
Operational permissions reflect real school responsibility boundaries across teachers, bursars, registrars, administrators, campus leaders, and HQ oversight.
Result unlocking, ledger reversals, and exeat approvals are audited ceremonies — not silent edits hidden inside ordinary forms.
Institutions can understand what changed, when, by whom, and under which workflow.
Results, report records, attendance evidence, approvals, locks, and academic history are long-term trust assets, not ordinary editable data.
Teacher-spoke databases are encrypted at rest. A stolen teacher laptop should not expose readable student data.
The cashbook is an append-only, chained ledger. Corrections are reversing entries, never erasures; altered receipts are detected, not discovered.
Every installation should complete a recovery ceremony before first use. A dead machine should be a restore event, not institutional data loss.
Chained, verified synchronization packages detect and refuse silent modification, replay, gaps, and out-of-order imports.
Review sync architectureIndelo installers are EV Authenticode-signed so Windows can show a verified publisher on every installer distributed through CABS-controlled channels.
Distributed trust
Teacher spokes, campus hubs, and HQ consolidation operate with scoped authorship, verified packages, audit chains, quarantine review, and business-rule guarded imports.
Synchronization cannot bypass institutional controls. Bad packages, gaps, replay, unsafe versions, and out-of-order imports are refused rather than quietly accepted.
Group verification
For school groups, HQ verification is the natural security closing loop: campus records and books can be re-verified centrally against the chained, signed packages each campus submits, so altered history is surfaced rather than silently accepted.
This is the operational meaning of trust infrastructure: not merely passwords, but evidence.
Enterprise deployment
Discuss encrypted teacher laptops, recovery bundles, controlled distribution, tamper-evident records, and multi-campus verification.