Information |
| Status | Approved |
|---|
| Main |
|
|---|
Attachment |
|---|
| Attachment |
|---|
| Attachment |
|---|
| Attachment |
|---|
| Attachment |
|---|
The audit log provides a comprehensive record of the deal that can be exported to a central document / matter management system once the deal has closed, to ensure compliance with record keeping requirements for client matters.
Each Transact deal now has an Audit log and an Activity log. These are the key distinctions between the two features.
|
|
Activity Log |
Audit Log |
|
How is it accessible? |
In the Dashboard for the deal within the user interface. |
Exportable in CSV format from the Settings page within the deal.* |
|
What is the objective? |
To keep deal participants updated on key events as they work through the deal in a user-friendly readable view. |
To provide a comprehensive record of all activity for record-keeping and archiving purposes. |
|
What events does it track? |
Selected key deal events relating to files, status notes, participants joining./leaving etc. |
Almost every action undertaken in the workspace is tracked. The only action not tracked at the date of first release are participant invitations being sent. |
|
Who can access it? |
Any deal participant. The events listed are filtered based on access restrictions applied in the deal. |
Deal admins only. |
Workshare started collecting data for Transact audit logs on 6 April 2019. Information about activity before this date is not available. Audit logs for transactions created prior to this date are exportable, but will not show any events taking place before this date.
The audit log tracks full details of the following events. Full details of the events are recorded (such as content of status notes, identity of relevant participants, etc.).
Actions tracked from 6 April 2019 (the release date of the audit log feature itself):Actions tracked from 10 July 2019 (the release date for the grouping of participants and approvals):
The audit log does not currently track the sending of invitations to join the deal (although join / leave events are tracked).
Note: As functionality in Transact is extended, appropriate events will be added to the audit log and we will amend this note appropriately to give full details.
The audit log is generated as a CSV file. Each row in the file represents an event or action with the following properties:
|
Property |
Description |
|---|---|
|
Time |
The exact moment the action takes place. |
|
Correlation ID |
An ID for the action. |
|
Agent Name |
The user name of the person performing the action. |
|
Agent Email |
The email address of the person performing the action. |
|
Agent UUID |
The unique identifier of the person performing the action. |
|
Action |
The action type performed, such as create folder, delete file. The user could perform one action, such as copy file, but this would be listed as two actions – copy and create. |
|
Resource Type |
The item the action was performed on. This could be the deal, a folder, a document, a draft version or other version type, a participant, etc. (Please note that “document” here means a document (or item) in the checklist, rather than a file.) |
|
Resource Name |
The name of the item the action was performed on. If the resource is folder, folder permissions or folder members, this will be the name of the folder. If the resource is file or file comparison, this will be the name of the file. |
|
Resource UUID |
The unique identifier of the item the action was performed on. |
|
Parent Type |
The resource type of the parent of the item the action was performed on. For example, when the audit log tracks a file upload, the parent is the checklist document/item the file is uploaded to. |
|
Parent Name |
The name of the parent of the item the action was performed on. For example, when the audit log tracks a file upload (eg Version 1), the parent name is the name of the checklist document/item the file is uploaded to (eg A1: Share Purchase Agreement). |
|
Parent UUID |
The unique identifier of the parent. |
|
IP |
The IP address of the computer of the person performing the action. |
|
User Agent |
The user agent of the software that is making the request to the application (this could provide information relating the end users’s browser and related software, or an internal Worskhare application microservice). |
|
Info |
Additional information. For example, this will track the original filename of a file uploaded (as opposed to its given Transact filename), the content of the status note added, etc. |
If you would like assistance in interpreting the audit log please contact us at transact@workshare.com.