Skip to main content
Question

Embedded Url - User might not have an account

  • January 13, 2025
  • 1 reply
  • 36 views

Forum|alt.badge.img+1

We are currently implementing a DocuSign Esignature integration. Our application is multi-tenanted.  What is the best way to handle users who need to sign a document via an embedded URL without logging in. My understanding is that the user would need to log into DocuSign to generate the URL or have a embed url sent via API by a sender account. Is there a way to avoid this requirement?

Some of our user will not have a DocuSign account and would not be willing to sign up. Is there another way to get the URL with minimum user interaction?

Our ideal scenario would be that the user logs into our application, selects from a list of envelopes, and signs the document via a embed URL. The user should not have to login to docuSign. 

1 reply

JohnSantos
Valued Contributor
Forum|alt.badge.img+18
  • Valued Contributor
  • 967 replies
  • January 13, 2025

@NGWestmeath 

Yes—your application can (and should) generate and provide an embedded signing URL directly to the signer without requiring them to log in to DocuSign.

This is accomplished via DocuSign’s “embedded signing” (or “captive recipient”) flow. The signer only needs to be authenticated to your app and never sees a DocuSign login screen.

Because your system is multi-tenanted, you can maintain a single “sender” or “service” account to handle envelope creation on behalf of your users/tenants.

Your backend needs an access token to call DocuSign’s APIs. Most production integrations use OAuth JWT grants for a headless, system-to-system flow, so you don’t have to constantly re-authenticate a user.

When you create the envelope or add recipients, mark them as “embedded” recipients by including a clientUserId property.

Embedded signing doesn’t require signers to have a DocuSign account. They just click the link and sign.