Practical guide

Sharing a signer access code without confusing the recipient

Last materially reviewed 2026-09-21

Quick answerTreat an access code as private access information, not as a public part of a signing link.
What to know

Verify compatibility with the documented access mechanism

Signaturely’s help describes copying a signer access code when the security option is enabled and sharing it with the intended signer. This establishes a documented mechanism, not proof that it satisfies every organization’s authentication requirements. Confirm the appropriate setting and recipient for the actual request. Do not put real codes in screenshots, shared checklists, analytics events or public support examples while explaining the process.

What to know

Make the instruction understandable

A recipient should know which request the code belongs to and where to enter it, without needing to guess from several unrelated messages. Keep the explanation short and use an established contact route. Do not send sensitive document contents merely to identify the request. If your organization requires a separate channel for access information, follow that policy rather than choosing convenience over the existing security procedure.

What to know

Limit private-data exposure during recovery

When a person reports difficulty, first check whether the request, recipient and code are the intended ones. Avoid forwarding access details to a new address simply because someone asks in an unverified message. A signing URL and its access code can together provide meaningful access. If identity or authority is uncertain, pause the transmission and use the established verification route. This is a handling principle, not a substitute for professional security advice.

What to know

Keep tests non-sensitive

Use a clearly labelled harmless sample to check whether the instructions are understandable. Do not collect a visitor’s real code in a website tool or use it as a demonstration value. Record the outcome without retaining the code itself in unnecessary logs. The direct-link guide explains how to reuse an existing request safely; the privacy guide covers which information should remain outside general-purpose notes and reporting.

Continue when useful

Next: Use an existing signing link without creating another request

Recover access to the original request when appropriate; do not manufacture a replacement agreement.

Open Use an existing signing link without creating another request →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Share the signer access code — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21
  2. Get an existing signing link — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21