Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the ability to share signature requests #3775

Open
DazeEnd opened this issue Oct 9, 2024 · 1 comment
Open

Add the ability to share signature requests #3775

DazeEnd opened this issue Oct 9, 2024 · 1 comment
Labels
feature-request New feature request question Further information is requested

Comments

@DazeEnd
Copy link

DazeEnd commented Oct 9, 2024

Is your feature request related to a problem? Please describe.
It would be nice if signature requests could be shared with other users who are not signers.

For example, in an office setting there may be two coworkers: Staff1 and Staff2. Staff1 requests the signature of a client ("Client") on a document. It would be nice if there was a way for Staff1 to share the signature request with Staff2 so that Staff2 could see if the document has been signed yet.

Ideally, this sharing mechanism would have a permission set so that the signature request could be shared as either read-only (i.e. see the status of the signature) or full edit permission (which would allow Staff2 to modify the signature request by adding additional signers or repositioning signature boxes.)

This would be great for teams that are working with LibreSign.

Describe the solution you'd like
I think it would be easiest (for the end user) to use the existing sharing features that are built into Nextcloud Files. If a user, "Staff2", has a file shared with him (either the file directly, or a folder containing the file), then Staff2 has permission to any attached signature requests as well. A read-only share would then restrict Staff2 to viewing the LibreSign status. A share that grants "edit" permission to Staff2 would allow Staff2 to modify any attached signature request (signers, signature placement, etc.) People who have received a signature request share should receive email notifications, just as the requester of the signature currently does.

Describe alternatives you've considered
It would also be conceivable that a completely separate permission system be built for LibreSign, but I fear that having two separate permission systems, probably using similar terms, would be confusing for users (especially casual users).

Additional context
N/A

@DazeEnd DazeEnd added the feature-request New feature request label Oct 9, 2024
@github-project-automation github-project-automation bot moved this to 0. Needs triage in Roadmap Oct 9, 2024
@vitormattos
Copy link
Member

The idea to make possible to list groups when request to sign and allow to choose a group could solve this. I agree that this could have problems. Maybe other good point to implement together with allow to share with a group is also allow to choose a circle from app Circles because a Circle is most flexible than a group.

Other related subject to this issue is to think about how to attach a certificate to a circle or a group by a secure way to make possible use a certificate generated by a CA of a PKI outside of LibreSign to able to all members of a group, circle or other kind of aggregation of signers to be sign the document using this certificate. A scenario related to this is when we have a director that represent the company and need to use the digital certificate of the company and this director go off on vacation and need to have another person to sign in your place representing the company. Is important to think about this because now already is possible to upload a digital certificate when sign a document.

@vitormattos vitormattos added the question Further information is requested label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature request question Further information is requested
Projects
Status: 0. Needs triage
Development

No branches or pull requests

3 participants
@vitormattos @DazeEnd and others