Guides
Get a document signed
Send a PDF for signature, let your bot chase down every signer, and walk away with a sealed copy and a Certificate of Completion.
Who this is for
You have a document — an NDA, a contract, an offer letter, a board resolution — and one or more people need to sign it. You don't want to explain a signing tool to anyone; you just want to hand your bot the file and the names, and get a signed copy back.
Before you start
- Sign enabled for your organization. If your bot says it can't send a document for signature, ask your admin to turn Sign on.
- The PDF ready to send — attached in chat, or already sitting in your files.
- Each signer's name, and their email if you have it. No email is fine too — your bot can give you a one-time link to hand over yourself (Slack, text, however you'd normally reach them).
Steps
Send it. Tell your bot who needs to sign: "Send this NDA to Anna and Erik for signature." If the order matters — say who should sign first: "Have Anna sign first, then Erik." If the document came from somewhere else in GATE (a file in Ledger), mention that too — the signed result lands back in Ledger automatically. A document drafted in Paper can be handed to Sign for sending, but the sealed copy lives in Sign.
Your bot confirms it's out. It tells you the request was sent and, for any signer whose email it has, that they've been emailed a link. For a signer with no email on file, it hands you a one-time link instead — copy that into whatever channel reaches them.
Each signer gets their own way in — no account needed. The usual path is an email with a one-click sign-in link (plus a 6-digit backup code, in case the link doesn't work for them). Opening it drops them straight into the document to review and draw or type their signature. If you set a signing order, whoever isn't up yet sees that it's not their turn — and gets their own nudge email the moment the person ahead of them finishes.
Check in any time. Ask your bot "Who's signed the NDA?" or "What's the status on the Acme contract?" — it reports each signer as pending, signed, or declined, and the overall state of the request.
Collect the sealed result. Once every signer is done, your bot seals the document on its own: every signature is stamped onto the file, and a Certificate of Completion page is appended — it lists every signer, how they proved who they were, when they signed, and a fingerprint of the original file so anyone can confirm nothing changed underneath it. Ask: "Send me the signed NDA" or "Is the Acme contract done yet?"
What you'll see
- In chat: the send confirmation, any one-time links you need to hand over yourself, status updates as signers finish, and the sealed PDF at the end.
- In your inbox: an invite email with the sign-in link + code for anyone waiting to sign, a "your turn" email once whoever was ahead of them finishes, and a final "it's signed" email once the document is sealed.
- In the dashboard, if your organization uses it: a Sign page listing every request and its status, with a detail view per request showing each signer's progress and a button to re-send any invite that went astray.
Troubleshooting
- A signer lost their link, or never got the email. Ask your bot to resend it — the old link stops working the moment the new one goes out, and a fresh invite email goes to the signer automatically if they have an address on file. A signer can also just check their inbox again and use the sign-in link there directly; it works independently of the one-time link your bot can hand out.
- A signer declined. That's final for this document — the request can no longer complete on its own. Ask your bot what happened, sort out whatever the objection was, then start a fresh request rather than trying to revive the declined one.
- The document needs to change after you sent it. Sign locks in the exact file it sent, so there's no way to swap the PDF underneath signers who already have a link. Have your bot cancel the request — "cancel the NDA signing request" — and send a corrected one. (A request where everyone has already finished signing can't be cancelled; it stays sealed as-is.)
- You asked for a stronger identity check (SMS code, BankID, eIDAS). Not available yet — your bot will refuse the request up front with a clear message rather than quietly signing people with a plain drawn or typed signature instead. Ask for the default (draw or type) for now.
- Everyone signed, but it still shows as unfinished. Rare, but sealing the final copy can occasionally hit a snag right after the last signature lands. Nothing is lost — say "everyone's signed the NDA but it looks stuck, can you check it?" and your bot can retry sealing without anyone signing again.