Every create, update, view, and export tracked with the actor, the workspace, the IP, and the timestamp. Look up exactly when a record changed and who did it — for public-records compliance, board accountability, insurance audits, and the rare moment when something needs to be reconstructed.
What it does
Comprehensive tracking
Every action on every record produces an audit entry: who did it, when, from what IP, what changed (before and after values for updates), what was viewed (for sensitive records). The system can't lose track of what happened; the logs can't be edited or backdated.
Searchable history
Per-record history view shows every action on that record over time. Search across the whole audit log by actor, by date range, by action type, by IP, by record type. Reconstruct what happened — useful for resolving disputes, investigating data quality issues, and the rare moment someone says "this wasn't what I entered."
Public records & insurance
Public-records requests for parks-and-rec departments. Insurance audits for community centers. Funder reviews for senior-center grants. Each compliance query becomes a saved filter — "all member records modified in Q3, by staff member" or "all reports run by the volunteer coordinator in 2024" — and the export goes to whoever's asking.
User activity views
Per-user activity views for management — recent actions, records touched, time of last activity. Useful for offboarding (what did the volunteer who just left have access to?), security review (any unusual activity?), and the rare moment when you need to understand how a staff member spends their time on the system.
A workflow walkthrough
The audit log earns its keep in small moments. Three of them — a dispute, a public-records request, a year-end audit — show how it does the work.
March — A member disputes a payment. A member says she never authorized the renewal charge. The director pulls up the member's record, opens the audit log filter for billing actions. The renewal: auto-renew fired on March 1, charge succeeded, confirmation email sent at 8:04 AM. The member had opted in to auto-renew at original signup; that consent action is logged too, with timestamp and IP. The dispute resolves in five minutes.
July — A public-records request. A reporter requests the utilization records for Riverside Park, Q1 and Q2. The parks director runs a saved query — "facility-use records for Riverside Park, Jan 1 to Jun 30" — and exports to PDF with PII redacted per the state's open-records policy. Response sent within the legal window; the audit log preserves the export action itself.
December — The annual audit. The external auditor needs three slices: all billing actions in the calendar year, all member-record modifications by the bookkeeper, all report exports to outside parties. Each slice exports in five minutes; the auditor signs off on internal controls without a follow-up. The director never has to reconstruct anything from memory.
Questions, answered
Set up your workspace this morning. Start your first record edits this afternoon. Watch every action log itself — and answer your first public-records request in two clicks next week.
14 days free · Card required · Cancel anytime
