Skip to main content
Opening a package’s signing link (/sign/[token]) takes a recipient through any required gates, then into the signing experience itself.

Video guide: Signing a document

The signing link's consent gate, asking the recipient to agree to sign electronicallyThe signing link's consent gate, asking the recipient to agree to sign electronically

The consent gate, one of the steps a recipient can meet before their documents.

Gates

Depending on how the package or template was configured, a recipient may see one or more of these before reaching their documents:
  • Password required, if the sender protected the package with an access code. The recipient enters it and selects Continue. Too many wrong attempts lock the link for 15 minutes.
  • A consent screen, asking the recipient to tick “I agree to use electronic records and signatures”, along with Flowsign’s Terms of Use and Privacy Policy, then select Continue. The screen links to the Electronic Records and Signatures Disclosure. Other Options offers Decline and Session information.
  • Workflow questions, if the sender’s workflow asks this recipient something before signing starts. After the consent screen, a step titled “A few questions before you sign” explains “Your answers decide which documents are part of this package.” It shows one question at a time, each needing an answer, with Back and Next to move between them and Continue on the last. An answer can lead to further questions before the documents open.
The consent screen with the Other Options menu open, showing Decline and Session informationThe consent screen with the Other Options menu open, showing Decline and Session information

Other Options on the consent screen offers Decline and Session information.

The Session information dialog showing the envelope ID, recipient ID and signing version, with Close and Copy to clipboard buttonsThe Session information dialog showing the envelope ID, recipient ID and signing version, with Close and Copy to clipboard buttons

Session information lists the IDs to share with support.

Instead of any of the above, the recipient may see one of these:

Signing

Once past the gates, the recipient sees their assigned documents with their fields highlighted. A counter above the page shows how many required fields are done, for example 2/5 fields required, and changes to Ready to finish once they all are. A tab row switches between documents when there’s more than one. Text the sender printed on the page from a template’s merge fields shows too, but it isn’t a field to fill and doesn’t count towards the total. When a package is signed in order, a later signer also sees what earlier signers filled in, printed on the page read only. Those aren’t fields to complete and don’t count towards the total. Some fields appear, disappear or become required after the recipient answers a question on the page, for example ticking a checkbox, picking a radio option or choosing an option from a dropdown. The required count updates as these fields change, and fields that stay hidden are never required. If a field hides again after the recipient fills it in, what they entered isn’t kept.
  • The tools rail on the left holds Your tasks (the list of fields to fill, with Next to jump to the next open one), Search in document and Download, which saves a blank copy without signatures for printing. Get help, Session information and Take the tour sit at the bottom of it.
  • The Pages rail on the right shows page thumbnails for jumping around the document.
  • On a phone, the bottom bar opens Tasks, a tab on the edge of the screen slides the pages in, and the More options menu holds Search in document, Download, Decline to sign, Get help, Session information and Take the tour.
A tab beside the first field reads Click to start. Selecting it jumps to that field. After that it reads Next, or Sign when the last required field left is a signature or initials.
The signing screen showing document tabs, the required-field count, a signature field reading Click to sign and a date field, with Decline and Finish Signing in the headerThe signing screen showing document tabs, the required-field count, a signature field reading Click to sign and a date field, with Decline and Finish Signing in the header

The signing screen, with the recipient's fields highlighted and the Click to start tab beside the first one.

The signing walkthrough card titled Begin with Click to start, with Skip and Next buttonsThe signing walkthrough card titled Begin with Click to start, with Skip and Next buttons

The first-visit walkthrough explains the Click to start tab that jumps between fields.

The first signature or initials field opens Adopt your signature (or Adopt your initials). The recipient confirms their name and initials under Your details, then picks how to make the mark under Choose a signature style:
  • Type: their typed name in a choice of signature styles.
  • Draw: draw the mark on the Sign here line with a mouse, trackpad or finger. Clear starts again, and when both a signature and initials are needed, Approve moves on to the other one.
  • Upload: a PNG or JPEG image under 5 MB.
Preview shows the mark as it will be stamped, and reads Looks good once everything needed is there. A recipient who is signed in to Flowsign with a saved signature sees it as soon as they open the package: a notice reads “Your saved signature is ready to use.” Use it opens Adopt your signature with the saved mark ready on Upload. If the saved signature can’t be loaded, the notice says so and they adopt one as usual.
The Adopt your signature dialog with the full name filled in, the Type, Draw and Upload options, a preview of the signature and an Adopt and sign buttonThe Adopt your signature dialog with the full name filled in, the Type, Draw and Upload options, a preview of the signature and an Adopt and sign button

Adopt your signature, with Type selected.

Adopt and sign applies the mark, and later signature fields reuse it. To swap it, use Change adopted signature at the bottom of the tools rail (in the More options menu on a phone). Some documents require an acknowledgement. The recipient reads it and selects I Acknowledge before they can finish. Finish Signing completes the session once every required field is filled. If something is still missing, selecting it jumps to the first open field instead. Get help, at the bottom of the tools rail (in the More options menu on a phone), shows who sent the document and how to contact the sender or the Flowsign team. Take the tour beside it walks you through the page.

Declining

A recipient can decline instead of signing, using Decline in the header (or Decline to sign in the More options menu on a phone). The Decline to Sign dialog reads “Pick a reason so the sender knows how to follow up. This can’t be undone.”
  1. Pick a Reason: “This document was not intended for me”, “I don’t agree with the terms”, “The document contains errors or needs changes”, “I did not authorise this request” or “Other”.
  2. Add a note for the sender. It’s optional for most reasons, but required for “The document contains errors or needs changes” and “Other” (up to 500 characters).
  3. Select Confirm Decline.
The Decline to Sign dialog with a reason picker, an optional note and a Confirm Decline buttonThe Decline to Sign dialog with a reason picker, an optional note and a Confirm Decline button

The Decline to Sign dialog, before a reason is picked.

Declining cannot be undone. The recipient sees a confirmation that the sender has been notified, along with the Reason shared with the sender.

Completion

After finishing, a completion screen confirms the document has been signed and that the sender has been notified. It lists who signed, who sent it and how many documents it includes. What happens next explains that once everyone has finished, the recipient is emailed a copy of the completed documents and the certificate of completion, with a link to contact the sender.