Governance
Audit Trail
Every action in BOS is recorded in a tamper-evident audit trail. You always know who did what, when, and why — and you can prove the record hasn't been altered.
What gets recorded
Practically everything that changes data or state is logged, including:
- Records created, updated, or deleted in any module.
- Approvals requested, granted, or rejected.
- Actions taken by the Orin assistant.
- Settings changes, including roles and autonomy levels.
- Logins and sensitive data access.
Why it's “tamper-evident”
The audit log is hash-chained: each entry includes a cryptographic fingerprint of the entry before it. If someone tried to change or delete a past record, the fingerprints would no longer match and the break would be immediately detectable.
In plain terms
Think of it as a sealed ledger where every page is stamped with a code derived from the previous page. You can't quietly tear out or rewrite a page without breaking the sequence.
Each entry tells the full story
A typical audit entry captures:
- Who — the user or AI that acted.
- What — the action and the affected record.
- When — a precise timestamp.
- Why — the workflow and any approval that authorized it.
Viewing and exporting
Administrators can browse the audit trail in the app, filter by user, module, or date, and export it for reviews. See Data Export.
Great for trust and compliance
A verifiable history is invaluable for audits, investor due diligence, and meeting regulatory requirements like the DPDP Act. See Security & Compliance.