[GH-ISSUE #2312] CC documents should also be shown in the Inbox if user has an account #655

Open
opened 2026-02-26 18:47:56 +03:00 by kerem · 3 comments
Owner

Originally created by @d-schiffner on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2312

Feature Description

If a user has been added as a "needs to view" and/or receives a copy, there is currently no way to view the document from within documenso for that user.

For users with accounts it would be very helpful to also have the ability to see documents, where they are in the CC Role.

Looking at the source code, I do find a filter in the find.inbox trpc method, that actively filters out the CC recipient role, but I do not know what use case is being considered here.

Use Case

I a user is being identified and no email has been generated, there is no way for the recipient (CC) to retrieve a document (or at least I did not find it).

The inbox can contain both documents which need attention (i.e. signing, approval) but also the copies without any additional downsides.

Proposed Solution

As both the role and inbox already do exist, the CC might be simply done by adding the Recipient with CC into the filtered list, if the user currently using the UI is the user in question.

Without in-depth knowledge, I cannot say, if just removing the where-clause actually breaks something further down the line, but this might be a simple fix for this.

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 @d-schiffner on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2312 ### Feature Description If a user has been added as a "needs to view" and/or receives a copy, there is currently no way to view the document from within documenso for that user. For users with accounts it would be very helpful to also have the ability to see documents, where they are in the CC Role. Looking at the source code, I do find a filter in the find.inbox trpc method, that actively filters out the CC recipient role, but I do not know what use case is being considered here. ### Use Case I a user is being identified and no email has been generated, there is no way for the recipient (CC) to retrieve a document (or at least I did not find it). The inbox can contain both documents which need attention (i.e. signing, approval) but also the copies without any additional downsides. ### Proposed Solution As both the role and inbox already do exist, the CC might be simply done by adding the Recipient with CC into the filtered list, if the user currently using the UI is the user in question. Without in-depth knowledge, I cannot say, if just removing the `where`-clause actually breaks something further down the line, but this might be a simple fix for this. ### 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. - [x] I have provided a detailed description of the requested feature. - [x] I have explained the use case or scenario for this feature. - [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. - [x] I want to work on creating a PR for this issue if approved
Author
Owner

@coderabbitai[bot] commented on GitHub (Dec 10, 2025):

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

  • Create Plan
Examples

🔗 Similar Issues

Possible Duplicates

  • ISSUE-1799

Related Issues

documenso/documenso#1179 - fix: add correct role names for direct templates [merged]

👤 Suggested Assignees

  • sebastianhelbig
  • mspisars
  • NDCallahan
  • raerhe
  • chrisirhc

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false
<!-- gh-comment-id:3638152064 --> @coderabbitai[bot] commented on GitHub (Dec 10, 2025): <!-- This is an auto-generated issue plan by CodeRabbit --> ## 📝 CodeRabbit Plan Mode Generate an implementation plan and agent prompts for this issue. - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan <details> <summary>Examples</summary> - [Example 1](https://github.com/coderabbitai/git-worktree-runner/issues/29#issuecomment-3589134556) - [Example 2](https://github.com/coderabbitai/git-worktree-runner/issues/12#issuecomment-3606665167) </details> ## 🔗 Similar Issues **Possible Duplicates** - ISSUE-1799 **Related Issues** - [documenso/documenso#1799](https://github.com/documenso/documenso/issues/1799) - [documenso/documenso#2027](https://github.com/documenso/documenso/issues/2027) - [documenso/documenso#2140](https://github.com/documenso/documenso/issues/2140) - [documenso/documenso#1914](https://github.com/documenso/documenso/issues/1914) - [documenso/documenso#1908](https://github.com/documenso/documenso/issues/1908) ## 🔗 Related PRs documenso/documenso#1179 - fix: add correct role names for direct templates [merged] ## 👤 Suggested Assignees - sebastianhelbig - mspisars - NDCallahan - raerhe - chrisirhc --- <details> <summary> 🧪 Issue enrichment is currently in early access.</summary> To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details>
Author
Owner

@github-actions[bot] commented on GitHub (Dec 10, 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:3638152715 --> @github-actions[bot] commented on GitHub (Dec 10, 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)
Author
Owner

@d-schiffner commented on GitHub (Dec 10, 2025):

Something like this:

Image

I just adjusted the where clause in the inbox trpc call.

<!-- gh-comment-id:3638819412 --> @d-schiffner commented on GitHub (Dec 10, 2025): Something like this: <img width="1241" height="480" alt="Image" src="https://github.com/user-attachments/assets/08752e44-9430-4ee2-ae6b-48657d5f9f36" /> I just adjusted the where clause in the inbox trpc call.
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#655
No description provided.