Help Forums

Hello,We setup a Docusign app on dev and followed all the steps mentioned in granting administrative consent for JWT Grant Flow. When we migrated our app to Prod, firstly, we don’t see the Organizations Tab that we see on Docusign dev and I get this error when I am trying to get an access token from Docusign.error 400 while reaching https://account.docusign.com/oauth/token: {"error":"consent_required"}I am not sure how to move forward from here because our setup works on Docusign Dev but doesn’t work after going live.

A welcome modal displaies the ERSD content and any messages from the sender, before entering the agreement. This window provides no added value for our customers; on the contrary, it leads to numerous queries and unsigned documents.I request an option to disable/remove this window via the administration.

Hi Team, Today we found docusign iframe was not loaded, it even worked yesterday, no changes applied in our side.When I opened the signing URL  in the browser, which starts with “https://demo.docusign.net/signing/mtredeem/v1”.I cannot find our domain in “content-security-policy” response header, and confirm our domain has been added into the FrameAncestors whie calling CreateRecipientView API. Is their any update for demo site? Thanks,Fei

Doing spreadsheets this year for 2024 taxes, and there it is...again. $325.00 charge from DOCUSIGN. I haven’t used Docusign in over 3 years and downgraded both my account years ago to free versions. There is NO help in cancelling an account. The entire process is circular and frustrating, meaning the end-user keeps ending up at the same place with error codes (when trying to login) and non-functional webpages.I’ve requested Docusign to cancel my account previously. Nothing. No messages, and no notifications. I’m not even being notified of annual billing by email. There’s no receipts or invoices. Users are being charged with ZERO recourse.When I log into my account it says “FREEMIUM” as the version and yet I’m still being charged.I’ve even changed my debit card information, and somehow DOCUSIGN is still getting around this and charging. This is downright criminal and grounds for a class-action lawsuit.

