Audit Logs
You can generate audit log reports to track user actions in Workforce Management (WFM).
To access Audit Logs, go to Workforce Management > Reports. Click Audit Logs.
You can use audit logs to meet the following goals:
-
View who published a schedule and the date and time it was published
-
View who unpublished a schedule and when, such as when amendments are made to shifts
-
Check whether any changes were made to shifts, including reassigning employees and changing times
-
Check payroll to see if shifts were added after a shift export was run
-
View who approved a leave or availability and when it was approved
-
Pinpoint if someone made changes to external integration configurations, such as unlinked Xero or MYOB locations or employees
-
View changes to employee personal details
You can filter audit logs according to the following:
-
Action – Filters logs based on specific actions.
-
Date – Filters logs based on on a specific date or period..
-
Anyone – Filters logs based on the user.
-
Type – Filters logs according to the Table column, which specifies the generic data type the user changed, such as Agreement, Brand, or Condition.
The Audit Logs page lists user actions starting with the most recent.
The following table shows the data available in audit logs.
|
Data |
Description |
Content |
|---|---|---|
|
Action |
Shows the type of action performed. |
Actions may include:
|
|
Timestamp |
Shows the date and time the action was performed based on your current timezone. If you download the CSV log, however, the timestamp shows time in GMT. |
N/A |
|
User |
Shows the user who performed the action. |
N/A |
|
IP address |
Shows the network IP address of the user who made the action. |
The red numbers or letters after the IP address is a unique session or instance ID. This ID is used to identify actions that were made in the same logged in session. For example, if a user logs in, makes a change, logs out, and then logs in again, the instance ID of the actions in the first session will be different from that of the actions in the second session. |
|
Instance |
Shows the specific field that was changed in relation to the Table column. |
Some examples that may appear in this row include:
|
|
Table |
Shows the general type of data field that the user changed, which was specified in the Instance column. |
Some examples are:
|
|
Changes |
Shows the change made as a comparison between the original value and the updated value. If there was no data there originally then it will show a blank value. |
N/A |
Sample Audit Log
To better understand how to interpret audit logs, refer to the following table.
|
Action |
Timestamp |
User |
IP Address |
Instance |
Table |
Changes |
|---|---|---|---|---|---|---|
|
Insert |
May 21, 2019, 10:57 a.m. 2 days ago |
Jasmine Connor |
61.68.198.142 qd7dl8... |
Blacktown [week 21 2019] |
Released Roster |
week: no value => 21 releaser: no value => Jasmine Connor 236752 location: no value => Blacktown 11695 id: no value => 742180 year: no value => 2019 |
|
Update |
May 21, 2019, 10:55 a.m. 2 days ago |
Jasmine Connor |
61.68.198.142 qd7dl8... |
[26991351] Matthew Townsend @ Blacktown 2019-05-30 9:30 am to 2:30 pm |
Rostered Shift |
person: Casey Gleeson 236259 => Matthew Townsend |
|
Update |
May 21, 2019, 10:54 a.m. 2 days ago |
Jasmine Connor |
61.68.198.102 3m1j2n... |
Vanessa Piong |
Person |
email: vpiong@ |
The first instance is for a location with week number attached. It is on the Released Roster table, meaning a roster or schedule has been released or sent out. The schedule is for Blacktown on week 21 in 2019.
The second instance is for an employee name at a location with a shift on May 30, 2019. Based on the Table column, this instance is for a scheduled shift. A user reassigned this shift that was previously for Casey.
The third instance is for an employees name based on the Personal table. The personal details field was changed. Based on the Changes column, the email address was updated.