Audit Log
TL;DR
A timestamped, immutable record of every important action taken in the system — who did what, to which record, when.
An audit log captures the actor (user), action (created, updated, deleted, approved), object (ticket, invoice, customer), and timestamp for every meaningful operation. It's the system's memory of what actually happened.
For repair shops, audit logs matter when something goes wrong: a refund was issued and the owner wants to know who issued it, a price was discounted and the owner wants to see the override chain, or a customer disputes a charge and the chain of approvals needs to be reconstructed.
Get Repair logs every state-changing action with the actor, IP, and a JSON diff of before/after. The log is queryable per record (show me everything that touched RPR-2847) or per user (show me everything one technician did this week).
Quick answers
How long are audit logs kept?
Indefinitely for the active period of the account. On account cancellation, logs are retained for a 90-day grace period and then permanently deleted along with the rest of the org's data.
Can I export audit logs?
Yes. CSV export for compliance or accountant review. The export includes the same fields you see in the in-app log: timestamp, actor, action, object, IP.
Related
RBAC(Role-Based Access Control)
A security model where what each user can see or do is determined by their role (e.g. Tech, Front Desk, Owner) rather than per-user toggles.
Multi-Tenancy
A software architecture where one system instance serves multiple isolated organizations (tenants), each seeing only their own data.