Skip to content

Activity Logs & Audit Trail

Activity Logs record every action taken in your event — who made a change, what they changed, and when. This is essential for accountability, compliance, and debugging.

Go to Settings → Activity Log in the event sidebar.


Each activity log entry includes:

FieldDescription
TimestampWhen the action happened
UserWho performed the action
DescriptionHuman-readable summary of what happened
Activity TypeCreated, Updated, Deleted, Viewed, Exported, or Imported
PageWhich CMS page the action was performed on
IP AddressThe user’s IP address

TypeExamples
CreatedNew ticket created, new session added, new attendee registered
UpdatedTicket price changed, session time modified, attendee details edited
DeletedTicket type removed, session cancelled, registration deleted
ViewedSensitive data accessed (attendee details, payment info)
ExportedAttendee list exported, report downloaded
ImportedBulk attendee import, data upload

Click any log entry to see the full detail view:

  • Action description and timestamp
  • User name, email, and role
  • HTTP Method (GET, POST, PUT, DELETE)
  • User Agent (browser and device)
  • IP Address
  • Resource Type (ticket, session, attendee, etc.)

The most powerful feature — see exactly what changed:

FieldOld ValueNew Value
price99149
name”Early Bird""Early Bird Special”
endDate2026-03-152026-03-31

The diff view resolves internal IDs to human-readable names, so you see “VIP Ticket” instead of a database ObjectId.


Filter activity logs by:

  • Date range — see activity for a specific period
  • User — filter by team member
  • Activity type — show only creates, updates, or deletes
  • Page — filter by CMS section (tickets, sessions, etc.)

“Why did the ticket price change?” Search the activity log for ticket updates. You’ll see who changed the price, when, and what the old price was.

For regulated industries (healthcare, finance events), activity logs provide an audit trail proving who accessed what data and when.

If multiple team members manage the event, activity logs show who’s making changes. This prevents confusion when two people edit the same settings.

After the event, review the activity log to understand the timeline of changes — when sessions were added, when ticket prices were adjusted, when marketing campaigns triggered import activity.


  • Check logs when something seems wrong — if settings changed unexpectedly, the activity log tells you exactly what happened and who did it.
  • Review before major events — scan recent activity to make sure no unintended changes were made in the days before your event.
  • Use for training — show new team members the activity log so they understand that all actions are tracked. This promotes careful, deliberate changes.