3 min read
Updated Apr 12, 2026
Public signing links are a controlled part of the recipient experience, not a general file-sharing mechanism. Their behavior depends on workspace defaults, document settings, and secure token handling.
A package that uses recipient signing links
Awareness of workspace security defaults
A need to explain link behavior to a stakeholder or recipient
Signelio issues random recipient tokens and stores only their hashes in the backend.
This helps limit exposure if data is inspected outside the authorized path.
Link expiration is configurable and should match the sensitivity and timing of the workflow.
If the workflow needs stronger control, shorten the access window rather than relying only on reminders.
Use the intended notification path and controlled resend flows instead of copying links into uncontrolled channels.
That keeps both access handling and audit context cleaner.
Align due dates and expiration windows so recipients are not surprised.
Short access windows are useful for sensitive workflows, but they also increase follow-up pressure.
Review public-link defaults as part of workspace setup, not only after a problem occurs.
Use this as a quick signal while the public knowledge base is static.
Our support team is here to assist you.