[GH-ISSUE #1813] Allow grouping of Signing order #524

Open
opened 2026-02-26 18:47:25 +03:00 by kerem · 1 comment
Owner

Originally created by @Pravpraskumar on GitHub (May 28, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1813

Feature Description

When enabling the signing order, we cannot assign the same sequence number to multiple signers to merge both the sequential and parallel flows.

Use Case

While assigning the Document Signers, if the user selects the Signing order, we can only sequence the order, but cannot use the same sequence number for two or more signers.

By allowing the same sequence number for multiple signers, the system will run in both sequential and Parallel flows on the same Document Signing Process.

Proposed Solution

No response

Alternatives (optional)

No response

Additional Context

No response

Please check the boxes that apply to this feature request.

  • I have searched the existing feature requests to make sure this is not a duplicate.
  • I have provided a detailed description of the requested feature.
  • I have explained the use case or scenario for this feature.
  • 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.
  • I want to work on creating a PR for this issue if approved
Originally created by @Pravpraskumar on GitHub (May 28, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1813 ### Feature Description When enabling the signing order, we cannot assign the same sequence number to multiple signers to merge both the sequential and parallel flows. ### Use Case While assigning the Document Signers, if the user selects the Signing order, we can only sequence the order, but cannot use the same sequence number for two or more signers. By allowing the same sequence number for multiple signers, the system will run in both sequential and Parallel flows on the same Document Signing Process. ### Proposed Solution _No response_ ### Alternatives (optional) _No response_ ### Additional Context _No response_ ### Please check the boxes that apply to this feature request. - [x] I have searched the existing feature requests to make sure this is not a duplicate. - [ ] I have provided a detailed description of the requested feature. - [ ] I have explained the use case or scenario for this feature. - [ ] 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. - [ ] I want to work on creating a PR for this issue if approved
Author
Owner

@github-actions[bot] commented on GitHub (May 28, 2025):

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:2916404944 --> @github-actions[bot] commented on GitHub (May 28, 2025): 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)
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#524
No description provided.