Skip to content
  • There are no suggestions because the search field is empty.

Audit Log Report - Filter Guide

The Audit Log report (Staff → Reports → Audit Log) lets administrators track who changed what, when, and where across supported modules and settings.

Each audit entry can include:

  • Date & Time of the change
  • Changed By (user who made the change)
  • Field / Property changed
  • Old Value
  • New Value
  • Affected User (for user-specific updates)

When to Use This Report

Use the Audit Log when you need to:

  • Investigate unexpected configuration or profile changes
  • Confirm who made a change and when
  • Review changes during release windows
  • Support internal compliance/audit requests

Filter Reference

1. Date From

  • What it does: Sets the start of the reporting period.

  • Use it for: Investigations beginning from a specific date/time.

2. Date To

  • What it does: Sets the end of the reporting period.

     

  • Use it for: Limiting results up to a specific date/time.

3. Module

  • What it does: Filters by product area where the change occurred (e.g., Staff, TimeOff, Warnings, Performance, Time-Clock, Time-Sheet).

     

  • Use it for: Module-specific troubleshooting or audits.

4. Changed By

  • What it does: Filters by the user/admin who made the change.

     

  • Use it for: Verifying actions performed by a specific administrator.

5. Affected User

  • What it does: Filters entries to a specific employee/user record that was changed.

     

  • Use it for: User-specific investigations (profile updates, approval hierarchy changes, TimeOff user settings, etc.).

6. Field / Property

  • Default: All Fields/Properties

     

  • What it does: Filters by the exact field/property that changed (e.g., Manager, Approval Hierarchy, profile field, accrual setting).

     

  • Use it for: Pinpointing a known field change.

7. All Fields/Properties

  • What it does: Default “no restriction” option for Field / Property.

     

  • Use it for: Viewing changes across all fields/properties.

8. Entity / Object Type

  • Default: All Entity Types

     

  • What it does: Filters by the record type that changed (e.g., account setting, policy, user setting, profile object).

     

  • Use it for: Focusing on a specific type of business object.

9. All Entity Types

  • What it does: Default “no restriction” option for Entity / Object Type.

     

  • Use it for: Broad reviews across all object types.

10. Smart Search

  • What it does: Keyword search across relevant audit log content (such as names, field/property text, and values, depending on implementation).

     

  • Use it for: Fast discovery when you have partial information.

     

Examples:

  • Search employee name to find user-related changes
  • Search “manager” to locate hierarchy updates
  • Search a specific value to identify when it was applied

Notes: The Audit Log implementation includes tracking for major settings/profile changes across supported modules, including user and account settings.
Some data types may be excluded by design based on implementation scope.


Best Practices

  1. Always set a date range first to keep results relevant.
  2. Add Module or Entity / Object Type next to narrow scope.
  3. Use Changed By or Affected User for accountability/user tracing.
  4. Use Field / Property when you need exact precision.
  5. Use Smart Search for quick discovery, then refine with structured filters.

Quick FAQ

Q: Why am I getting too many results?
A: Start with Date From/Date To, then add Module and Entity / Object Type.

Q: I know the user but not the field changed. What should I use?
A: Use Affected User + date range, then add Smart Search keywords.

Q: I know the field changed but not who changed it.
A: Use Field / Property + date range; optionally add Module for faster narrowing.