Embedded Signing

I created an app to prove the Docusign JS embedded signing with Focused View.  I am using C# at the server and JS/jQuery at the client.  I followed all of the steps in the article “How to request a signature using focused view” (https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view).Everything on the server side is fine, but when the JS code runs to load the document for signing, I get the following permission errors:Refused to frame 'https://apps-d.docusign.com/' because it violates the following Content Security Policy directive: "default-src 'self' https://js-d.docusign.com/". Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback. Refused to connect to 'http://localhost:49618/05e7fec…/browserLinkSignalR/…ationData.browserId&browserId=b7e3-320d&clientProtocol=1.3&_=1728595245739' because it violates the following Content Security Policy directive: "default-src 'self 'https://js-d.docusign.com/". Note that

Hello,I am hosting multiple apps that require signing, so I created a dedicated app that uses the DocuSign JS library to provide a focused view signing interface. This app is designed to be accessed via an iframe by my other apps. But it keeps giving this error: Refused to frame 'https://apps-d.docusign.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors https://localhost:4209"The signing app is hosted at https://localhost:4209, while the other apps are hosted on ports 4201 and 4206. The signing app works perfectly when accessed directly from the browser at https://localhost:4209, but it fails to load when embedded in an iframe within the apps hosted on ports 4201 and 4206.I have added all the required domains in the request. Here’s the C# code of the request for generating the urlvar recipientViewRequest = new RecipientViewRequest { ReturnUrl = request.ReturnUrl, ClientUserId = "1234",

Hi, I’m wondering that can I modify the “Message from {xxx}” using API or website?I knew that there is email-subject and email-content can be modified in template setting, but I want to show business partners’ name on the “agree-to-use-eSignature” page

We require embedded signing functionality within a customer portal mobile application. The signer will log in to the mobile app and complete the signing process through an embedded signing experience using an iframe. Is it feasible to implement IDV Liveness for signer identification within this iframe?

Hello DocuSign Community,  My teammate and I are participating in the DocuSign  "Unlocked" Hackathon, and we’re working on a project to enhance the signing process by introducing interactive document features. Specifically, we are trying to add the ability to:1. Highlight specific sections or lines in a document to draw users’ attention to key details. 2. Display contextual bullet points or notes alongside the document to provide additional guidance or explanations. We’re exploring how to best integrate these features into the signing flow using embedded signing. At this point, we’d love some guidance on:- Whether embedded signing is the right approach for implementing such dynamic features.  - Any tips, tools, or APIs within DocuSign that could simplify this process.  If you’ve worked on enhancing the signing experience or have insights on building customizations like this, your advice would be greatly appreciated!Thank you for your time and help!

Hello everyone,Im not really used to docusign, i work in a project where there is some screen with a docusign iframe, and recently there is a new popup modal that appear in the modal (it didnt before) that i dont want to show, any idea how to avoir it please ? English trad of the popup : check and continueHello, please consult a new document converning ...   

Unlike with EnvelopeViews:createRecipient, which has options to configure clickjacking protections via x-frame-options or csp frame-ancestors, there are no such options for the createSender view.Due to this when displaying the sender view within an iframe element the browser blocks the request.How can we add Clickjacking protection to the embedded sender view to avoid this and add security.Here’s an example of the error on Firefox: 

In my application i am using iFrame to display the docusign embedded view.i am able to complete the sign and read the event and perform operations and navigations in my app successfully in local environment. But the issue is when this is tested in production environment, I am able to sign and redirect url is being called giving 200 response but nothing is happening after that.  same code is working fine with local environment and failing in production environment. I am not understanding is it because of any configuration issue or what.The difference I could see in the network requests is below request is failing. I don’t know exactly this is the problem. PFA belowI am using react router Route to handle the docusign url redirection like below<Routepath={urls.docusignComplete}component={() => <CustomDocusignCallback />}/> In the CustomDocusignCallback component, i am handling the event and calling backend api to update the document status and after that navigating back to

