The Audit Feature

Katrin Geske
Katrin Geske
  • Updated

babelforce comes with a full audit feature which allows you to revisit change conducted in your account.

Enabling the Audit log

Under Global > Settings Audit log settings you can select Enable audit on every request. Also, if your company has strict privacy compliance rules, you can decide to Hide user information. If you activate this, logs will still be stored but without the reference to the user who did the changes.

mceclip0.png

 

Reading the Audit logs

If you have worked with versioning tools like Git, it will be easy for you to read the logs. If not, it might be a bit hard in the beginning, but no worries, we are here to explain.

You find the log in the section Reporting > Audit log

There you have a range of options:

  • Select a date
  • Filter by resource
    • Agent
    • Module
    • Business Hours
    • Etc.
  • Select the operation
    • Created
    • Deleted
    • Update
  • Search for a specific user in the free search field

mceclip1.png

To view a log, click on the little arrow next to the date. 

The first page is usually not very interesting if you are just looking for the change. It represents the payload which is the current status of the resource, meaning all settings of a Global Automation for instance. You want to know more about payload? Here is a link to Wikipedia. 

mceclip3.png

If you now click on "Dif" you are going to see what's actually relevant.

For instance, in our little example, the Global Automation was changed on Dec 2nd, at 15:35 (the time always represents your browser time). Two changes happened. The old version, in red, is on the left, the new, in green, on the right. 

What happened:

  • The automation was disabled (enabled: false)
  • The Trigger changed 

mceclip4.png

 

 

 

Was this article helpful?

/

Comments

0 comments

Please sign in to leave a comment.