Request and track signatures
A signing submission is a request for electronic signatures on one document prepared for particular people. It records the template version, the associated records, the recipients and the progress of that request.
Use a stored-document upload when you already have a file to keep. Use a signing submission when you need the signing workflow.
Start from the related record
Section titled “Start from the related record”Open the relevant staff member, site or other supported record. In Documents, open the additional actions and choose Create signing submission.
Choose an available template. The available choices depend on the kind of record you started from and your access.
Check the document and recipients
Section titled “Check the document and recipients”Complete the associated records and the information requested by the template. Review the title, notes and any values you need to enter.
Some recipients come from the linked records. Other templates ask you to enter an external signer’s name and email. Check each recipient carefully before continuing.
Choose Next to generate the preview. Resolve any missing required values shown by the portal.
Review before sending
Section titled “Review before sending”Read the prepared document, including the names, dates and fields to be completed or signed. Review the invitation preview when one is provided.
Choose Send when the document and recipients are correct. This starts the signing process. If something needs correcting, return to the form, update it and choose Next to review a new preview before sending.
Follow the request
Section titled “Follow the request”Open Documents → Signing Submissions and find the request. Its details show the overall status and the recipients’ progress, including available sent, opened or completion information.
Use the displayed status to distinguish a request that is still in progress from one that has completed or failed. If there is a failure reason, read it before deciding what to do next.
When completion artifacts are available, the details offer downloads such as the signed document and signing audit log. Their availability depends on the submission’s state.
Keep the history understandable
Section titled “Keep the history understandable”The submission retains its template version and record associations so you can understand what was prepared and for whom.
Archive controls manage whether a submission appears in active lists. Archiving should not be treated as cancelling a recipient’s signing process; use only the actions actually offered for the request.