starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #1576] Support an upload field #444

New issue

Open

opened 2026-02-26 18:47:04 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @limegorilla on GitHub (Jan 8, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1576

Feature Description

Docusign currently allows our signees to upload files inline when singing a document.

We add a field to the document to require an upload - like any other field. The signee has to then upload a file. This will then attach to the document.

This would then attach to the final PDF that's created as another page - which limits this to image-based files.

Use Case

We use this for a few reasons - namely:

Supplier onboarding (capturing compliance documents, such as insurance)
Operative onboarding (proof of address etc.)

This allows our staff to send out one request that has to be responded to. It's a great help to them as they don't have to chase separately, and it's clear to anyone signing that they need to submit xyz documents to complete the process.

We really struggle to get signees to get our documents back, and this would completely alleviate that. I think it's also useful for general onboarding tasks most companies have to do in terms of staff etc.

Proposed Solution

** I am new to the repo, so as I am going through and seeing how things work I'll update this **

At a high level:

Create a new upload field
- Allow form creator to specify MIME type
- Possible restrictions on this (e.g, allow image/*, application/pdf... but not .exe or .dmg as an example)
Create API endpoint to accept uploaded file
- Would need to store in DB - at least temporarily while the document is being signed as not to loose state.
- Would say there's (IMO) no point in keeping after as the file should be then attached to the completed PDF.

This would necessitate:

New API route(s)
Storage considerations

Alternatives (optional)

There is the obvious "just ask signee to send an email with files attached" but as I outlined above - this would create a huge amount of friction for us.

We are also slowly getting systems built around our legacy ones that do not have built-in ways of accepting uploads, or API's to add them in ourselves.

Additional Context

We are switching to documenso in the summer - this is something I am planning on working on and implementing before then. I would like to get feedback and ideas from the community in terms of how this should be implemented.

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 @limegorilla on GitHub (Jan 8, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1576 ### Feature Description Docusign currently allows our signees to upload files inline when singing a document. We add a field to the document to require an upload - like any other field. The signee has to then upload a file. This will then attach to the document. This would then attach to the final PDF that's created as another page - which limits this to image-based files. ### Use Case We use this for a few reasons - namely: - Supplier onboarding (capturing compliance documents, such as insurance) - Operative onboarding (proof of address etc.) This allows our staff to send out one request that has to be responded to. It's a great help to them as they don't have to chase separately, and it's clear to anyone signing that they need to submit xyz documents to complete the process. We really struggle to get signees to get our documents back, and this would completely alleviate that. I think it's also useful for general onboarding tasks most companies have to do in terms of staff etc. ### Proposed Solution ** I am new to the repo, so as I am going through and seeing how things work I'll update this ** At a high level: 1. Create a new upload field - Allow form creator to specify MIME type - Possible restrictions on this (e.g, allow image/*, application/pdf... but not .exe or .dmg as an example) 2. Create API endpoint to accept uploaded file - Would need to store in DB - at least temporarily while the document is being signed as not to loose state. - Would say there's (IMO) no point in keeping after as the file should be then attached to the completed PDF. This would necessitate: - New API route(s) - Storage considerations ### Alternatives (optional) There is the obvious "just ask signee to send an email with files attached" but as I outlined above - this would create a huge amount of friction for us. We are also slowly getting systems built around our legacy ones that do not have built-in ways of accepting uploads, or API's to add them in ourselves. ### Additional Context We are switching to documenso in the summer - this is something I am planning on working on and implementing before then. I would like to get feedback and ideas from the community in terms of how this should be implemented. ### 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

kerem added the

Stale

status: triage

labels

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

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jan 8, 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

@github-actions[bot] commented on GitHub (Jan 8, 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)

kerem commented

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

Author

Owner

@seamon67 commented on GitHub (Jun 18, 2025):

+1 to this. An upload field would be a game changer

@seamon67 commented on GitHub (Jun 18, 2025): +1 to this. An upload field would be a game changer

kerem referenced this issue

2026-02-26 19:31:18 +03:00

[PR #448] [CLOSED] fix: completed count incorrect #976

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

No description provided.

Rows
Columns