Repository navigation
Require at least one signature field before sending document #7710
Description
Activity
Thanks for your suggestion!
In LibreSign, a visible signature field is not required for a document to be signed. The document can be digitally signed even when no visible signature stamp is placed on the PDF.
Because of this, requiring at least one visible signature field before sending could block valid use cases where the signer only needs to apply a digital signature without a visual representation.
That said, I agree this can be confusing for some users. Instead of enforcing it globally, perhaps we could show a warning before sending or make it configurable through a policy for organizations that require visible signature fields.
If this requirement is important for your organization and you would like to prioritize its development, feel free to contact us about sponsorship or funding options.
This feature is now tracked as part of the broader form-fields roadmap in #8264.
The goal is to implement it on top of the shared field model and editor infrastructure instead of adding a separate field representation only for this use case.
This issue should remain open and focused on its original user requirement.
- added a parent issue
on Sep 6, 2026 A visible signature field is optional in a PDF digital signature, so LibreSign should not require one before sending a request.
The UX problem is still valid: LibreSign should explain this behavior more clearly to requesters and signers.
We are consolidating this work in #8321, with a clearer scope for the requester flow, signer flow, user preference and tests.
Please continue the discussion there if you have feedback or use cases we should consider.
Closing this in favor of #8321.
- removed a parent issue
on Sep 20, 2026 This was addressed with a different approach in #8321.
LibreSign will keep visible signature fields optional, because a PDF digital signature can be valid without a visible mark. Instead of blocking the request, we are improving the workflow to clearly inform the requester and the signer when no visible signature field is used.
Most of this work is already implemented, and the remaining part is tracked in #8321.
I will close this issue to keep the roadmap organized.
If this feature or LibreSign is useful for your organization, please consider supporting the project. LibreSign depends a lot on community support to keep development moving. You can help by starring the repository, sponsoring the project, contributing code, or using our enterprise support.
Is your feature request related to a problem? Please describe.
As a document creator in LibreSign, I can send a document to a
signer without placing any signature fields. This leads to confusion
for the recipient, who receives a document but has no idea where
or whether they need to sign.
Describe the solution you'd like
LibreSign should validate before sending a document that at least
one signature field has been placed. If no signature field exists,
the send button should be disabled or a warning message should
appear, preventing the document from being sent without a
designated signing area.
Describe alternatives you've considered
Currently the only alternative is an internal policy reminding
creators to always place signature fields manually. This is
error-prone and not a reliable solution, especially for teams
with multiple users.
Additional context
This would significantly improve the user experience for both
document creators and recipients. It is a common validation
feature in other signing tools like DocuSign or Adobe Sign and
would make LibreSign more professional and reliable for
business use.