The audit log

When something needs explaining — who issued that refund, when was that data deleted — the Audit log has the answer. It's a running record of the important things that happen in your organisation.

What gets recorded

The audit log captures actions that matter, grouped roughly as follows:

• Orders & payments — refunds (issued or failed), manual payment confirmations, order edits, cancellations and expiries by an admin, invoicing changes, invoices generated, add-ons fulfilled, POS orders
• Tickets & check-in — tickets resent, ticket form data edited, ticket transfers, manual check-ins and reverted check-ins from the dashboard, waitlist entries removed
• Attendee data — data exported, deleted or rectified (GDPR requests), retention purges, CSV exports
• Events — events created, updated, cancelled or deleted, plus every change to ticket types, discount codes, access codes, add-ons, capacity pools, gates, locations, event templates, promo links, passes and widgets
• Communication — broadcasts and custom emails sent, email templates created, updated or deleted
• Team — invitations sent, revoked or accepted, members removed, role changes, and platform-support impersonation sessions
• Organisation settings — general settings, subscription changes, payment provider connections, custom and email sending domains, marketing integrations, API keys and webhooks

Each entry carries a timestamp, the user who did it (or System for automated actions such as a subscription change coming from Stripe), the affected record and the IP address. Use the action filter at the top of the page to narrow the list to one type of action.

Why it helps

Two things, mainly:

1. Accountability — in a team, you can see who did what, which keeps everyone aligned and surfaces mistakes early.
2. A clear history — when a customer, a colleague or a regulator asks what happened, you have a factual, time-stamped trail instead of guesswork.