As you populate Planhat with filters, automations, custom fields, and more, tracing changes to objects becomes increasingly important. You may notice a Company with an erroneous status, or a License with an unexpected value. You want to know - is this a systematic issue, perhaps caused by a mistake in an automation or an incorrect value imported via integration, or is this a discrete event, caused by human error?

You can drill down into logs to trace exactly what caused an update or creation of a Company, License or any other object throughout the app, as well as where the update originated.

You can filter by Company, Object type, Action, Actor, and Date (subject to the logs history limit on your account). You can also text-search logs, as well as right-clicking on a particular record name, and selecting "view logs" to filter on that particular record.

You simply go to the ellipsis of any record, and select "view logs". For Companies, End Users, and Users, you can access logs through the ellipsis in the top right corner of their respective Profiles.

You can also access the Logs Explorer from the Command Box - electing to "view logs" for a specific record you searched for, or selecting the general Logs Explorer button at the bottom of the Command Box.