Demo: eSignatures with Audit Trail
18-minute demo of the eSignature flow — request, recipient experience, signed PDF, audit certificate, what holds up in court.
Demo: eSignatures with Audit Trail
Recorded 12 February 2026 · 18 minutes · Hosted by Achieng Otieno (Solutions Engineer)
[Embed placeholder — video opens on the webinars portal]
What you'll see
A complete eSignature lifecycle:
- Sender selects a contract document in Papyrus, clicks Request Signature
- Adds two recipients (one internal, one external)
- Places signature fields, sets parallel signing order
- Recipient #1 (external) opens email → secure link → reviews document → signs (drawn signature)
- Recipient #2 (internal) approves via in-app workflow task → signs (passkey-verified)
- Final signed PDF includes both signatures + audit certificate as the last page
- Audit log shows the full chain: timestamps, IPs, devices, methods
Transcript highlights
"Look at the certificate page. It shows the document hash at the moment of signing. If anyone modifies the PDF later, the hash won't match — that's the tamper-evidence."
"This is a Tier-2 eSignature — fine for routine commercial contracts in Kenya. For deeds or high-value contracts, we'd add a PKI certificate from a recognised CA. That's a 30-second config change."
Legal context
The webinar includes a 4-minute segment on Kenya's KICA framework and when each tier of eSignature is appropriate. See the linked guide for the full treatment.