Consent and sender wording

Two pieces of wording are yours to override on the Sliick Docs Settings page: the signer consent a signer accepts before signing, and the sender warning an admin acknowledges when turning e-signature on for a template. This is the page to read if your organisation needs its own jurisdiction’s statutes named.

How the override works

• Leave a box blank and the packaged wording is used, word for word. A blank body never produces an empty disclosure, so there is no way to accidentally send a signer nothing.
• Write your own and it prints as yours. The Certificate of Completion shows your organisation’s own version of the wording, and it does not cite the statutes the packaged text cites, because your wording is yours to stand behind.
• The editor offers machine-translated starting points in ten languages. Pick a language and the draft is pre-filled for you to review, edit and save. Nothing reaches a signer until you save, so the translations are a drafting aid rather than a live setting. One caveat is printed on the card itself: a signing site serves one wording to every signer on it, whatever language each of them reads, so choose the language your signers read.
• The wording box is tall enough to read a whole disclosure without dragging it open, and can still be dragged taller.

What the packaged consent says

There is one signer consent and one sender warning, used for every signer everywhere, rather than a different body per country. It records the signer’s intent to sign electronically; it does not assert that the resulting signature is legally binding, because that is not universally true.

Some document types, countries and industries require a higher form of signature, a witness, notarisation, or wet ink. The wording tells any signer who believes their document is one of those not to sign it, and to ask the sender instead.

When a change takes effect

Each signer’s consent wording is frozen at the moment they are invited. Editing the text later never changes what an already-issued certificate reprints. See Verification and certificates.

The sender warning behaves the same way: the acknowledgment is snapshotted onto every request sent from the template, and updating the warning text asks admins to re-acknowledge templates that were acknowledged against the older version. See One-time org setup.