starred/documenso

Fork 0

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

[GH-ISSUE #2258] React Integration V2 Prefill Email Not working #647

New issue

Open

opened 2026-02-26 18:47:54 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @KarloDerEchte on GitHub (Nov 27, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2258

Issue Description

When using the Direct Link Embed with V2 Documenso Documents I cant prefill the email so that the Signer Doesnt needs to add it. With V1 Documents it Works.

Steps to Reproduce

Create a V2 Template
Make a Direct Link Template out of it
Create a NextJS App
Add the Documenso Embed for React NPM Package
Make a DirectLink Component
6.prefill the email in the component
Start the App and See that the Document Doesnt has the email prefilled when clicking on complete After signing

Expected Behavior

The Email should be prefilled in V2 Documents as in V1 Documents

Current Behavior

Email is Not being Auto filled in Direct links implemented in a custom Website via the Documenso react integration

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Windows 11

Browser [e.g., Chrome, Firefox]

Chrome

Version [e.g., 2.0.1]

2.1.0

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @KarloDerEchte on GitHub (Nov 27, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2258 ### Issue Description When using the Direct Link Embed with V2 Documenso Documents I cant prefill the email so that the Signer Doesnt needs to add it. With V1 Documents it Works. ### Steps to Reproduce 1. Create a V2 Template 2. Make a Direct Link Template out of it 3. Create a NextJS App 4. Add the Documenso Embed for React NPM Package 5. Make a DirectLink Component 6.prefill the email in the component 7. Start the App and See that the Document Doesnt has the email prefilled when clicking on complete After signing ### Expected Behavior The Email should be prefilled in V2 Documents as in V1 Documents ### Current Behavior Email is Not being Auto filled in Direct links implemented in a custom Website via the Documenso react integration ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Windows 11 ### Browser [e.g., Chrome, Firefox] Chrome ### Version [e.g., 2.0.1] 2.1.0 ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [x] I have included relevant environment information. - [x] I have included any relevant screenshots. - [x] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem added the

status: triage

label

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

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Nov 27, 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 (Nov 27, 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:54 +03:00

Author

Owner

@KarloDerEchte commented on GitHub (Nov 27, 2025):

V1 (Expected)

@KarloDerEchte commented on GitHub (Nov 27, 2025): V1 (Expected) <img width="447" height="936" alt="Image" src="https://github.com/user-attachments/assets/1eed2c6b-6a06-4aa0-baf9-6b0e72b04826" />

kerem commented

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

Author

Owner

@KarloDerEchte commented on GitHub (Nov 27, 2025):

V2 Docs: Not working as expected

Code:

@KarloDerEchte commented on GitHub (Nov 27, 2025): V2 Docs: Not working as expected ![image](https://github.com/user-attachments/assets/4919db9e-8704-4f4a-8a0c-d3a7ed0fc555) Code: ![image](https://github.com/user-attachments/assets/2bd9484b-d5be-4866-a7cf-1b6c996cc108)

kerem commented

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

Author

Owner

@mykshaf commented on GitHub (Jan 15, 2026):

I am having the same issue, and worse, the email field locks after one letter, even if I pass lockedEmail=false

This means I cannot put the email in myself, and it's not pre-populated so I cannot sign.

@mykshaf commented on GitHub (Jan 15, 2026): I am having the same issue, and worse, the email field locks after one letter, even if I pass lockedEmail=false This means I cannot put the email in myself, and it's not pre-populated so I cannot sign.

kerem commented

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

Author

Owner

@KarloDerEchte commented on GitHub (Jan 15, 2026):

I am having the same issue, and worse, the email field locks after one letter, even if I pass lockedEmail=false

This means I cannot put the email in myself, and it's not pre-populated so I cannot sign.

What i did as a work around was not to use a template but creating a document from it first and than including the document itself

So instead of the template itself i create a Document from it first and then use the signing token of the document.

@KarloDerEchte commented on GitHub (Jan 15, 2026): > I am having the same issue, and worse, the email field locks after one letter, even if I pass lockedEmail=false > > This means I cannot put the email in myself, and it's not pre-populated so I cannot sign. What i did as a work around was not to use a template but creating a document from it first and than including the document itself So instead of the template itself i create a Document from it first and then use the signing token of the document.

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

No description provided.

Rows
Columns