Resources & knowledge base
Guides to signing, sealing and verifying
Short, plain explanations of how electronic agreements work and how to get the most from AccordSeal. No sign-up needed to read them.
What makes an electronic signature provable?
A signature image proves very little. What matters is the evidence around it: who acted, on which text, when, and whether anything changed afterwards.
EvidencePAdES seals and RFC 3161 timestamps, explained plainly
What PAdES seals, RFC 3161 timestamps and AATL certificates are, what each one proves about a signed PDF, and how AccordSeal uses each one.
How-toHow to verify an AccordSeal document
Three ways to check that a signed PDF is genuine and unchanged: by verification code, by SHA-256 hash, or by uploading the file. No account needed.
WorkflowSequential or parallel signing: which order should you use?
When to send an agreement to signers one after another, when to send it to everyone at once, and how to combine the two without slowing things down.
How-toBulk send from a CSV: a preparation checklist
How to prepare a template and a spreadsheet so that a bulk send of hundreds of agreements goes out cleanly the first time.
AdministrationRolling out single sign-on and SCIM: a checklist
The order to do things in when you connect AccordSeal to your identity provider, so that nobody is locked out and leavers lose access immediately.
DevelopersIntegrating AccordSeal: an overview for developers
How the pieces of the developer platform fit together: keys or OAuth, creating an agreement, embedded signing, webhooks, and testing in the sandbox.
Run your next agreement from draft to proof.
Start with the Free plan, or ask us to walk your team through AccordSeal with your own documents.