Routes
/board/sign/[token]/board/sign/[token]/verify/board/sign/[token]/sign/board/sign/[token]/doneFlow 5
Signer Flow
A recipient opens a protected link, verifies access if needed, fills assigned fields, signs, and the sender sees progress.
4
Routes
5
Buttons
2
Screenshots
3
Watch-outs
ELI10
A recipient opens a protected link, verifies access if needed, fills assigned fields, signs, and the sender sees progress.
W5
Who: the recipient/signer.
What: protected link, verification, assigned fields, submit, completion.
When: after the sender clicks Send now.
Where: signer token routes.
Why: signing must be simple for the recipient and auditable for the sender.
Flow graph
Screens and paths in this flow
Each step connects to its screen manual. Follow the nodes left-to-right to trace the document journey.
4nodes
Step 1Signer LinkRecipient opens the protected signing link.
Step 2VerifyRecipient verifies PIN or email before signing.
Signer Flow4 routes · 5 actions
Signer Link→Verify→Sign→Done
Important buttons
Watch-outs
If a link is public, the sender needs an explicit warning.
If a link is protected, the invite email must include the PIN or clear instructions.
Sender status must update: sent, opened, fields completed, signed.