Activity and record history

Find out who changed a record and use the appropriate history to understand what happened.

Needs: Core

The Audits area lists recorded application activity. Individual records also keep histories for their own work, such as ticket conversations, employee changes and invoice payments. Use the history closest to the question you are investigating.

Find an event

Open Audits or the relevant record and filter by the available person, action, record and date fields. Begin with a known record number or approximate time, then open the source record to understand the event in context.

Your view may be limited to your own activity unless you have audit-view or administrative permission. Check the filters and permissions if no results appear.

Choose the right history

Read the ticket conversation for customer replies and service events, payment history for receipts, employee history for profile changes and Security activity for sign-ins. Those detailed records often explain more than a general audit entry.

Pay-related information remains subject to HR pay permissions. Exporting audit data should not be used to work around a restricted HR view.

Understand what a log establishes

A log shows events the application recorded and the information captured with them. It does not automatically provide a complete, immutable forensic archive or prove that a recipient read a message.

For a deeper incident investigation, preserve relevant application and server records through your normal process. Once the cause is understood, correct the underlying permission or procedure and test the change with a controlled example.