Hi DocuSign Community!I'm experiencing an issue with displaying base64-encoded images in HTML templates used for embedded signing via the eSignature API.I'm using HTML templates with <img> tags that contain base64-encoded images in the src attribute (using data: URLs). The images display perfectly when viewing the HTML in a standard web browser, but they disappear when the document is embedded using the DocuSignJS SDK for signing.Technical Details:API Used: DocuSign eSignature API with embedded signingSDK: DocuSignJS SDK (https://js.docusign.com/bundle.js)Image Format: Base64-encoded images using data:image/[format];base64,[data] syntaxImplementation: HTML templates with embedded <img> tags Are there any known limitations or specific requirements for displaying base64-encoded images in HTML templates when using embedd

I have updated several existing templates and need to know what happens to the in progress envelopes that were created using these templates before they were updated. Is there a way to go into the in progress envelope and update to the newer template? I have tried using “Manage Applied Templates” but it does not update to the new version. Any help is appreciated.

When a Recipient needs to sign with two witnesses and one of those witnesses needs to be corrected, it does not allow you to just correct the one witness, unless 1 of the witnesses has already signed. It automatically changes the second witness to the same as the first witness. Is this a glitch?

I have a customer who is looking to validate payment information (credit cards mostly) during the Docusign process. They want to use a payment gateway, such as Stripe, to collect payment information. However, they want to verify that the payment information is valid. They often incur bounced payments from incorrect information when they collect this manually. Do we know if the payment gateways are validating the payment information when we collect it? The documentation doesn't explicitly say this, so they want to confirm if this is happening or not. Any help would be appreciated, thanks!

Hi ,How can i get a copy of the Certificate of completion

Hi TeamI updated the resource file to disable downloads during signing:<data name="DocuSign_SigningAllowDownload">false</data>This hides the Download option as expected during Review/Signing, but it also hides it for Completed Documents. I want the Download button hidden while signing and visible once the document is completed.I tried enabling it for completed documents with:<data name="DocuSignComplete_AllowDownload">true</data>However, the Download option is still not visible on completed documents.Could you please help on this.

My organization wants to lower the complexity of collecting signatures for a specific form. This form is challenging because we have 3 dynamic parties and initially only party B knows both A and C  A: My organizationB: 3rd party intermediary   C: Customer. The issue is that A currently has to send the template to B but initially only B knows the name and contact information for C. Currently what we’re doing is A initiates the form sending to B and having B use the “Correct Envelope” or “Bulk” process to fill in the information for C. This process happens several hundred times for each party B and is labor intensive for B.  Staff has requested that I setup a PowerForms and host a link on our site so C can initia

I have a strange misalignment of signer records when I am setting up one signer as a host and another signer as an inPersonSigner using API.  The result of a setup is the signerName is used along side of a host email when it is showing “Hosted By” and also in one of the flow dialogs when it is saying that “Name1, pass control of the session to Name1”, where Name1 is the inPersonSigner signerName. I am submitting clientUserId for both host and inperson signer, otherwise I could not match the inPerson signer while generating a RecipientView. I see that it aligns the names correctly if I remove clientUserId from inPersonSigner record, but it breaks the mapping for RecipientView. Is there any possible work around for this?

I’m creating a DocuSign Template and in the custom email sent to the signer I want to include the senders job title. Ideally I could have a variable/command in the template that would pull the job title from their DocuSign account and place it in the message. My research into this seems to indicate this isn’t possible without either setting up a field where the staff member needs to type their title every time or setting up an API. This change would affect hundreds of our templates, so I just wanted to confirm this was the case before I select a path.  Could I please get a recommendation on the best path forward?

We use DocuSign for processing B2B credit applications. A common scenario we encounter is that an administrator at a customer’s company fills out the credit application form (sent via a Powerform linked to our credit application template), but afterward, they need to send it to an executive for signature.Much to their frustration, they discover that they cannot delegate the envelope to someone else once the form has been filled out. This limitation creates friction in our workflow and causes confusion for our customers.Having the ability to delegate an envelope after the form is completed would be a significant improvement for our business use case.

Is there a way to tell which administrative user created an agreement rule in our eSignature account? Also, if a user creates an agreement rule, but we close that user’s profile when they leave the organization, does this affect any existing, enabled agreement rules they may have created?

In a previous data ingestion effort by my former team, we integrated account data from another system into Salesforce. As part of this process, we established a mapping between Salesforce Accounts and DocuSign CLM Accounts using a naming convention that combines the account Name and ID. (not same as salesforce account Id but another field)However, we’ve encountered a problem: although the migrated account folders follow the correct naming convention, they are not being linked to the corresponding existing Salesforce Accounts. Instead, new Salesforce Accounts are being created, resulting in data inconsistency.Expected Behavior:Migrated DocuSign CLM account folders that match the existing naming convention should be mapped to the corresponding Salesforce Account.Actual Behavior:Despite matching names and IDs, new Salesforce Accounts are being created instead of linkin

I have configured a brand for Signing. But unable to see it the header and footer in the signing document. I am able to see it in emails and forms however.

I need for my clients to be able to receive my contracts so they can sIGN them and return them through Docusign. I can’t get the scanned contracts to them without my initials and signature in the place they are supposed to sign? I need help setting it up please? I need to set up a new account strictly for my clients?

I am planning on taking the test for the Certified DocuSign eSignature Administrator in a month or so.Are there any other resources aside from the toolkit that have sample questions I can practice?

How do I add my middle name to signature?

Hello everyone,I’ve got some questions regarding the export of events, generated by employees to a company’s SIEM. As a security team’s representative, I’m interested in enhancing the monitoring and security of this system in my company, so I want to know if it’s possible to export this events to SIEM systemOur company has eSignature Business Pro Edition Plan and I have read the DocuSign has a Docusign Monitor, which can detect potential threats and it also has a pre-built alerts and SIEM integration capabilities, but unfortunately our plan doesn’t have this DocuSign Monitor. Are there any other ways to export the event logs to our SIEM system? Thanks everyone in advance.

​Hello,​I am trying to achieve a specific email notification workflow with the eSignature REST API, but I'm running into an issue.​My Goal:​I have an envelope with one embedded signer (clientUserId) and several CC recipients (carbonCopies). My desiredworkflow is:​The CC recipients should receive NO email when the envelope is sent.​After the embedded signer completes the signing, both the embedded signer and all CC recipients should receive the final "Completed" notification email.​What I've Tried:​I have tried two approaches, but both have failed:​Attempt 1: Using routingOrderI set routingOrder: 1 for the signer and routingOrder: 2 for the carbonCopies.​Result: The CC recipients still receive an email immediately when the envelope is sent. This email contains a "live view" link to the in-process document.​Attempt 2: Using suppressEmailsI kept routingOrder: 2 for the CCs a

Imagine a scenario where I send an envelope to several recipients containing some documents (let's call this the "first batch"). Later, I send a new document inside this same envelope. If any recipient hasn't completed signing the documents in the first batch, the new document is sent to them as usual. They receive an email notification, and upon opening it, they can view both the documents from the first batch and the new one. However, another recipient who had already completed all the pending signatures for the documents in the first batch isn't sent this second notification with the new file. I'm developing this functionality in PHP with the eSignatureAPI + e-sign client sdk.I'd like to know if it's possible to create this functionality. And if so, how can I do it?

In web forms I would like to inbed a URL in a description in a field. 

I’ve been using Power Automate to send/track agreements sent by our legal team for about a year. Sending an envelope inserts a record into our MSSQL database, and the tracker PA updates the row when an envelope status changes.The contracts team recently reached out and wants to start recording the reasons that envelopes are being voided/declines. Previously I was just tracking if they were or not, but added a new column to the SQL table for ‘reason’. Capturing the reason for future envelopes has already been implemented, but I have ~350 voided envelopes I would like to retroactively access the ‘void reason’ for. I have all the envelope IDs that I need, but is there an API endpoint that I can call to get the void/declined reason? If I have to make two PAs (one for void, the other for decline, as the JSON packages are slightly different), that’s fine. I just haven’t found anything that works so far. Thank you!