starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 06:15:58 +03:00

[GH-ISSUE #705] [OSSHACK] Recipient Roles #206

New issue

Closed

opened 2026-02-26 18:45:52 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @Mythie on GitHub (Dec 1, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/705

Improvement Description

Add the ability to specify a role for a recipient. This will include CC (Carbon Copy), Signer, Viewer, and Approver.

Signers will be able to sign the document as per usual.
Approvers may be able to sign the document but will also be able to approve the document without signing it.
Viewers will be able to view the document but will not be able to sign or approve it.
CCs will only receive a copy of the completed document.

Rationale

Not all recipients of a given document need to sign it. Some recipients may only need to view the document, others may need to approve it, and others may need to sign it. Support for these roles will allow for more flexibility in the types of documents that can be created and sent.

Proposed Solution

Add a role enum to the Recipient model that contains the role types.
Update the add signers step to allow for the selection of a role for each recipient defaulting to Signer.
Update our signing flow to allow for the different roles.
Update the recipient popover to display the role of each recipient in addition to their email.
Update our complete document flow to allow for the different roles and email sending requirements.

Alternatives

N/A

Additional Context

The design for this improvement can be found on our Figma: https://www.figma.com/file/mKYFxgmekwxXsoXCP9dXXx/Documenso-Design-System?type=design&node-id=4%3A336&mode=design&t=RCNR7fdt1cxJEReM-1

Originally created by @Mythie on GitHub (Dec 1, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/705 ## Improvement Description Add the ability to specify a role for a recipient. This will include CC (Carbon Copy), Signer, Viewer, and Approver. - Signers will be able to sign the document as per usual. - Approvers may be able to sign the document but will also be able to approve the document without signing it. - Viewers will be able to view the document but will not be able to sign or approve it. - CCs will only receive a copy of the completed document. ## Rationale Not all recipients of a given document need to sign it. Some recipients may only need to view the document, others may need to approve it, and others may need to sign it. Support for these roles will allow for more flexibility in the types of documents that can be created and sent. ## Proposed Solution - Add a `role` enum to the `Recipient` model that contains the role types. - Update the add signers step to allow for the selection of a role for each recipient defaulting to `Signer`. - Update our signing flow to allow for the different roles. - Update the recipient popover to display the role of each recipient in addition to their email. - Update our complete document flow to allow for the different roles and email sending requirements. ## Alternatives N/A ## Additional Context - The design for this improvement can be found on our Figma: https://www.figma.com/file/mKYFxgmekwxXsoXCP9dXXx/Documenso-Design-System?type=design&node-id=4%3A336&mode=design&t=RCNR7fdt1cxJEReM-1

kerem

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

closed this issue
added the
Stale

osshack
labels

kerem commented

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

Author

Owner

@e-roy commented on GitHub (Dec 2, 2023):

@Mythie I'm interested in starting on this.

@e-roy commented on GitHub (Dec 2, 2023): @Mythie I'm interested in starting on this.

kerem commented

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

Author

Owner

@Mythie commented on GitHub (Dec 2, 2023):

For OSSHack participants we won’t be assigning or following our usual guidelines, please start work if you want to do the challenge.

The first good solution (read: to acceptable quality and conformance) wins!

@Mythie commented on GitHub (Dec 2, 2023): For OSSHack participants we won’t be assigning or following our usual guidelines, please start work if you want to do the challenge. The first *good* solution (read: to acceptable quality and conformance) wins!

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jan 2, 2024):

This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

@github-actions[bot] commented on GitHub (Jan 2, 2024): This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

kerem referenced this issue

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

[PR #206] [CLOSED] feat: add google as auth provider #791

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

No description provided.

Rows
Columns