LibreSign / LibreSign/libresign
Allow a new set of signatures on the same original document
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 818
- Forks
- 146
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 326
Description
Is your feature request related to a problem? Please describe.
I created a test PDF Test signature.pdf for userA to sign, once signed, a new file Test signature.signed.pdf was created. Let's say this is a code of conduct or something.
A week later, I need userB to read and sign that document, but I need a separate "signed" pdf.
If I want another person to sign the same document (ie: code of conduct), I would need to copy the original file I'm guessing and now for two signatures I have 4 files.
Describe the solution you'd like
On the sidebar:
For the original document:
Show who requested the signature of that document and if/when it was signed for each "batch"
Admin on .... requested a signature to: userA, userD
userA signed on ....
userD signed on...
Add a button, "request new signatures" that will use the same predefined signing area, but we can set who needs to sign where
Describe alternatives you've considered
Right now I need to copy the original PDF so LibreSign sidebar allows for another set of signatures.
Additional context
Clear confusion between signed and unsigned file
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the sidebar flow for original and signed PDFs, including the confusion referenced in issue #4160. Trace how the current signing area and signature request are associated with a copied document, then define the design for multiple signature batches on one original; done means new recipients can sign the same predefined areas while each batch has separate status and signed output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100