The Audit Trail gives your team a searchable record of activity across your organization. Instead of contacting Support to find out who changed a ticket price, processed a refund, updated an order, or changed a staff member's access, you can look it up directly from the dashboard.

The Audit Trail can help you:

The Audit Trail appears in four places, depending on what you're trying to investigate.

Think of it as moving from specific to broad: use a History tab when you already know the production or order involved, User Activity when you know the person, and the Audit Log when you want the full organizational picture.

Audit Trail entries use a consistent format across the different views.

Each entry shows:

For example, instead of simply telling you that a ticket tier was edited, an entry may explain that a staff member changed the General Admission ticket price from one amount to another.

Recent activity uses relative timestamps, such as:

Activity older than 24 hours displays the full date and time.

Hover over a timestamp when you need the exact date and time.

Not every change is made by a person.

When the OTS platform performs an action automatically:

This makes automated platform activity easy to distinguish from staff activity.

In views containing activity from multiple productions or orders, entries include a link to the affected record. Icons help identify what kind of record you're looking at:

Click the entity link to jump directly to the related production, order, or record.

Some Audit Trail entries contain more detail than what's visible in the initial summary.

If you see a chevron on the right side of an entry:

If a value was newly created, the BEFORE column displays a dash. If a value was removed, the AFTER column displays a dash.

No chevron? Field-level details aren't available for every action. The main activity summary still tells you what happened.

The Audit Trail can also record actions that someone attempted but didn't successfully complete.

For example, an entry may indicate that a staff member attempted to change a ticket price but that the change was not saved.

Failed attempts appear alongside successful actions so you have a more complete picture of what happened in the account.

Removing a staff member doesn't remove their historical activity.

If a user has been deleted:

Use the Production History tab when your question is about one specific show.

For example:

Who changed the ticket price on Friday night's performance?

History appears after Details, Schedule, Tickets, Orders, and Reports.

The tab shows a reverse-chronological list of production activity, including:

Activity is grouped by date, such as Today, Yesterday, or a specific date, with the newest group first.

You can filter by:

During the run is unique to productions. It automatically uses the first and last performance dates as the date range, making it useful for post-show reviews.

When filters are active, use Clear filters to reset the view.

Use the Order History tab when you need to investigate activity on one specific order.

For example:

Who processed this refund?

or

Who exchanged these tickets?

Order History can include:

Activity appears in reverse chronological order and is grouped by date.

When field-level information is available for a refund, click the entry's chevron to see details such as the refund amount and payment status change.

The History tab and Payment History serve different purposes.

The two views work together rather than replacing one another.

Use User Activity when you want to see what one staff member has been doing.

Permissions: Admins and Owners can view another staff member's activity. Any staff member can view their own activity.

The page includes information about the staff member, including:

You'll also see summary information for the selected filter period:

You can filter by:

Date options include All time, Last 7 days, Last 30 days, Last 90 days, and a custom range. Entity types include Productions, Orders, Contacts, Organization Settings, and Users.

The Audit Log gives Admins and Owners the broadest view of what's happening across the organization.

By default, the page shows activity from the last 7 days, grouped by date. Each date heading includes the number of activities recorded, and a summary shows the total number of matching entries.

The org-wide Audit Log includes the most extensive filtering options:

The Staff member filter also includes System, allowing you to isolate automated activity. The Source filter lets you choose between:

Turn on High-stakes only when you want to focus on consequential changes and remove routine activity from the feed.

High-stakes actions include:

Tip: This is especially useful when you need a quick review of significant account activity—for example, checking what happened over a busy weekend.

CSV export is available from:

The exported file respects your currently selected filters, so set the date range, categories, or other filters you need before exporting.

The CSV contains:

Dates and times use your organization's configured timezone, or UTC if no timezone has been configured. For large exports, the export button enters a loading state while the file is prepared and downloads automatically when ready.

The History tab appears after the Audit Trail feature has been enabled for your organization.

If it's missing, confirm that the feature has been rolled out to your account.

The Audit Trail starts recording activity after the feature is enabled.

Actions that happened before the feature was enabled aren't added retroactively.

The org-wide Audit Log and another user's activity require an Admin or Owner role.

Check your role under:

Admin Settings → User Management

Any staff member can view their own activity.

The person has been removed from the system.

Their historical actions are preserved, but their identifying account information is no longer displayed.

Not every activity type currently supports field-level before-and-after details.

If there's no chevron, use the entry's summary to see what happened. This is expected for action types that don't yet have detailed change tracking.

Large exports can take longer to prepare, especially for busy organizations or long date ranges.

You can continue using the page while the export processes. To speed things up, try narrowing the date range or applying additional filters before exporting.