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).