**Source URL:** https://general.veevavault.dev/medical/vault-sdk/references/audit.md

# Vault Audit Logs



From the **Admin > Logs** area in Vault, you can view a history of actions within your Vault, including actions performed with the Vault Java SDK. You can learn more about the [Vault Admin Logs in Vault Help](https://platform.veevavault.help/en/gr/14341).

<Aside type="note" title="Note">Audit logs support a precision to one second. Events occurring within
a single second may appear in an unexpected order.

</Aside>
# System Audit History {#System_Audit_History}

The **System Audit History** page displays Vault-level configuration and settings changes, which includes managing Vault extensions. For example, uploading a new trigger to your Vault.

<ThemeImage srcLight="/images/sdk/sdk_system_audit.png" srcDark="/images/sdk/sdk_system_audit.png" alt="System Audit History in Vault."></ThemeImage>
# Object Record Audit History {#Object_Record_Audit_History}

Records affected by triggers indirectly through the use of the `RecordService` have an audit entry identifying the change with *System on behalf of* the user initiating the request. This allows an Admin to audit changes which may not have been directly manipulated by users, but rather by code in triggers. When a user delegates access to another user, the audit will show *Java SDK Service Account on behalf of* the delegating user.

In addition, when a workflow starts indirectly by code, the audit log will also indicate *Java SDK Service Account on behalf of* the user initiating a request. This is important because a user may create a new record that fires a trigger to start a workflow. In this case, the end user did not start a workflow, they created a new record. The audit log would then indicate that the Java SDK Service Account started the workflow on the user's behalf.

# Document Audit History {#Document_Audit_History}

The **Document Audit History** page displays document-related events, including events triggered through the Vault Java SDK. Documents affected by Vault extensions through the use of `DocumentService` have audit entries identifying the change with *Java SDK Service Account on behalf of* the user initiating the request. When a user delegates access to another user, the audit will show *Java SDK Service Account on behalf of* the delegating user.



---

**Previous:** [Vault Permissions](/medical/vault-sdk/references/vault-permissions)  
**Next:** [Sample Code](/medical/vault-sdk/references/sample-code)