Skip to main content
arrow-left Back to Docusign.com

Hello, I am integrating delegation into the embedded signing process using the Node.js SDK. I set the parameter 'allowReassign: true' in the envelope, and in my developer account, the setting 'Allow recipients to reassign' is enabled. However, when I generate the recipient view link with the standard interface, the 'Assign to someone else' button is not visible. In contrast, the button is visible in the non-embedded flow. Are there additional configurations required to enable the reassign button in the embedded flow? What am I doing wrong in the embedded signing process? Thanks for your support.

Hello, ​@ValeCodo 

 

Verify these settings in the account level:

 

Then in the envelope level: 

 

Let us to know, If this solves your issue, give your Like here, pls.

 

Best,

Alexandre

Hi ​​@ValeCodo,

I hope you are doing well.

I want to confirm if you were able to solve your issue by utilizing the suggested solution or if the information provided was useful. If so, please mark it as the best answer by clicking “Select as Best” to make it easier for other users to find. Otherwise, let me know, and I will gladly help you address the situation as soon as possible.

 

Best regards,

Melanie | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Hello ​@Alexandre.Augusto and ​@Melanie.Panguito ,

thanks for your replies. In my account the options are set:

In embedded signing the button “Assign to someone else” is not yet present. Can you help me? Thanks.

Hello ​@ValeCodo,

Thank you for the update. 

Delegated signing requires the recipient to be a Docusign account member. In contrast, an embedded recipient view is usually assigned to a captive recipient instead. A captive recipient, also known as an embedded recipient, is a person who can sign without a Docusign account. This is the opposite of a placeholder recipient outside of Docusign. 

If a captive recipient is being used, (Captive recipients are also referred to as embedded recipients) which is very common in embedded signing scenarios, and the flow uses it, then it is not compatible with the delegated signing feature. My sincere apologies.

Articles: 

Captive recipients

Embedded signing | Docusign

Let me know if you need further assistance.

 

Best regards,

Melanie | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Hello ​@ValeCodo,

 

I trust all is well. If you found my response to be a useful solution to your question, could you please click the "Best Answer ✅" button at the bottom of the post? It helps other community members who might have similar questions.

 

Best regards,

Melanie | Docusign Community Moderator

"Select as Best" below if you find the answer a valid solution to your issue.

Code of ConductAccessibility statement

Docusign Community

Code of Conduct