Study audit log

Achala
Achala
  • Updated

The In Vivo study audit log feature provides end-users with comprehensive insights into study modifications, enhancing quality control and troubleshooting. This article outlines how to utilize the audit log feature, including exporting logs and managing event records.

 

Key Features 

Detailed Audit Trails

End users with at least read-only access can export logs detailing all significant actions taken within a study, such as creations, deletions, and modifications of samples, measurements, 

Record Reason for Change

When enabled, users are required to enter a reason for any edit or deletion of core entities (e.g., measurements, samples). This reason must consist of at least three characters. Unlike previous protocols, users no longer need to type "DELETE" to confirm deletions. For bulk actions, like sample collection or measurement edits, the reason for change will be recorded automatically. 

 

Enabling the Audit Log

To activate the Audit Log for your tenant, contact support@benchling.com. This feature must be enabled to begin tracking and exporting logs.

Exporting Audit Logs

1. Navigate to the exports section within the study interface.

2. Click the 'Generate audit log' button. An email will be sent once the file is ready, containing a link to download the audit log from the attachments section of the study.

3. Each time the  'Generate audit log' button is clicked, the CSV file is updated with a new version.

 

 

Additional Audit Log Details

  • This log will initially only track created, updated, and deleted events for specific entities like measurements, samples, observations, doses, and changes to animal living status.
  • The 'Reason for Change' must be entered for all edits or deletions.  If not needed, this feature can be enabled or disabled upon request.
  • The audit log is available exclusively in CSV format. PDF exports are not supported at this time.

 

FAQ

Q: Can the audit logs sync with Benchling core tenants?

  • No, In Vivo Audit logs are only available from the In Vivo Tenant. Core tenant Audit logs of the synced entity do not contain the same information found in the In Vivo study audit log which is user actions rather than actions performed by the In Vivo sync application.
  • Export from In Vivo as the source of truth for all In Vivo study data.

Q: Will more events be added to the audit log?

  • Yes, we plan to continue to add events over time including, but not limited to, changes to animal details and study design or status.
  • If there are particular events that you would like to have included please raise this with your benchling representative or contact support@benchling.com

 

Was this article helpful?

Have more questions? Submit a request