Audit trail
bb-sign records what happens to each envelope during signing: who opened the link, who signed, when and from which IP address. Every event is chained to the previous one, so any alteration of the record is detected. This gives you full traceability for every document.
Who: organization admins and platform admins. Where: the Audit Trail section of each envelope’s detail page.
Review an envelope’s trail
Section titled “Review an envelope’s trail”On the envelope detail, the Audit Trail section lists every event with its type, who caused it (the person’s email or “System”), the date and time, and its hash.
The Auditors, Contributors and Managers of the envelope’s workspace can review it, as can every admin. For a Viewer to review it, give them the Auditor role in Workspaces and members.
| Event | When it is recorded |
|---|---|
SIGNING_LINK_CLICKED |
A signer opened their signing link. |
SIGNING_VIEW_OPENED, SIGNING_VIEW_CLOSED |
A signer opened or closed the document view. |
SIGNER_ELIGIBLE |
In sequential signing, a signer’s turn came. |
SIGNER_SIGNED |
A signer signed; their IP address is recorded. |
ENVELOPE_COMPLETED |
The last signer signed. |
SIGNED_COPY_ACCESSED |
The signed copy was downloaded from the signer’s link. |
EMAIL_SENT, EMAIL_DELIVERED, EMAIL_OPENED, EMAIL_BOUNCED |
An envelope email was sent, delivered, opened or bounced. |
The envelope’s overall status (created, sent, cancelled or expired) is shown on the envelope itself and reaches your systems through webhooks.
Organization configuration changes
Section titled “Organization configuration changes”bb-sign also records the configuration changes that affect access to your organization:
- Creating and revoking API credentials.
- Creating a webhook, rotating its secret and deleting it.
- Creating, renaming and deleting workspaces.
- Granting and removing workspace roles for people and API keys.
These events belong to your organization. To obtain them, request them from Binary Bridges support.
How the record is protected
Section titled “How the record is protected”Every event carries a SHA-256 hash computed over its content and over the hash of the previous event of the same envelope. Modifying, inserting or deleting an event therefore breaks the chain from that point on and makes the alteration evident. The organization’s configuration events also carry their own hash.
If you need to present an envelope’s evidence to a third party, request it from Binary Bridges support.