Skip to main content
Solved

Embedded signing client userid for Docusign webapp

  • January 22, 2025
  • 3 replies
  • 66 views

neethujkp
Troubleshooter
Forum|alt.badge.img+10

When defining an embedded signer, we need to provide a clientUserId along with the recipient's name and email. The clientUserId is a sender-defined identifier for the embedded recipient, enabling the generation of a signing URL for them. How can this be accomplished when envelope is initiated using the DocuSign web app and recipient should sign using embedded signing in a custom built mobile app

Best answer by mrave

@neethujkp 

No, embedded signing can only be initiated via API and not via the (standard) Docusign Web App. The clientUserId needs to be specified by the application that is also redirecting the user to sign the document.

That having said, you can correct an envelope created by the Docusign Web App to change it to embedded signing by adding the clientUserId for a recipient. In that case the initial recipient will always receive an email, but you could use an internal email address as a placeholder and also remove/update that recipient while correcting the envelope.

View Original
Is this content helpful?

3 replies

Forum|alt.badge.img+6
  • Docusign Employee
  • 60 replies
  • January 23, 2025

Hello ​@neethujkp,

I believe in this case you can use the Hybrid Signing session, where you can use the DocuSign UI, email notification but also create an embedded session. You can check how to do that here:

https://www.docusign.com/blog/developers/the-trenches-hybrid-captiveremote-signing-embeddedrecipientstarturl

 

Thanks!

 


neethujkp
Troubleshooter
Forum|alt.badge.img+10
  • Author
  • Troubleshooter
  • 80 replies
  • January 23, 2025

Hi Eduardo

Thanks for your reply. But when I am initiating an envelope from Docusign web app interface (standalone) where can I specify the client userid?


Michael.Rave
Docusign Employee
Forum|alt.badge.img+14
  • Docusign Employee
  • 929 replies
  • Answer
  • January 23, 2025

@neethujkp 

No, embedded signing can only be initiated via API and not via the (standard) Docusign Web App. The clientUserId needs to be specified by the application that is also redirecting the user to sign the document.

That having said, you can correct an envelope created by the Docusign Web App to change it to embedded signing by adding the clientUserId for a recipient. In that case the initial recipient will always receive an email, but you could use an internal email address as a placeholder and also remove/update that recipient while correcting the envelope.