To ensure compliance with GxP regulations, the Tetra Data Platform (TDP) provides an Audit Trail for user actions that create, modify, or logically delete electronic records. The Audit Trail can also be configured to require a reason for change.
As an Admin, you can enable or disable the following features:
- Audit Trail
- Change Reason enabled in Audit Trail
Audit Trail is activated for each organization by default. Change Reason enabled in Audit Trail is not activated by default. To set up change reason logging, you must activate it on the Compliance Settings page.
As an Admin, you can enable or disable compliance settings for an organization from the Organization details page.
To enable compliance settings for an organization, do the following:
- Sign in to the TDP as an admin.
- In the left navigation pane, select the hamburger menu icon. Then, choose Administration.
- Choose Organization Settings. The Organization Settings page opens.
- In the AUDIT TRAIL section, choose Edit. The Edit Audit Trail Settings dialog appears. By default, Audit Trail is set to Enabled and Change Reason enabled in Audit Trail is set to Disabled.
As an Admin, you can enable or disable whether to track and log user actions for an organization into an audit trail. The Audit Trail setting is enabled by default. For instructions on how to access and review your audit trail in the TDP, see Audit Trail.
Disabling the Audit Trail
You should disable the audit trail for development environments only. If you disable the audit trail for production environments, you may not be able to be satisfy GxP quality guidelines and regulations.
As an Admin, you can enable or disable the optional Change Reason enabled in Audit Trail setting for an organization. By default, this setting is disabled.
The Audit Trail compliance setting must be enabled before you can access the Change Reason enabled in Audit Trail setting.
To provide evidence of how the Tetra Data Platform (TDP) is being used for a process governed by GLP guidelines, toggle the setting to enable adding change reasons to the audit trail.
This table shows the TDP entity and potential user actions that would require a change reason when done through the TDP UI as they make changes affecting scientific data for an organization's environment (eligible for change reason and tracking):
|TDP Entity||Applicable User Actions|
|File||Upload, Update Labels, Update Tags, Update Metadata, Update Metadata & Tags, Delete|
|Pipeline||Create, Update, Delete|
|Agent||Create, Update, Enable, Disable, Enable Queue, Disable Queue, Change Cloud Configuration, Change Local Configuration, Start Agent, Stop Agent, Add New, Add New Empower Project, Rerun Existing Empower Project, Select Existing Empower Project|
|Data Hub||Activate, Create, Update, Enable, Disable, Delete, Sync, Update Config|
|Data Hub Connector||Create, Update, Enable, Disable, Delete|
|Data Hub Agent||Create, Update, Delete, Enable, Disable|
|Hubs||Create, Update, Configure, Change Status, Sync|
|Pluggable Connector||Create, Update, Configure, Change Status, Sync|
|IoT Integration||Create, Update, Delete|
|IoT Source||Create, Update, Delete|
|Integration||Create, Update, Delete|
|Source||Create, Update, Delete, Enable, Disable, Enable Queue, Disable Queue|
For each of theses changes, after you click to save or submit, the following dialog will display asking you to enter and save the reason for the change (action):
The change reason you entered will be added to the log entry that is generated by any of the viewable, searchable, and exportable changes (previously listed in the table), and will display as an entry in the TDP Audit Trail.
Updated about 1 month ago