Overview
LinkSquares Sign can confirm that the person signing an agreement is the person you sent it to. When verification is on, each signer verifies their email address with a one-time access code, or by signing in to LinkSquares, before they can view or sign. You can also stop signers from reassigning their signature to someone else.
Key Benefits:
- A forwarded email can't produce a signature: the access code goes only to the address on the Signature Request, so anyone else who opens the link can't view or sign.
- Signing authority stays where you put it: with reassignment off, signers can't hand the agreement to someone else to sign.
- Stronger evidence if a signature is challenged: each signer's email verification is recorded in the agreement's Activity tab and in the Signature History PDF.
- No accounts or passwords for counterparties: external signers verify with a code sent to their own inbox.
- Company defaults with per-request control: Finalize Admins set the defaults once, and senders can adjust them for an individual Signature Request.
Accessing Signer Verification and Reassignment Settings
Prerequisites
- Your company uses LinkSquares Sign to send Signature Requests.
- To change the company defaults, you must be a Finalize Admin. On the Agentic Platform, your Customer Success Manager configures the defaults.
- To change the settings on an individual Signature Request, you need permission to send agreements for signature. See Overview: Finalize Settings for who can send Signature Requests.
Setting the Company Defaults
- Click the products menu (the grid icon next to FINALIZE) and select SETTINGS.
- Select Finalize App, then select the SIGNATURE REQUESTS tab.
- Scroll to the signer verification settings, below Allow auto-send for signature.
- Toggle Require access code to sign by default on or off.
- Toggle Allow signers to reassign by default on or off.
- Your changes are saved automatically.
These defaults apply to every new Signature Request your company sends, including bulk sends, Signature Requests sent with Auto-Send for Signature, and requests sent by LinkSquares agents.
Using Signer Verification and Reassignment Settings
Set Verification on an Individual Signature Request
When you build a Signature Request, the company defaults are already filled in. You can change them for that request before you send it.
- Open the agreement and start a Signature Request as usual. See Quick Start - Sign: Sending Agreements to Signature from Finalize.
- In the Signature Request builder, find the Require access code to sign and Allow signers to reassign switches.
- Toggle either switch to change it for this request only. Your choice is saved with the request, including when you save it as a draft and reopen it.
- When Require access code to sign is on, a lock icon appears next to each signer. Recipients who only receive a copy of the executed agreement don't need to verify.
- Send the Signature Request.
- Note: Bulk Signature Requests and Signature Requests sent with Auto-Send for Signature don't show these switches. They always use your company defaults. See LS Sign: Auto-Send for Signature.
What an external signer sees
Signers outside your organization verify with a one-time access code.
- The signer receives the signing email. When an access code is required, the email says so, names the address the code will go to, and asks the signer not to share it.
- The signer clicks REVIEW DOCUMENT. Instead of the agreement, they see the Verify your identity screen, which shows the email address the code will go to, partly hidden.
- The signer clicks SEND ACCESS CODE. LinkSquares Sign emails a 6-digit code to the signer's address on the Signature Request. The code is never sent to anyone else, even if the signing email was forwarded.
- On the Enter your access code screen, the signer types the code and clicks VERIFY. A countdown on the screen shows how long until the code expires.
- If the code doesn't arrive, they click Resend code. A new code can be requested every 60 seconds.
- Once verified, the signer sees a confirmation that their identity was verified, then clicks BEGIN SIGNING to sign as usual.
- Each code must be entered within 10 minutes of being sent. Requesting a new code cancels the previous unused one.
- Each code allows three incorrect attempts, and the error after each miss shows how many are left.
- After the third miss, the code is cancelled and the link is locked for 15 minutes, in any browser.
- The Too many attempts screen says signing is paused and counts down from 15:00. When the lock ends, the signer can request a new code.
- Signers wait 60 seconds between code requests and can request up to five codes per hour from the same browser. After the fifth, the screen shows how long they need to wait before requesting another.
- If a signing link reaches 20 incorrect attempts in total, or 20 codes requested in 24 hours, the link locks until the sender resends the Signature Request. The resend creates a new link with fresh limits, and an entry in the agreement's Activity tab shows why the link is locked. Normal use won't reach these limits.
- A signing session ends after 30 minutes of inactivity. Each action the signer takes restarts the timer. When the session ends, the page shows the Your session has expired screen, either on its own or as soon as the signer clicks a button such as BEGIN SIGNING.
- The signer clicks SEND NEW CODE to verify again.
What an internal signer sees
Signers who are LinkSquares users in your organization sign in to LinkSquares.
- Already signed in with the email address on the Signature Request: the signer skips verification. They see a message that they're signed in to LinkSquares as that user, and go straight to the agreement.
- Not signed in: the signer is asked to sign in to LinkSquares. After they sign in with the matching account, the agreement opens.
- Signed in as a different user: the signer sees the Enter your access code screen and verifies with a code sent to the address on the Signature Request.
Reassignment
- Allow signers to reassign on: signers still see REASSIGN TO SOMEONE ELSE. If an access code is required, the new signer verifies with their own code, sent to the email address they were reassigned to. See LinkSquares Sign: Signing and Recipient Experience for how reassigning works.
Allow signers to reassign off: signers don't see REASSIGN TO SOMEONE ELSE. Only the person you addressed can sign.
Review the Verification Record
- When a signer verifies, the event is recorded in the Activity tab of the individual agreement view and in the Signature History PDF sent with the executed agreement.
- The Signature History PDF shows that the signer's email address was verified.
- The Activity tab also records incorrect code attempts, so you can see failed verification steps as well as the successful one.
- Each Activity entry shows the signer's name, email address, IP address and the time, for example: "Jordan Lee at jordan.lee@example.com, 203.0.113.10 successfully verified their email address with a one-time passcode."
- If a signing link locks after too many incorrect attempts, the entry reads, for example: "Jordan Lee at jordan.lee@example.com, 203.0.113.10 failed email verification after too many incorrect passcode attempts."
Common Use Cases
Require Verification on Every Agreement
Scenario: Your legal team uses LinkSquares Sign for all e-signatures and needs to know each signature came from the addressed signer.
Steps:
- Open SETTINGS > Finalize App > SIGNATURE REQUESTS.
- Toggle Require access code to sign by default on.
- Send Signature Requests as usual. Every signer verifies before viewing or signing.
Keep Signing Authority with a Named Executive
Scenario: An MSA must be signed by the counterparty's CFO, and you don't want it delegated.
Steps:
- Start the Signature Request and add the CFO as the signer.
- In the builder, toggle Allow signers to reassign off for this request.
- Toggle Require access code to sign on so a forwarded email can't be used.
- Send the Signature Request.
Turn Verification Off for a Low-Risk Internal Form
Scenario: Your company requires verification by default, but an internal acknowledgment form goes to employees who are already signed in.
Steps:
- Start the Signature Request.
- In the builder, toggle Require access code to sign off for this request.
- Send the Signature Request.
Common Issues and Solutions
| Issue | Solution |
|---|---|
| The signer didn't receive the access code | Ask them to check spam or junk folders, then click Resend code. A new code can be requested every 60 seconds, up to five per hour from the same browser. The code goes only to the email address on the Signature Request. |
| The signer sees "Code expired" | Each code must be entered within 10 minutes of being sent. Requesting a new code cancels the previous unused one. The signer clicks Resend code and enters the new code. |
| The signer is locked out after too many attempts | Each code allows three incorrect attempts, and after the third the link is locked for 15 minutes. The signer waits for the 15:00 countdown on screen to finish, then requests a new code. If the link locks after 20 incorrect attempts in total, or 20 codes in 24 hours, the sender resends the Signature Request, which creates a new link. |
| The signer forwarded the email to a colleague, who can't open it | This is expected. The access code goes only to the original signer. If someone else should sign, the original signer can reassign (if allowed), or the sender can update the recipient and resend. |
| The signer's session expired before they finished | A signing session ends after 30 minutes of inactivity. The signer clicks SEND NEW CODE on the Your session has expired screen, verifies with the new code, and completes signing. |
| An internal signer is asked to sign in instead of entering a code | This is expected. LinkSquares users in your organization verify by signing in with the account that matches the Signature Request. |
| Signers still see REASSIGN TO SOMEONE ELSE | Check the setting on that Signature Request, not only the company default. Requests keep the settings they were sent with. To change it, void the request and send a new one with Allow signers to reassign off. |
Additional Notes
-
Existing Signature Requests: each request keeps the settings it was sent with.
Changing the company defaults affects only requests sent afterward. To change the settings on a request that's already out for signature, void it and send a new Signature Request. - Coming in a future release: only LS Sign Admins will be able to change Require access code to sign and Allow signers to reassign when sending a Signature Request. Other users will use the company defaults for every request they send.
- Resent requests: when a sender resends a Signature Request, the new link requires a new access code and starts with fresh attempt and code limits.
- Ordered signing: verification works with ordered signing. Each signer verifies when it's their turn.
- Copy recipients: recipients who only receive the executed agreement don't verify.
- Other e-signature providers: these settings apply to LinkSquares Sign only. DocuSign and Adobe Acrobat Sign have their own recipient authentication, configured in those products.
- Agentic Platform: signer verification works with the Agentic Platform. Signature Requests sent with LinkSquares Sign from the Agentic Platform follow the same company defaults, and your Customer Success Manager can configure those defaults for your organization. Coming in a future release: for companies that use only the Agentic Platform, internal signers will verify with an access code, even when they're signed in.
FAQ
Do counterparties need a LinkSquares account to verify?
No. External signers verify with a one-time code sent to their email. No account or password is needed.
Can a signer verify with a different email address?
No. The code is sent only to the email address on the Signature Request. To change the signer, the sender updates the recipient, or the signer reassigns if reassignment is allowed.
What happens if someone forwards the signing email?
The person who receives the forward can't view or sign without the access code, and the code is sent only to the original signer's email address.
If reassignment is allowed, does the new signer have to verify?
Yes. When an access code is required, the new signer receives their own code at their own email address.
Does turning on verification affect Signature Requests already out for signature?
No. Each request keeps the settings it was sent with. To change them, void the request and send a new Signature Request.
Can I require verification for some agreements and not others?
Yes. Set the company default, then toggle Require access code to sign on or off in the Signature Request builder for individual requests. Bulk sends and Auto-Send for Signature always use the company default.
Where can I see that a signer was verified?
In the agreement's Activity tab and in the Signature History PDF sent with the executed agreement.
Have questions about Signer Verification and Reassignment Settings?
Contact your LinkSquares administrator or reach out to LinkSquares Support for assistance.
Have feedback on this documentation?
We welcome your input to help us improve our knowledge base articles.