Audit log
An append-only record of every management action — who did what, when, and from where — with filters, search, and a note on what counts as auditable.
The audit log answers the question every organization eventually asks: who did that, and when? It records every management action — "who did what, when and from where" — in an append-only trail you can filter, search, and trust.
It's a first-class destination, not a settings tab: Audit log in the organization sidebar for the whole organization, and the same viewer pre-scoped inside each event (the event sidebar's Audit log), which is where most people actually use it.
Reading the log
Each row is one action, with columns for When, Who, Action, Target, and Details. Expand any entry for the full context, including the IP address and browser the action came from.
Who is one of four actor kinds, badged so you can tell a person from a process at a glance:
- Staff — a signed-in team member,
- API key — a partner integration,
- Scanner device — a gate,
- System — Bookitive itself (automatic expiries, matched payments, worker actions).
Filtering and search
- Who — narrow to one actor.
- Action — grouped into Credentials & API, Money, Orders, Events & seating, Team & roles, Protection, Exports, and Other — so "show me every money movement" is one click. (Scanner-device actions live under Credentials & API; Scanner device is a choice in the Who filter, not the Action one.)
- Target — the kind of thing acted on.
- Date range — a custom from/to date picker; set either end to bound the window.
- Search across actions and details for a reference or a name.
The log loads more as you scroll, so a busy organization's history stays responsive.
What's recorded — and what isn't
The log captures mutations (creating, changing, deleting, moving money, admitting, approving) and, deliberately, a few sensitive reads: exporting customers, orders, or attendees is logged, because pulling personal data out of Bookitive is an action an organization should be able to account for. Ordinary viewing — opening an order, browsing the dashboard — is not logged; it would bury the signal.
Writing to the log is the job of whatever service did the work, inside the same transaction — so an entry can't exist without the change it describes, and a change can't happen without its entry. The log is as reliable as the action itself.
Retention
Entries are kept for a configured period (one year by default) and then swept — the only process that ever removes audit rows. For organizations that need an indefinite record, retention can be set to keep forever.
Related
Attendee names
Require one name per ticket — printed on tickets and shown at check-in — plus the backfill action for tickets sold before you turned it on.
Analytics
The organization dashboard and the event's Overview, Sales, and Attendance tabs — date ranges, comparisons, benchmark events, and auto-generated insights.