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
Solved
Embedded signing client userid for Docusign webapp
Best answer by Michael.Rave
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.
Sign up
Already have an account? Login
You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.
Customer Login/Registration Developer Login/RegistrationDocusign Community
You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.
Customer Login/Registration Developer Login/RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Back to Docusign.com


