Repository navigation
Templates for a quicker workflow #5628
Description
Is your feature request related to a problem? Please describe.
When sending the same document again but to different person for signature, you currently have to manually place the signature field(s) each time.
Describe the solution you'd like
Hello!
Wouldn’t it be more efficient to create templates with predefined signature fields, so you only need to select or enter who must sign in each field?
For example, if you have a document like a contract that you use multiple times for different cases, templates would make the workflow much faster.
When creating a template, you select the file you want to include, optionally multiple files, and then place the signature fields. You can label each field (e.g., “CEO”) or any label you prefer and give the template a custom name.
After that, you simply choose a template, assign the signers to each field, and send it.
Best regards,
Niklas
Describe alternatives you've considered
No response
Additional context
No response
Activity
henmohr commentedon Oct 24, 2025
Hey, that's a nice idea! Would be much more faster to sign documents. We've thought about this functionality before but no issue was created since then.
Also, if you are signing a lot of contracts, would be very unpleasant to ask you to sponsor the project?
(not saying that this would implemented ASAP)
https://github.com/sponsors/LibreSign
darkfight14 commentedon Oct 24, 2025
Hey, thats kind of weird why nobody asked for that feature.
Because that makes it so much easier for companies or a to sign a lot of stuff multiple times like a privacy documentation or something like that.
I‘ve already thought about to sponsor this project. Thats great work, that has to be appreciated.
Happy coding and no hurry for that feature but you‘re free to implement it earlier 😂
Best regards,
Niklas
henmohr commentedon Oct 24, 2025
Indeed, very strange!
Thanks for sponsoring, thought!
vitormattos commentedon Oct 30, 2025
Thank you, this is a very good feature request and it makes a lot of sense for users who frequently send similar documents for signature. Looking at your scenario and needs, having a template workflow with predefined fields could indeed save a lot of time and reduce repetitive steps.
However, before moving forward with an implementation, we’ll need to carefully think about the entire flow, both on the frontend (visual and usability aspects) and the backend (data structure and signing logic).
For example, we’d need to evaluate:
This idea is also related to the discussion in #4165, since both deal with improving the usability of workflows involving multiple, similar documents.
It would be great if we could first outline the expected flow more clearly, for example, with a step-by-step description explaining how the template would behave when applied to a new document. That would help us understand where it fits in the current architecture and what kind of UI and API adjustments would be required.
Once we have that, we can evaluate the technical feasibility and define the implementation path step by step.
If you’re interested, we’d be happy to discuss how to support or co-fund this feature, either through a one-time sponsorship (to prioritize its implementation) or through ongoing support to ensure maintenance and continuous improvement. If full funding isn’t possible, any recurring contribution via GitHub Sponsors is also greatly appreciated to help the project.
Thank you again for helping make LibreSign better with this excellent feature suggestion. Contributions like this truly move the project forward. 💚
kiplingw commentedon Jul 7, 2026
This would be very useful. It's a feature very common in mainstream proprietary alternatives like DropBox Sign, Adobe Sign, Docusign, etc.
vitormattos commentedon Sep 6, 2026
The form-field work tracked in #8264 should provide part of the foundation for reusable templates.
Templates have a broader scope than form fields, so this issue should remain independent, but predefined field definitions and later recipient assignment should follow the model introduced by that epic.
[-][FEATURE]: Templates for a quicker workflow[/-][+]Templates for a quicker workflow[/+]