Signatures
Send documents for signature, place the fields, and keep the proof of who signed what and when.
Getting documents signed
The recipient gets a link, opens their documents in the browser and signs. Back comes a PDF with their signature, a protocol sheet and proof that nothing has been altered since.
Read itSetting up the send
The automation step that starts the request. You decide which templates get signed, where the result goes, who gets the mail and how long it is valid.
Read itThe proof: protocol sheet and chain
Every request keeps a chain of events: requested, opened, signed, delivered. Each entry carries the hash of the one before it, and the finished PDF gets a protocol sheet as its last page.
Read itThe signing page
The recipient taps the button in the mail and lands on a page with no sign-in. They see their documents, the marked spots and a button to finish.
Read itWhere on the document people sign
On the template you mark the spots the recipient should fill. The kind of element decides what they fill it with: a tick, some text, or their signature.
Read it