[GH-ISSUE #1169] Copy signing link to send to recipients #337

Closed
opened 2026-02-26 18:46:34 +03:00 by kerem · 7 comments
Owner

Originally created by @TaylorHo on GitHub (May 22, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1169

Describe the improvement you are suggesting in detail

Actually, as I could see in the Dashboard, I can only re-send the email for recipients to sign the document. It would be great to have an option to copy the signing link to send directly to the recipient.
This improvement is a way to avoid the default emails going to Span (it happened to me).
The copy link option could be in the document submenu.

Additional Information & Alternatives (optional)

No response

Do you want to work on this improvement?

Yes

Please check the boxes that apply to this improvement suggestion.

  • I have searched the existing issues and improvement suggestions to avoid duplication.
  • I have provided a clear description of the improvement being suggested.
  • I have explained the rationale behind this improvement.
  • I have included any relevant technical details or design suggestions.
  • I understand that this is a suggestion and that there is no guarantee of implementation.
Originally created by @TaylorHo on GitHub (May 22, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1169 ### Describe the improvement you are suggesting in detail Actually, as I could see in the Dashboard, I can only re-send the email for recipients to sign the document. It would be great to have an option to copy the signing link to send directly to the recipient. This improvement is a way to avoid the default emails going to Span (it happened to me). The copy link option could be in the document submenu. ### Additional Information & Alternatives (optional) _No response_ ### Do you want to work on this improvement? Yes ### Please check the boxes that apply to this improvement suggestion. - [X] I have searched the existing issues and improvement suggestions to avoid duplication. - [X] I have provided a clear description of the improvement being suggested. - [X] I have explained the rationale behind this improvement. - [X] I have included any relevant technical details or design suggestions. - [X] I understand that this is a suggestion and that there is no guarantee of implementation.
Author
Owner

@github-actions[bot] commented on GitHub (May 22, 2024):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

<!-- gh-comment-id:2124738131 --> @github-actions[bot] commented on GitHub (May 22, 2024): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)
Author
Owner

@TaylorHo commented on GitHub (May 22, 2024):

Oh, I found the option now, I need to click in the signer email to copy the link. It's nice to have an option for this, but I also suggest having this same option in the submenu, since it's easiest to find this information there - it's the place where people look into it.

What do you guys think of it?

<!-- gh-comment-id:2124746547 --> @TaylorHo commented on GitHub (May 22, 2024): Oh, I found the option now, I need to click in the signer email to copy the link. It's nice to have an option for this, but I also suggest having this same option in the submenu, since it's easiest to find this information there - it's the place where people look into it. What do you guys think of it?
Author
Owner

@dguyen commented on GitHub (Jun 12, 2024):

Hey, sorry for the delayed response

That's a good idea, we'll ask our designer work on this and will try get it in soon

<!-- gh-comment-id:2162261440 --> @dguyen commented on GitHub (Jun 12, 2024): Hey, sorry for the delayed response That's a good idea, we'll ask our designer work on this and will try get it in soon
Author
Owner

@myspace20 commented on GitHub (Jul 3, 2024):

Hello, I would like to work on this feature.

<!-- gh-comment-id:2207310161 --> @myspace20 commented on GitHub (Jul 3, 2024): Hello, I would like to work on this feature.
Author
Owner

@TaylorHo commented on GitHub (Jul 3, 2024):

Go ahead @myspace20, I haven't done anything on it yet, and I think that @dguyen hasn't either.

<!-- gh-comment-id:2207400428 --> @TaylorHo commented on GitHub (Jul 3, 2024): Go ahead @myspace20, I haven't done anything on it yet, and I think that @dguyen hasn't either.
Author
Owner

@myspace20 commented on GitHub (Jul 3, 2024):

Okay

<!-- gh-comment-id:2207446368 --> @myspace20 commented on GitHub (Jul 3, 2024): Okay
Author
Owner

@ephraimduncan commented on GitHub (Sep 21, 2024):

Closing this as you can currently do that with the current version.

<!-- gh-comment-id:2365331649 --> @ephraimduncan commented on GitHub (Sep 21, 2024): Closing this as you can currently do that with the current version.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#337
No description provided.