Administration

Change tracking

Every admin change is logged with who changed what, and from which IP address.

When something in a phone system stops working the way it should, the first useful question is: what changed, and who changed it? Voxbi keeps a complete, tamper-proof record of every configuration change made in the Voxbi Cockpit. Each entry shows the timestamp, the user who made the change, the type of action (create, update, delete, or restore), the object that was affected, and the before-and-after values so you can see exactly what moved.

The change log is available across the whole system and also at the level of individual objects. Open any user, extension, or SIP device and the change log tab shows the full history for that record alone. This makes it straightforward to answer the question "what happened to this user's setup?" without scrolling through a system-wide list.

When you'd use change tracking

  • An IT administrator needs to find out why a call flow stopped routing correctly after a Friday afternoon. The change log shows every setting touched that day, by whom, so the cause is easy to identify and reverse.

  • A compliance team preparing for an audit needs to demonstrate that administrative access to the phone system is controlled and monitored. Exporting the log provides a dated, user-attributed record of all configuration activity.

  • A multi-administrator organisation wants accountability across the team. If a queue ring policy or an IVR menu is changed unexpectedly, the log shows which administrator made the edit so you can discuss it rather than guess.

How change tracking works in Voxbi

  1. Every change is logged automatically

    There is nothing to switch on. Every create, update, delete, or restore action that any administrator performs in the Voxbi Cockpit is written to the log immediately, including the IP address of the session.

  2. Filter to what matters

    The change log can be filtered by user, by time period, and by object type, so you can narrow from the full system history down to the specific record or person you are investigating without scrolling through unrelated entries.

  3. Read the before-and-after detail

    Each entry expands to show the old value and the new value side by side. This means you can confirm exactly what was changed, not just that something was changed.

  4. Export for audit or backup

    The log can be exported for use in compliance reports or external storage. The log itself cannot be deleted or edited from within Voxbi, which preserves its integrity as an audit record.

Frequently asked questions

Can administrators delete or edit entries in the change log?

No. The change log is append-only and cannot be deleted or modified from within the Voxbi Cockpit. This is deliberate: it preserves the log's value as an audit record and means you can trust that what you see is a complete and unaltered history.

Does the log cover all parts of the phone system?

The change log covers configuration changes made in the Voxbi Cockpit: users, extensions, SIP devices, call flows, queues, schedules, integrations, and PBX settings, among others. Each object type also has its own change log tab so you can view history at the record level.

How far back does the log go?

The log retains all changes without a fixed cutoff, so you can search back through the full history of your configuration. For very long-running installations, using the date filter is the practical way to narrow the results.

Is the IP address of each change recorded?

Yes. Each log entry includes the IP address of the session that made the change, in addition to the user account. This supports security investigations where you need to check whether a change was made from an expected location.

See Voxbi in your business.

Talk to us or to a certified Voxbi partner.