Skip to main content
The console keeps a complete audit trail. Every successful change made through the console is recorded automatically — creating an event, publishing a ticket type, changing a member’s role, disabling a redemption code. Recording is always on. New features are audited as they ship. Each entry records:
  • Time — when it happened.
  • Actor — the signed-in member who did it.
  • Action — what kind of change (create, update, and so on).
  • Scope — where it applies: the organization, one Business Unit, or one event.
  • Subject — the object that was changed, with a Details view of the recorded entry.
Reading the log requires no extra setup. The console writes entries automatically.

​
Three views of one trail

The same trail is readable at three levels:
Audit log in the organization section shows every console operation across the organization — actor, action, scope, and time. This is the governance view, available to organization owners and admins: organization-wide change review and compliance.
Each Business Unit has its own Audit log page showing only that unit’s slice of the trail. A unit’s admins see that team’s history, not the rest of the organization.
Each event has an Audit log page in its navigation: operations on that event — ticket types, codes, perks, forms, and registrations. Use this to find who changed a ticket type’s capacity.

​
Filtering

Large organizations generate a lot of entries. The Filter bar above the log accepts simple conditions joined with AND — the hint under the field lists the exact syntax. Narrow by the kind of object, the action, the actor, the Business Unit or event, and a date range, then choose Apply. Typical questions the filter answers:
  • Everything one person did in the last month.
  • All changes to redemption codes across an event.
  • Every role change in a Business Unit since a given date.

​
Rules to know

  • The log is append-only. Entries cannot be edited or deleted, by anyone. That is what makes it an audit trail rather than a notes field.
  • Only successful changes are recorded. A rejected or failed attempt did not change anything, so it does not appear.
  • Reads are not logged. The trail records changes, not who looked at what.
  • The organization-wide view is for owners and admins. Members see the slices their Business Unit roles give them access to.
  • Some pages include a timeline written for reading. An attendee’s detail page, for example, shows a registration activity timeline — approvals, status changes — while the audit log stays the formal ledger. For a readable timeline, use the page. For the formal record, use the log.
When a ticket type is off sale or a code is disabled, check the event’s audit log first. Actor, action, and time are usually sufficient.