Sliick Docs v2.4: Proof That Travels With the Document

Sliick Docs v2.3 was about polish and control: branded signing emails, a redesigned template editor, and more say over how a signature request behaves. v2.4 is about what a signed document can prove once it has left your organisation.

This article gives a high-level overview of what has changed since v2.3. For the step-by-step reference, see the Sliick Docs Complete User Guide.

Anyone can verify a signed document

This is the headline change in v2.4.

Every completed envelope produces a signed PDF and a public verification page. A counterparty who receives the signed document drops the file onto that page, or pastes its fingerprint, and gets a confirmation straight from your system.

The page now works for anyone: no login, no Salesforce account, no record access. What it shows is a purpose-built public summary and nothing more:

• the envelope name and the document name
• the date the envelope completed
• a masked summary of who signed
• confirmation that the audit trail behind the document is intact

No private signing detail is exposed. Verification remains available to whoever holds the signed file, and to nobody else.

If you host the verification page yourself, its route now ships with the reference signing site, so provisioning it is one less manual step. If you have already placed the verifier on a public page of your own, nothing needs to change.

A logo library for signing emails

v2.3 introduced branded signing emails: your organisation’s logo, your accent colour, and your personal message on every invitation, reminder, cancellation, and completion. v2.4 builds out how you supply and manage that logo, and makes it render in mainstream mail clients including Gmail and Outlook.

• Two sources. Upload an image file, or paste the address of a logo you already host on your own site or CDN.
• A logo library. Every logo you upload is kept. Switch back to an earlier one without re-uploading it, and delete the ones you no longer want. The logo currently in use is protected from deletion.
• Sent emails keep their logo. Changing your branding today does not reach backwards and alter a signing email a counterparty received last month.

Uploading a file depends on a Salesforce setting your administrator controls. Where it is not switched on, Sliick Docs names the exact screen to enable it and offers the paste-an-address option in the meantime.

The Certificate of Completion records more

The Certificate of Completion is the document you keep, and in v2.4 it carries a fuller and more durable account of what happened:

• The sender and the complete signing history appear on every envelope, including those signed by parties outside your org.
• The signer’s location is captured on signing sites built with Salesforce’s newer site technology.
• The exact consent wording that signer accepted is captured at the moment they accept it, so editing your consent text later leaves every earlier certificate intact and self-consistent.
• One typeface throughout.

One related signing improvement: on a document carrying both a signature box and an initials box, adopting your signature now applies only to signature boxes, and initials are captured separately.

Consent wording that fits the signer

The consent a signer accepts now describes the flow they are actually looking at: a tick box and a signature pad.

Signers in the United States and Australia continue to see the statute-specific wording that applies to them. Signers elsewhere now see a generic disclosure referring to applicable law, rather than a disclosure citing legislation from another jurisdiction.

Upgrading

Sliick Docs v2.4 is live on the AppExchange. New installs get v2.4 directly.

• Everything from v2.3 carries forward unchanged. Your templates, bundles, batches, branding, and settings continue to work exactly as before.
• The verification, certificate, and consent changes apply automatically. There is nothing to configure.
• If you already use an email logo, re-upload it once so it is served the new way and renders in Gmail and Outlook. Your other branding settings are untouched.

Where to start

• Sliick Docs Complete User Guide - the full reference.
• E-Signature in Sliick Docs: The Story, the Law, and the Tick - the background on evidence and certificates.
• Sliick Docs product page - feature overview and AppExchange install link.

If you would like a hand setting up the public verification page for your organisation, get in touch.