Repository navigation
Option to add initials to document #5273
Description
Is your feature request related to a problem? Please describe.
Many documents require the signer to apply initials in several places as well as a full signature. LibreSign appears to only have the option to apply a full signature, multiple times.
Describe the solution you'd like
In settings/admin/libresign, a near-duplicate of the "Signature stamp" section for "Initials stamp". Have it set just the initials from the signer's name.
Add signer --> Next, where it says "Select a signer to set their signature position", split the signer buttons into full signature or just initials.
Describe alternatives you've considered
The admin section doesn't necessarily need the "Initials stamp" part added, as long as the option exists to add just initials where needed.
Additional context
No response
Activity
[-][FEATURE]: Option to add initials to document[/-][+]Option to add initials to document[/+]vitormattos commentedon Aug 6, 2025
Hi @ASerbinski, thank you for the excellent suggestion!
You're absolutely right, many documents require not just full signatures but also initials in specific locations, and having native support for that in LibreSign would be an excelent improvement.
We really like your idea of extending the interface to include an "Initials stamp" option, either as part of the admin settings or directly in the document preparation flow. It's a thoughtful feature that would enhance usability for many use cases.
That said, implementing and maintaining features like this takes time of our team, and we're currently focusing development efforts based on demand and support from customers and sponsors. If your organization (or others in the community) are interested in helping fund this feature, we'd be happy to prioritize it. You can reach out through our contact form or via GitHub Sponsors. One-time or recurring contributions are welcome!
Thanks again for helping us make LibreSign better!
vitormattos commentedon Sep 6, 2026
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.