AuraDoc
Sign inSign up

Blog

Audit trails: who did what, and when

See the privacy trail, invitation history, signature audit trail and agent run steps in AuraDoc, and learn who can open each one and what it records.


When several people work on the same documents, sooner or later someone asks who changed a setting, who invited a colleague, or what exactly happened before a contract was signed. AuraDoc keeps records for these questions in several places, each one tied to a specific kind of activity. This article walks through the trails that exist today, what each one records and who is allowed to read it, so you know where to look and what to expect.

The privacy trail for your workspace

The privacy area keeps a trail of privacy-related events for your workspace. Each entry shows the type of event, the user who triggered it when there is one, extra details about what happened and the time it was recorded. The list is paginated, newest first, and you can narrow it by event type, by a start and end date, or by a free-text search across the event type, the user and the details. Only your own workspace is ever shown, never anyone else’s.

Invitation history

Inviting people is a sensitive action, so it leaves its own record. The invitation audit lists recent invitation activity for the workspace, which helps when you need to confirm who was invited, when, and what happened to the invitation afterwards. Both this list and the privacy trail are meant for people who manage users, so ordinary members do not see them. To understand who gets that permission, read team roles and permissions.

The audit trail of a signature

Every signature request keeps its own trail, stored with the request itself. It lists each signer with their name, e-mail, order and role, together with their status and the moments they verified their one-time code, signed or declined. It also records the network address and browser reported for each signer, and a list of events in the order they happened. Alongside it you find a hash of the trail and hashes of the original and the sealed file, so the record can be checked against the documents. The full flow is described in electronic signatures with OTP, and verifying a signed PDF shows how to confirm a finished file.

Step-by-step records of agent runs

When an agent works through a task for you, its run is recorded step by step. The audit of a run lists the events in order, and shows which documents the run used as its source, with their names. That makes it possible to review how an answer was reached instead of only seeing the final text. It is available to people who can use the chat, and only for runs that belong to your own workspace.

Who sees what, and why it matters

These trails share a few principles. They are scoped to your workspace, so one customer never sees another’s records. Access follows roles: the trails about people and privacy are for those who manage users, while a signature trail is available to the workspace that owns the request. And they record facts about activity, not the content of your documents.

Together they support routine questions such as who invited a colleague last week, which event type appears most often, or in what order a document was signed. For the bigger picture of how privacy is handled across the product, read privacy and compliance built in, and see the privacy page for the commitments we publish.

Getting the most from the trails

A few habits make these records more useful. Check the privacy trail after you change roles or settings, so you confirm the change was recorded as you expected. Use the date filter to focus on a specific incident rather than scrolling through everything. Keep the signature trail together with the sealed file when you archive a contract, since the hashes tie them together.

Remember that each trail answers a specific question. If you cannot find an event in one place, think about which kind of activity it was and look in the matching trail instead. If a record you need is missing, tell us, so we can improve the coverage.

Back to the blog