Skip to main content

Track All Admin Changes with the Audit Log

Niha U
  • Updated

The Audit Log acts as your system’s audit trail, giving you a clear, time-stamped snapshot of every change made by every user.

Accessing the Audit Log

  1. Open the Admin App
  2. Navigate to Configuration > Audit Log.
  3. The main Audit Log table appears with filters at the top.

Columns in the Audit Log

The log displays a list of actions performed within the system. Each entry includes:

Field Description
Date & Time When the change happened
User Type Super Admin / Admin
Username/Email Who performed the action
Action Type of change (e.g., Update)
Module Which module was affected (phone-tree, call-queue, agent, etc)
Affected Entity Specific item updated (e.g., Whisper Message, Extensions)
Result Success / Failed
View Link to detailed info

Using Filters

The Audit Log includes filters to help you quickly narrow down entries:

  • Location – View actions within specific practice locations
  • User Types – Filter by Admin or Super Admin
  • Date Range – Last week, last month, or a custom period

These filters make it easy to audit changes for compliance reviews or issue investigations. You can also use the search bar to quickly locate any log. 

Viewing Detailed Logs

  • Click View on any entry to open the Log Details pop-up.

The detailed view includes:

1. User & Session Information

  • Performed By – Email of the user
  • Role – Admin or Super Admin
  • IP Address – Helps identify the device/network used
  • User Location – Practice or location tied to the action
  • Accessed From – Browser and OS (e.g., Chrome on Windows)

2. Change Information

  • Action Type – Update, Delete, Create
  • Status – Success or Failed
  • Affected Module – phone-tree, call-queue, ring-group, etc.
  • Affected Entities – Specific configuration elements

3. Old Value vs New Value

This information is displayed side-by-side:

Old Value New Value
Welcome-FD.Mp3 Callback CQ

This helps identify exactly what changed—critical for debugging and compliance.

Why the Audit Log Matters

  • Track unauthorized changes
  • Investigate configuration issues
  • Verify who updated the settings
  • Maintain security and compliance
  • Understand operational changes across teams

Example Use Cases

  • A phone tree stops working → check if someone changed a whisper message.
  • A Call Queue behaves differently → verify if settings were modified.
  • Need to review all updates for a location → apply filters and export (if enabled).
  • Security audit → validate IP addresses and user actions.

Tips for Admins

  • Review the audit log weekly for high-usage practices.
  • Use the filter by location feature for multi-practice setups.
  • Pay attention to unexpected IP addresses.
  • When a user reports “something changed”, the Audit Log is your first stop.

Support / Contact

Need further help? Contact support@voicestack.com  or call 407-833-6436.

Related articles