starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #112] [DOC-230] Signature Workflow #34

New issue

Closed

opened 2026-02-26 18:45:04 +03:00 by kerem · 13 comments

kerem commented

2026-02-26 18:45:04 +03:00

Owner

Originally created by @ElTimuro on GitHub (Apr 15, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/112

Signatures never exist in a vacuum
The workflow around the signature is an important part of the domain
Recognizing that we want Documenso to support flexible workflow types to enable all kinds of real-life flow
Some fundamental types and rules for workflows are: Signing order, Parallel or sequential signing
Defining Subsitue signer for a step in the workflow

This feature will heavily integrate with the team inbox

Originally created by @ElTimuro on GitHub (Apr 15, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/112 * Signatures never exist in a vacuum * The workflow around the signature is an important part of the domain * Recognizing that we want Documenso to support flexible workflow types to enable all kinds of real-life flow * Some fundamental types and rules for workflows are: Signing order, Parallel or sequential signing * Defining Subsitue signer for a step in the workflow This feature will heavily integrate with the team inbox

kerem closed this issue

2026-02-26 18:45:04 +03:00

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@daallgeier commented on GitHub (May 28, 2023):

These workflows will be a pre-requisit for many organisations out there to complete a switch.

@daallgeier commented on GitHub (May 28, 2023): These workflows will be a pre-requisit for many organisations out there to complete a switch.

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@ElTimuro commented on GitHub (Nov 27, 2023):

Moved to Q1, but signer roles (CC, approved etc.) could be a possibility for EOY

@ElTimuro commented on GitHub (Nov 27, 2023): Moved to Q1, but signer roles (CC, approved etc.) could be a possibility for EOY

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@harkiratsm commented on GitHub (Feb 9, 2024):

Are we moving in the direction of managing the actions of each recipient?

@harkiratsm commented on GitHub (Feb 9, 2024): Are we moving in the direction of managing the actions of each recipient? ![image](https://github.com/documenso/documenso/assets/71957674/bb7acb37-d920-44e1-b7ba-11b5c079937d)

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@ElTimuro commented on GitHub (Feb 12, 2024):

@harkiratsm we already merged the roles into main 👀 rescoping this to advanced workflows using ordering

@ElTimuro commented on GitHub (Feb 12, 2024): @harkiratsm we already merged the roles into main 👀 rescoping this to advanced workflows using ordering

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@ElTimuro commented on GitHub (Feb 12, 2024):

Rescoping to advanced workflows and moving to longterm roadmap

@ElTimuro commented on GitHub (Feb 12, 2024): Rescoping to advanced workflows and moving to longterm roadmap

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@yl-chow commented on GitHub (Mar 7, 2024):

Was looking forward to having this feature as it is a crucial part for our organisation. Hope this gets prioritised again.

@yl-chow commented on GitHub (Mar 7, 2024): Was looking forward to having this feature as it is a crucial part for our organisation. Hope this gets prioritised again.

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@lodembeep commented on GitHub (Apr 11, 2024):

Hey guys, bumping this up since it is a very interesting feature that is worth prioritising. Mostly the Parallel or sequential signing.

@lodembeep commented on GitHub (Apr 11, 2024): Hey guys, bumping this up since it is a very interesting feature that is worth prioritising. Mostly the Parallel or sequential signing.

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@ElTimuro commented on GitHub (Apr 12, 2024):

Hey guys, bumping this up since it is a very interesting feature that is worth prioritising. Mostly the Parallel or sequential signing.

noted. Any particular use cases for each? would love to learn

@ElTimuro commented on GitHub (Apr 12, 2024): > Hey guys, bumping this up since it is a very interesting feature that is worth prioritising. Mostly the Parallel or sequential signing. noted. Any particular use cases for each? would love to learn

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@lodembeep commented on GitHub (Apr 15, 2024):

Sequential would be great for us since it would let a Viewer or Approver see if the document has been signed before approving or viewing.

Say i send a document to someone for signing and add myself as an approver, i don't want to approve a document who hasn't been signed since i sent it. Doing so would help me and my collaborators to easily follow on who did sign or not.
Right now, we don't really know what is going on and only a blank copy of the document is shared untill every participant has signed the document.

I am not really sure for parallel, but i think that the demand for it would raise as soon as sequential signing is available.

@lodembeep commented on GitHub (Apr 15, 2024): Sequential would be great for us since it would let a Viewer or Approver see if the document has been signed before approving or viewing. Say i send a document to someone for signing and add myself as an approver, i don't want to approve a document who hasn't been signed since i sent it. Doing so would help me and my collaborators to easily follow on who did sign or not. Right now, we don't really know what is going on and only a blank copy of the document is shared untill every participant has signed the document. I am not really sure for parallel, but i think that the demand for it would raise as soon as sequential signing is available.

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@ElTimuro commented on GitHub (Apr 16, 2024):

Thanks for sharing 🙏
The sequential case makes sense
Parallel is what we currently have, and interesting question is, if combining the two makes sense or if that's just too complex: e.g. 1 persons signs, then 1 approves, then 3 people do things in parallel

@ElTimuro commented on GitHub (Apr 16, 2024): - Thanks for sharing 🙏 - The sequential case makes sense - Parallel is what we currently have, and interesting question is, if combining the two makes sense or if that's just too complex: e.g. 1 persons signs, then 1 approves, then 3 people do things in parallel

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@lodembeep commented on GitHub (Apr 16, 2024):

makes sense too, but maybe after the sequential feature is made available, some sort of hybrid mode

@lodembeep commented on GitHub (Apr 16, 2024): 3. makes sense too, but maybe after the sequential feature is made available, some sort of hybrid mode

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@ElTimuro commented on GitHub (Apr 17, 2024):

Yes, sequential should be the first thing to be released, since it's the most impactful and common I would expect

@ElTimuro commented on GitHub (Apr 17, 2024): - Yes, sequential should be the first thing to be released, since it's the most impactful and common I would expect

kerem commented

2026-02-26 18:45:05 +03:00

Author

Owner

@Mythie commented on GitHub (Dec 6, 2024):

We now support parallel, sequential and signing orders!

Docs need an update though 🥵

@Mythie commented on GitHub (Dec 6, 2024): We now support parallel, sequential and signing orders! Docs need an update though 🥵

kerem referenced this issue

2026-02-26 18:48:39 +03:00

[PR #34] [MERGED] [new] Add prettier #722

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#34

No description provided.

Rows
Columns