Skip to main content

Audit Logs in Whippy

Use Audit logs to review user actions, system events, and configuration changes across your organization.

Written by Maria Cairns

Why it matters

Audit logs help admins understand what changed, who was involved, where the action came from, and when it happened.

Key Concepts

User: The user associated with the logged event, shown with a user avatar where available.

Event: The action recorded by the audit log.

Geolocation and Date: Geolocation shows city and country when available. Date shows when the event occurred.

Step-by-Step: Search audit logs

  1. Open Settings > Audit logs.

  2. Review the User, Event, Geolocation, and Date columns.

  3. Use Search logs... to search the log list.

  4. Use available filters such as Event, User, or Date when you need a narrower view.

  5. Open geolocation details where available if you need more context.

  6. Clear search or filters to return to the full log list.

Tips and Best Practices

  • Use search for quick investigations and filters for repeated reviews.

  • Check Date when investigating a specific report or support issue.

  • Treat missing geolocation as a signal that location data was not available, not that the event failed.

  • Use audit logs as evidence, then confirm details in the relevant Settings area.

Troubleshooting

Issue

Possible Cause

Fix

No audit logs match that search

The search term or filters may be too narrow.

Clear the search and remove filters, then try a broader term.

Geolocation shows a dash

No geolocation data is available for that event.

Use the User, Event, and Date columns for the investigation.

Expected event is missing

The event may not be logged, may fall outside the current filters, or may have a different event label.

Clear filters, search by user, and review nearby dates.

Did this answer your question?