Audit log

Audit log is the append-only, hash-chained record of privileged actions across your organisation — who did what, and when, read-only by design.

What it is

Every entry records an action (create, update, grant, key minted/revoked, finalize, soft delete, and more), the entity it affected, who did it, and when. Survey creation and every field-level change to a survey — drafts included — are captured automatically as they happen, giving a contemporaneous edit history that sits underneath the sealed-evidence chain itself, not just a summary of it.

How to do it

1. Open Settings → Audit log.
2. Search by entity, entity ID, or the actor’s email or user ID, and filter by action type.
3. Where an entry relates to a survey or work order, click through to open that record directly.
4. Page through older entries as needed — the feed loads newest first.

How it integrates

Each entry carries its own hash plus the previous entry’s hash, so the sequence you’re viewing is spot-checked for a broken link across the currently loaded page — the same tamper-evidence property a single sealed record’s own verification demonstrates, applied across the log itself. A separate nightly sweep independently recomputes every finalized survey’s hash chain in full; if it ever finds a mismatch, that record is quarantined (a display flag only, never altering the evidence it questions) and an integrity alert is written to this same log and your organisation’s notification centre. A clean nightly run is itself recorded, so “no alert” is provable rather than simply an absence of evidence.

Common problems

• I don’t see Audit log in Settings at all. It needs audit-module view access — coordinators and viewers have it by default, but it’s switched off for finance and for field roles (surveyor, operative).
• An entry doesn’t show who performed a system-triggered action. Some automated entries (the nightly integrity sweep, for example) record system as the actor — that’s expected for actions HousingSurvey Pro itself performs rather than a person.
• I saw an “EVIDENCE INTEGRITY” alert. That means the nightly chain-verification sweep found a mismatch on a specific record — the record is quarantined pending investigation; treat it as a genuine incident rather than a display glitch.