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.

Four steps, and only the second costs anyone time

An automation requests the signature. The recipient gets the mail and signs. The application stamps the PDF, appends the protocol sheet and files it in the target field on the record. After that it goes to the recipient as an attachment, so they can keep it.

One request, several documents, all or nothing

A request may carry several documents, a contract and a consent form for instance. Whoever signs, signs all of them. There is no partial completion, and that is not a limitation but the point: two half-signed records would be two cases for someone to clear up.

What this is and what it is not

A simple electronic signature under Article 25 eIDAS. Its evidentiary weight comes from the protocol and not from a certificate. There is no qualified signature, no identity check and no trust service provider. Whoever has the link can sign; that is covered by the short validity, sending only to the address on the record, and the logging.

Without the module the element kind does not exist

At its core the module contributes one thing: the Signature element kind in the template editor. Stamping uses the same function that produces a quote. If the module is not booked, the element kind is not forbidden, it is not on offer at all.

Step by step

1. Create a document template and place a Signature element on it.
2. Create a file field for the signed PDF to land in.
3. Set up the step Request signature in an automation.
4. Play it through with a test record and look at the history.

Is this legally watertight?

It is a simple electronic signature. Whether that suffices for your purpose depends on your business and is a legal question we do not answer. What the application delivers is a protocol with time, origin and a chain that makes any later change visible.

Could someone else use the link?

Technically yes, which is inherent to a simple signature. The request therefore goes only to the address on the record, the link expires, and every step is logged with time and origin.

Is the signature stored and reused?

No. The image exists only in the finished PDF and is not kept as an image of its own. A stored signature that can be applied again would be a different legal position and a different risk.

Can several people sign one after another?

No. A request has one recipient. A chain of several signers is a subject of its own and is not built.

What happens if nobody signs?

After the deadline the request is closed and the trigger Signature expired fires. What happens then is up to your automation.