> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/s-sign/automation-and-envelope-lifecycle/overview-the-s-sign-audit-trail.md).

# Overview: The S-Sign Audit Trail

The S-Sign Audit Trail is a comprehensive digital record that archives the when, where, and by whom of an e-signature request. I

***

### 🔍 Key Components of the Audit Trail

The audit trail is divided into five primary sections to ensure legal defensibility and transparency.

#### 1. Unique Document Identifier

* SHA-256 Hash: A unique digital fingerprint is generated for every signed document.
* Authenticity: If the document is altered after signing, a newly generated hash will not match this string, proving the document has been tampered with.

#### 2. Request Metadata

* Signature Requested By: Displays the name and email of the Salesforce user who initiated the request.
* Domain Tracking: Lists the Salesforce domain where the request originated and the S-Sign Site URL where it was signed.

#### 3. Signer Information

Each signer’s profile is detailed with:

* Name & Email: As defined in the signer profile or entered during signing.
* Signer Position: The numerical order in which they signed.
* IP Address: The network location from which the document was submitted.
* Timestamp: Exact date and time of completion (Time zone is configurable).

***

### 📜 Audit Event Tracking

This section provides a granular timeline of every interaction with the document.

| **Event Type** | **Description / Trigger**                                         |
| -------------- | ----------------------------------------------------------------- |
| Create         | Request is initialized in Salesforce or final document is stored. |
| Email          | Link is sent to a signer or a confirmation email is dispatched.   |
| Verification   | PIN codes (2FA) sent/entered or "Consent to do business" checked. |
| View           | Signer opens the document link.                                   |
| Save           | Signer saves progress to finish later (if enabled).               |
| Submit         | Signer completes their portion of the document.                   |
| Completed      | The entire request is finalized by all parties.                   |

***

### ⚙️ Customization & Behavior

Administrators can modify how the Audit Trail behaves through the S-Sign Template Settings:

* Time Zone Management: Change the time zone displayed on the audit record to match your local business requirements.
* Custom File Naming: Use merge fields to automatically name the final "Signed Document with Audit Trail" PDF.
* Progressive Visibility: Enable "Show audit trail during signing process" so that subsequent signers (e.g., Signer 2) can see the audit data for previous signers (e.g., Signer 1) before they sign.
* Access Control: Optionally prevent specific signer profiles from receiving the audit record in their confirmation emails (though keeping this enabled is recommended for transparency).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/s-sign/automation-and-envelope-lifecycle/overview-the-s-sign-audit-trail.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.