Launchboard’s e-signature workflow lets you collect legally binding signatures on documents stored in your Dataroom. Signers receive an email with a signing link — no Launchboard account required — and you can track each signer’s progress in real time from the Inspector panel. Once all signers complete, the signed PDF is stored as an immutable version and a cryptographic seal hash is computed as permanent proof.Documentation Index
Fetch the complete documentation index at: https://docs.launchboard.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Requesting signatures
Open the document in the Dataroom
Navigate to Dataroom and click on the document you want to send for signatures. The document must have a status of
REVIEWED or later.Click Request Signatures
In the Inspector panel or the document toolbar, click Request Signatures. A dialog opens where you configure the signature request.
Add signers
Enter the name and email address of each person who needs to sign. You can add multiple signers — each will receive a separate signing link.
Configure signature fields
Position signature fields and any other fields (date, initials) on the document. Each field is assigned to a specific signer.
The signing experience
Signers receive an email with a link to a Launchboard signing page (/sign/...). They can open the document, review it, and apply their signature — no Launchboard account is required to sign. Once a signer completes their signature, their status updates in the Inspector immediately.
If a signer needs to return to a partially completed document, you can click Resume signing in the Inspector to send them a new link, or use Copy signing link to share it directly.
Signature status tracking
| Status | Meaning |
|---|---|
PENDING_SIGNATURE | Request sent — no one has signed yet |
PARTIALLY_SIGNED | One or more signers have completed, others have not |
SIGNED | All signers have completed the document |
What happens on completion
When the last signer completes the document:- The fully signed PDF is downloaded and stored as a new immutable version in the Dataroom.
- A seal hash is computed from the signed PDF and stored alongside the version record.
- The original unsigned version remains intact — no existing versions are overwritten.
- The document status moves to
SIGNED.
Seal hash
The seal hash is the cryptographic proof that a specific version of a document was signed. It is a SHA hash computed from the signed PDF at the moment of completion. If the document is altered in any way after signing, the hash will not match — making tampering detectable.
- Open the document in the Dataroom.
- In the Inspector panel, scroll to the Signatures section.
- The seal hash is displayed in a truncated format. Click the copy icon to copy the full hash to your clipboard.
Status and event mapping
Launchboard listens for events from the e-signature provider and maps them to document statuses automatically:| Provider signal | Document status |
|---|---|
document.sent, document.pending, envelope.sent | PENDING_SIGNATURE |
recipient.signed, recipient.completed (partial progress) | PARTIALLY_SIGNED |
document.completed, envelope.completed (all signers done) | SIGNED |
document.cancelled, document.rejected, envelope.cancelled | REVIEWED |
Reconciliation
Launchboard uses webhooks to receive signature updates in real time. If a webhook is missed or delayed, the status in the Inspector may be temporarily out of date. To pull the latest status manually, click Sync now in the Inspector’s Signatures section. Launchboard will fetch the current state from the signing provider and update the document status.Cancelling a signature request
To cancel an in-progress signature request, open the Inspector and click Cancel request in the Signatures section. The signature request is cancelled and the document returns toREVIEWED status. If some signers had already completed before the cancellation, those signatures are voided.