Hello,I’ve been trying all weekend but I just cannot get this to work, so hopefully the experts here and guide me through what I’m missing.  I’ve tried a number of combinations and nothing is working.  What I want to do, is create an In Person Signing event, where the delivery driver (under the host account) signed the document saying he has delivered the shipment, and then passes the device to the customer for them to sign their portion.  In a mockup, I got it to work but I can’t get it to work in a full run through with an embedded signing request with the PHP SDK.Heres what I got:$document = new DocuSign\eSign\Model\Document( [ 'document_base64' => base64_encode($file_content_in_bytes), 'name' => 'TestFile', 'file_extension' => 'pdf', 'document_id' => '1' ] ); //Find Driver Area $deliverySignature = new DocuSign\eSign\Model\SignHere( [ 'anchor_string' => 'Signatu

When the user clicks on the finish button after signing the document, I want to show a pop up message while staying on the page. Is it possible to do? 

We have built an integration with DocuSign, which essentially shares the envelope with the signer via our (Zingly’s) application.This is good, because it keeps the engagement between sales and service reps and their customers in the workspace. Having said that, in addition to the signer (customer) being notified that they can review and complete signing via Zingly, we would like to ensure the signer continues to get their “An envelope has been shared with you to review and sign” email from DocuSign.HOWEVER -- it appears that with DocuSign integrations (such as embedded signing), the integrations SUPPRESS all but the “completed signing” emails. (See link: https://support.docusign.com/s/articles/Why-aren-t-my-signers-receiving-DocuSign-Notification-emails?language=en_US)Can someone confirm whether embedded / integrations CAN or CAN NOT allow DocuSign’s native email / sms notifications to the signers to continue, in addition to the embedded integration? 

Hello,I have integrated the Docusign signature for my customer orders via the Focused view mode.However, I encounter 2 problematic issues:1. The buttons are not translated into french even though the default language of my account is set to french. Via the JS setting, we can only change the last button but all the others and the start popup are in english. Is it possible to choose the language somewhere?2. The zoom on the documents by default does not suit me.It is too high and I do not know how it is calculated.Is it possible to adjust it in one way or another?Thanking you in advance for your answers,Regards,Flav

We are successfully using the embedded view “default” style to allow our users to sign documents, and then proceed onto the next step. However, we do allow the user to refresh the page and get back into the “signing step”, and that works well, except if it has already been signed. When the document is signed, and the page is refreshed, we successfully show the document again, and this time instead of “Sign” or “Finish”, Docusign UX displays “Close”. When that “Close” is pressed, the “endSession” event isn’t triggered as normal, but the nested iFrame is destroyed. This workflow does works well with the “focused” style in all cases (meaning that by just changing “displayFormat” to “focused” it fixes the issue), however, we would like to use the “default” UX. How could we have “endSession” trigger when pressing “Close” on an already signed document?

If we have already have a envelopeId and we want to show the documents for signing in our single page app, do we have to communicate with DocuSign’s API?

Hi Team,  I’ m integrating docusign Embedded Signing in React js Application.   I create below component : import React, {useEffect} from 'react';import PropTypes from 'prop-types';function DocumentSignUI({integrationKey, docUrl}) { useEffect(() => { const loadDocuSign = async () => { const docusign = await window.DocuSign.loadDocuSign(integrationKey); const url = `${docUrl}&output=embed`; const signing = docusign.signing({ url, displayFormat: 'focused', style: { /** High-level variables that mirror our existing branding APIs. Reusing the branding name here for familiarity. */ branding: { primaryButton: { /** Background color of primary button */ backgroundColor: '#333', /** Text color of primary button */ color: '#fff',

Dear Community, I am looking for a solution to an issue that we ran into recently while creating elastic templates.We created the elastic template following the documentation from Docusign, however, once we tried to create conditional rules, we noticed that we cannot drag and the document field into rule builder as shown in the video/gif in the documentation: Conditional Content (docusign.com)I have attached a GIF of the issue that we are experiencing. Is this a bug or are we doing something wrong?Best Regards,Shahir 

Hello,We’ve just updated to the Embedded Signing flow. When loading up a document the embedded loader is appearing on the left of the screen. However, there is no way to modify this. Is there something we can pass or is there a bug with our container? Bellow are the screenshots and source code //running in the console$('div[data-qa="embedded-document-loading"]').style.width='100%';//updates the loader to show as centeredApplication Code://TSconst signingConfiguration = { url: this.url, //url from service displayFormat: 'default', style: { signingNavigationButton: { finishText: 'Submit', position: 'bottom-right' } }};try { const docusign = await DocuSign.loadDocuSign(clientId); const signing = docusign.signing(signingConfiguration); /** Event handlers **/ signing.on('ready', (_event) => { console.log('UI is rendered'); }); signing.on('sessionEnd', (event) => { console.log('sessionEnd', event); i

Hey there, currently I’m integrating the bundle.js to my application to sign an agreement. I’m using a dialog to present this document, this dialog can be closed or opened (everytime that I open this dialog I’m loading again the DocuSign client and requesting the document url to load the embed view),I was looking for a way to clean the event listeners of the signing but I can’t find any information about it. I’m using React, there’s any way to remove the listeners associated when unmount the docusign embed document?

Hello,I am trying to implement the Focused view for embedded signing in my application. While I can complete the signing process in one shot, there are cases where I would like to reload the iFrame, i.e., call DocuSign.signing again with the same URL and resume my session as it was. Is this possible?Currently, when I try to reload the iFrame, I see a loading page and a document with the URL chrome-error://chromewebdata/ instead of https://demo.docusign.net/Signing/?insession=1&ti=<id>. I also see the console error :Refused to frame 'return_url' because it violates the following Content Security Policy directive: "frame-src 'self' https://docucdn-a.akamaihd.net/ https://apps-d.docusign.com https://demo.docusign.net https://account-d.docusign.com https://proof-d.docusign.net https://identity-d.docusign.net https://azure-demo.docusign.com https://content.googleapis.com https://docs.google.com https://players.brightcove.net https://www.youtube.com https://accounts.google.com http

We are using an iframe to embed a PowerForm for signing envelopes on an app using React js. I wanted to ask if there is a way to handle errors (if any) and loading events outside of the iframe.What I have tried:<iframe ... onError={(e) => { console.log({ e }); }} onLoadStart={(e) => { console.log({ e }); }} .../> 

Environment: ASP.NET Core MVCProblem Description: I am experiencing an issue with the DocuSignJS integration on my website. The specific error I am encountering is a Permissions Policy violation, which is causing the document iframe to load indefinitely. However, the DocuSign footer is still visible.Full Error Message: [Violation] Permissions policy violation: Geolocation access has been blocked because of a permissions policy applied to the current document.Additional Information:I am using the focused view mode. I have tried adding allow="geolocation" to the first iframe by modifying the bundle.js file where the iframe element is created (the second iframe is controlled by the DocuSign script). I have also set up my geolocation header, but nothing seems to resolve the issue.Steps Taken:Added allow="geolocation" to the first iframe. Configured geolocation headers.Despite these steps, the iframe continues to load indefinitely.Any assistance or suggestions on how to resolve this issue w

I want create a embedded signing link, and when user click the link.he will fill the name and email.So can I create a signing link without name and email of signer?

As per subject, I would need a way to have Embedded Signers receiving the Completed e-mail when all signers completes the envelopes. My integration is within an Online Account Opening application and I have a possible scenario with a mixed combination of Embedded Signers (the main owner of the account being opened) and additional Remote Signers (the joint owners of that account).With this scenario the joint owners could complete the envelopes days after the main one completed the embedded signing procedure but only the Joint owners would receive the e-mail notification.I understand e-mail notification is off by default for embedded signers and that can make sense when a single signer is needed for a given envelope… but when multiple signers are involved, especially if mixed like in my case, this default behaviour sounds more like a Defect rather than a desired behaviour. I know I have the possibility to use the “embeddedRecipientStartURL” parameter with "SIGN_AT_DOCUSIGN" to set main o

Hello Everyone, I’m trying to do Embedded Signing. I’m facing an issue while integrating DocuSign with our angular Api using focusView it is giving Violation Error like [violation] permission policy violation: “Geolocation access has been blocked because of permission policy applied to the current document”

Hello,We are in the process of integrating an integrated signature flow on our website via your API, and we have some questions.Our project is to allow our customers to sign their contract on our website, without leaving it. They fill out a form that we manage and process in PHP, and when they click on the " signing my contract" button, it should generate a contract from a template that we have set up in our DocuSign account, pre-fill the fields with the elements of our form, and allow the customer to sign their contract, while remaining on our site. If successful, or if there is an error, the customer is redirected to different confirmation pages, still on our site.Our customers do not have a Docusign account and should not be asked to authenticate themselves.From this point on, we wonder about the following point:We have consulted the documentation but we are not sure which type of authentication is suitable for our project: Authorization Code Grant or JWT? The JWT seems to