To ensure compliance, most audit log columns aren't configurable. However, you can customize some columns to help with organization and readability. To export an audit log, visit Exporting and downloading audit logs.
Customize audit log exports
You can customize audit logs by adding or removing optional columns. You can also choose how some columns display, like timestamps.
To customize your audit logs:
- Click your avatar in the bottom-left corner and select Tenant Admin Console.
- Click the Settings tab, then select Configurations.
- [Optional] Customize fields using their respective drop-down menus in the Data Management section.
- [Optional] In the Audit log columns section, click Select columns to export, then select any non-required columns to display or not display in audit log exports. Required columns can't be deselected.
View an audit log
Audit logs render in an intuitive format that includes one update per row, before and after changes in separate columns, and consistent formatting across all change events, including the removal of JSON formatting.
The table below describes each column in the audit log, what they represent, and if the column is required for compliance. Optional columns can be added or removed from audit log exports. Columns marked with an asterisk ( * ) are customizable.
|
Audit log column |
Required |
Column description |
|
Timestamp (UTC)* |
Yes |
Datetime of an update in either:
|
|
Name |
No |
First and last name of the user that made the update |
|
User |
Yes |
Username for the account that made the update. This could be a person or service account |
|
Transaction ID |
No |
ID that groups related updates initiated by the same action |
|
Event Description |
Yes |
Overview of the update, including the audited object type |
|
Action |
Yes |
The object property that was updated |
|
Old Value |
Yes |
If an update is made, the previous value is stored. If a deletion occurs, the removed value is stored |
|
New Value |
Yes |
If an update is made, the new value is stored. If a creation occurs, the added value is stored |
|
Item |
Yes |
Name of the updated object |
|
Item Developer ID |
No |
Object API ID |
|
Item ID |
No |
Benchling ID For example, Registry ID, Experiment ID or barcode |
|
Item Type |
No |
Type of object |
|
Electronically signed |
Yes |
|
|
Parent Item 1 Parent Item 2 Parent Item 3 |
No |
Related objects that help identify where the update happened Note: An updated object can have up to three parents, but often has fewer or none. For example, a Result table row has the following parents: Parent Item 1: the Result table where the row is found Parent Item 2: the entry where the result table (and relevant row) is found |
|
Parent Item 1 Developer ID Parent Item 2 Developer ID Parent Item 3 Developer ID |
No |
API ID for corresponding parent |
|
Parent Item 1 Type Parent Item 2 Type Parent Item 3 Type |
No |
Object type of corresponding parent |
|
Reason code |
Yes |
|
|
Comment |
Yes |
|
|
Delegate User |
No |
Benchling team member acting as Benchling Support on the tenant |