History Logs allow you to view a history of changes made by admins in the admin console. Logs are available for orders, sessions, speakers, ticket settings, and badge designer setting changes.

The order history log will show a timeline of changes within the admin console. This can include payments, refunds, exchanges, cancellations, ticket buyer and holder information changes and more.

For other areas in the event (ticket settings, sessions, speakers, badge design), the history log will show a list of team members that made changes. This is arranged chronologically with the latest update on top. When you click the details, you'll see 2 columns to compare the previous and current settings.

When you click View on a log entry, a detail panel opens with two columns:

Here's an example for ticket settings history log:

If you open Log 2, the right column shows $100 (what was saved in that log). In the left column dropdown, you can then choose:

This lets you compare any two points in time — not just the immediate before and after.

In some history logs, you'll see a View changes link for some line items. Like for the Badge design history, this appears in the Design Json line item. When you open this link, what you'll expect is to see a comparison of the design changes in a JSON structured format.

If the update or change is not as straight forwards as increased the ticket price from $50 to $100, the JSON structured format will give you a more detailed information, like when a new element is added to the badge design, moved to a certain area, and then resized.

Example: You have 4 logs for the badge history.

When you open Log 1 or 2, you'll see only the basic design details including the badge size and margins. But when you open Log 3 where we know that the action done was to add the QR Code widget to the design, you'll see a View Changes button for Design Json.

When you open it, you'll see a comparison in JSON format. We choose a previous log on the left column to compare the before and after JSON. You can see that the code stops at Line 709 for the previous log (blank design loaded), and on the right side for Log 3, additional code appears and this is the code that indicates that the QR Code widget is added to the design.

Another example here is for the session settings history log's Post-Session Call to Action line item. Initially, the post-session call to action feature was not enabled in the session as seen in the left column. After it's enabled and routed to a specific booth in the expo, the JSON code on the right side showed that it's now enabled / true and indicated the destination.