Docs (Basic): View History/Audit Trail

Audit Trail allows you to check everything that has taken place with a document. The log shows you the entire history sorted chronologically by the most recent event of when someone:

  • Uploaded a document
  • Renamed a document
  • Viewed a document
  • Downloaded a document
  • Deleted a document
  • Restored a document
  • Signed a document (if a team member added the My signature field, their name shows up as the signer)
  • Signed a document with KBA/QES/AdES
  • Declined to sign a document
  • Failed to sign with KBA
  • Reset KBA
  • Sent a signature request
  • Resent a signature request
  • Voided a signature
  • Canceled a signature request
  • Sealed a document
  • Unsealed a document
  • Approved a document
  • Resent a document approval
  • Disapproved a document
  • Moved a document to another top-level folder
  • Moved a document to another client account
  • Modified a PDF document (for more details on reviewing changes made to a PDF, go here)
  • Transferred a document to DATEV

To view a document’s history, click the three dots to the far right of the document’s name, then click Audit trail.

You can also get to  Audit Trail from the document viewer.

On the Audit trail page, you’ll find this information about a document’s history:

  • Account name: the first and last name of the account user or the name of their business.   
  • User: the first name, last name, and email address of one of the users who opened the document. If the document was signed by your client who doesn't use the client portal, this field will contain information that they opened it via a secure link.
  • Event: an event that took place with the document. In some instances, the document’s updated size or name.
  • Server time: the UTC time when the event occurred.
  • Client time: the time in the user’s location when the event occurred. The difference between UTC and the user’s location time is also displayed.
  • IP address: the IP address of the user who accessed the file, as well as the city and country they are located in
  • Browser: the browser used when the event took place
  • OS: the operating system of the user who made changes

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.