How to Use the Audit Log

Available for

✗ Prey Tracking
✗ Prey Protection
✔︎ Prey Full Suite

If you have multiple users working on your Prey platform or share management responsibility with another person, the Audit Log will come in handy to help keep track of what modifications and actions were taken on the platform, when, and who did them in the first place.

In a nutshell, the Audit Log is an event registry that keeps account of what actions and setting modifications were taken by every user, both admin and regular, connected to your main account.

IMPORTANT: This feature is only available for the account's administrator. If you don't have Admins enabled, check out this article.

Where to Find the Audit Log

Log into your account at the Online Panel, there you can access the SETTINGS tab on the left-hand menu, where you will find the AUDIT LOG access. Click it to enter the log's view.

Here you will see the complete current record of events, which by default displays all events, for all users, in the current day. These are seen on the table and include the following information:
  • Date and time of execution
  • Event details and changes
  • The IP of the session that made the change
  • The logged-in user who made the change

Using the Audit Log Filters

There are three types of filters you can apply to the audit log: a date filter, an event type filter, and a user filter.

Date Filter: Pick a period of time and see all events registered during the said period.

Event Filter: Choose specific types of events, such as log-ins, to view. These filters are automatically generated when a new type of event is registered, meaning that if an action hasn't occurred yet you won't be able to see or select that event filter. 

User Filter: Filters the event table by the user who executed the action. Useful when you want to oversee general account activity, or when you want to if a user made a change you didn't authorize.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.