Multi-step signing

Sometimes the signing procedure needs to change according to the current situation. In this case, the signing of the document is divided into several steps.

For example, you do not know in advance who will sign for the supplier. So you create a document where representatives of your party will sign, but you choose not to lock the document. Once it is clear who will be signing on the other side, you download the document, create a new signature script, and send it to the supplier.

1. The document is passed to the 1st signer to sign first, then the document with one signature is passed to the 2nd signer to sign, etc. When the first signatories sign, the document must not be closed against changes so that subsequent signatures can be inserted. The content of the document remains unchanged.

2. Only when the last signatory signs the document is closed against changes.

• Jak v Signi podepisovat na více kroků?
• Jak se to projeví v dokumentech?
• Co se stane, když se pokusíte přidat podpis na již uzamčený dokument?
• Lze něco takového zrealizovat i z integrované aplikace?

How to sign on multiple steps in Signi?

1. When entering a signing scenario for the first signer, do NOT check Lock document in the signature scenario entry.

2. When entering a signature scenario for the last signer, they MUST check Lock Document in the signature scenario entry.

Should the document be locked against further changes after all signatories have signed? The default is yes.

How will this be reflected in the documents?

You can see how the document is changed in a multi-step signing process, for example in Adobe Reader.

In the first steps of signing a document, it is not visible e.g. in Adobe Reader that the document is locked against further changes.	In the final document in Adobe Reader, for example, you can see that the document is locked against further changes in addition to everyone's signatures.

What happens if you try to add a signature to an already locked document?

If you upload a document to Signi that is already locked against changes, Signi will return an error. If someone has sent you such a file, you need to ask them to re-save it WITHOUT locking it against changes. These are not changes to the content of the document, but changes to related information such as signatures, seals and timestamps. 

The actual content of the document remains unchanged throughout the signing process.

If you upload a document to Signi that is already locked against changes, Signi will return an error.

Can something like this be implemented from an integrated application?

Yes, you can, see Advanced Signi API call examples.