Audit Logs

The Audit Logs section maintains records of each activity a user performs in Quickwork, regardless of a free or a paid user. Through audit logs, a user gets the ability to view and track all the operations performed on various components such as journey, folder, connection, and Team. The user can also view details of the user's login/out from the account. All these details are recorded with the name of a user, time, the IP address of a system, and browser details through which the user accessed the Quickwork account.

To view the logs of your account, click the Dashboard tab. The Audit Logs tab appears with a timestamp filter as Last 30 days by default:

You can view the logs ranging from the last hour to the last 30 days. To bring granularity, Quickwork allows filtering the logs through a specific resource, event, or user with respect to the timestamp of each, respectively. If there is no activity performed by a user for a specific time for a specific resource and its event, Quickwork will have no logs recorded and you’ll be asked to change filters accordingly:

Available resources to filter:

1. Journey

2. Folder

3. Connection

4. User

5. Team

Activities performed by a user in a journey, folder, and connection are considered as account-level logs, whereas logs of a user and team are considered as organization-level logs. Each resource has a set of associated events. Let’s look at the following image:

This image shows the audit logs of all the journeys updated in the last 30 days. Hence, the timestamp filter is Last 30 days, the resource filter is Journey, and its associated event is Journey updated. Each log shows five pieces of information:

1. The operation performed: In the case of journey logs, you’ll get the operation being performed on a journey present in a specific folder. E.g., Journey Shopify session 14 (Part 3) was started in session as shown in the above image. The user can easily navigate to a journey and folder by clicking their respective names.

2. The name of the user: The name of the user who performed the operation. It changes as per the user name selected in the filter.

3. Timestamp: The date and time when the operation was performed.

4. IP address: The IP address of the user’s system.

5. System information: The system and browser information of the user.

Filtering events for a resource

Depending on the operational bandwidth of a resource, events are associated accordingly as a filter option. For example, the Journey resource is associated with full-fledged events, i.e., from start to stop a journey. This resource has higher operational points as compared to operations performed on a folder or a connection:

Similarly, a user can perform numerous operations in a team such as adding members, deleting them, changing their roles, sending invitations, accepting invitations, etc. The events filter displays such operations and filter events. Also, you can see the name of the team members added to your team in the user filter:

The Folder and Connection resources have simple operations such as creating/deleting/renaming a folder and creating/disconnecting/switching a connection.

Limitations

A team member of any role has no permission to view the audit logs of the inviter. There are no custom filters that can be added to the audit logs of an account.