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

Curious about creating a smooth, in-app signing experience with Docusign? We recently hosted an async Ask Me Anything (AMA) with ​@paige.rossi, Lead Developer Advocate at Docusign, where developers submitted their questions on embedding eSignature using the Docusign API.

Below is a recap of the top questions and their answers.

What’s the difference between embedded signing and embedded sending?

Answer: These two terms sound similar but serve different purposes in your Docusign integration.

  • Embedded signing lets signers complete documents within your app or website, instead of navigating away to check their email. It’s all about making the signing experience faster and smoother for your users.

  • Embedded sending, on the other hand, is for the senders. It allows you to embed the Docusign sending experience into your own app or portal, so users can create and send envelopes without going to Docusign.com.

Why does this matter?
By embedding either (or both), you streamline the agreement workflow—no need to switch tools, open email, or log into Docusign separately. It’s a better user experience that can boost completion rates and reduce friction.

Can I use embedded signing with a Signing Group via the API?

Answer: No, embedded signing isn’t supported for Signing Groups. That’s because embedded signing requires your app to authenticate each signer, and you need to know exactly who the signer is before they sign. For Signing Groups, you’ll want to use remote signing instead.

How do I support multiple signers in a specific order (e.g., client signs, then manager)?

Answer: That’s called sequential routing, and yes, it’s supported! You can use Advanced Recipient Routing and even set up conditional logic. If you want the signers to sign in-app (embedded), be sure to:

  • Assign a clientUserId to each signer

  • Use the EnvelopeViews: createRecipient endpoint to generate their unique signing URL

🔗 Check out this how-to guide with sample code.

Should I use embedded signing or just embed the envelope in an iframe?

Answer: Avoid iframes. While tempting, they introduce security risks and can cause unexpected issues—like the scrollbar problems some developers have experienced.

Instead, try using:

  • Docusign JS with

  • Focused View for an embedded, styled experience that feels native

You can use the StyleObject properties to control how it looks and behaves in your app.

🔗 Read this guide for more on iframe risks 

When should I use embedded signing vs. a link or the Docusign site?

Answer: It depends on the user experience you want:

  • Use remote signing if the signer doesn't need to stay in your app or if you require features like identity verification or advanced compliance.

  • Use embedded signing to keep users in your app and streamline the signing flow.

  • Use focused view for a fully embedded, cleaner visual experience—but note that some features (like identity verification) aren’t available with it.

Still unsure? Consider your workflow priorities: simplicity, automation, security, or branding.

Can embedded recipients use their saved signature and stamp from their Docusign account?

Answer: No. Embedded (or “captive”) recipients aren’t linked to a Docusign account during signing, so they won’t have access to stored signature styles or stamps. If this is important, remote signing is a better fit.

Can I use wildcards in the frameAncestors property to support multiple subdomains?

Answer: Not currently. Due to strict CSP (Content Security Policy) requirements, wildcards like *.mydomain.com aren’t supported. You’ll need to list each domain individually. That said, our product team has logged this feedback.

👋 Have more questions or want to learn more?

Have a question you want answered? Comment below or start a new post in the Developer Forum.

If you want to dive deeper into this topic, here are a few helpful resources to check out: 


 

Be the first to reply!
Code of Conduct

Docusign Community

Code of Conduct