Unanswered questions

I’m currently on the business standard plan but need to send a 1 time bulk envelope to about 70 recipients.  Recipients are in a .csv file.Is there a way to do this without having to upgrade my entire plan for this one time?

My template is a word doc uploaded.  Then I add the text boxes and fitted them into the table - they look correct.  Some have a conditional field associated with them. However, when the template arrives with the recipent, the boxes over lap?  I have set the fixed width option but that doesn’t seem to make a difference. What am I doing wrong?

WE have installed the Docusign Sharepoint Site Edition to a test Sharepoint site. When we try to connect this to the developer docusign admin portal via "Manage Docusign Administration Settings" in the SharePoint document library, it goes to the production link (https://account.docusign.com/oauth/….) not https://account-d.docusign.com/ which is the developer docusign portal. With this how can we grant consent a docusign developer environment to a sharepoint site? 

Hello DocuSign Support,We have a production Power Automate flow using the DocuSign connector that had been working correctly for approximately 30 days and suddenly stopped working today.The issue occurs specifically with the DocuSign Production connector.Symptoms:Existing DocuSign connection in Power Automate shows Connected. The Create envelope (V2) action times out after multiple retries. The Account ID dropdown in Power Automate returns"No items". I tried switching/re-authenticating the existing DocuSign connection, but the issue persists. I also tried creating a completely new DocuSign Production connection. Power Automate returns:"Connection test failed. Please review your configuration and try again." I can successfully log in to the DocuSign Production web portal and access the Tata Communications account. In DocuSign Connected Apps, Microsoft Flow and Power Apps is present. Most importantly, the DocuSign Demo connector works successfully, while the DocuSign Production connector

I sent an envelop using a template. In the template i had a wrong email. I had corrected the email in the template, resend the envelope, When i check history i stiil see the old email. How do i correct it. One or two recipients had signed the document

We recently switched from DFS to DAL and noticed the “Copy” button within the Agreement tab does not seem to create a Docusign Status record within Salesforce.With DFS: When used the “Copy” button within Docusign portal, a Docusign Status record was created linking it to the parent object from where the original agreement was sent.With DAL: No Docusign Status record is created within Salesforce.

Hi, when I go to Admin page and try to go to Billing, the site keeps crashing.I tried this in different browser (Chrome, FireFox, and Safari). Happened to all three. Cleared cache, but same result.Any help would be much appreciated 

Hello,I have an active DocuSign account under my full legal name. I can edit and save my signature in my profile successfully.However, when I receive documents to sign, DocuSign continues to use a previous signature/initials instead of the updated signature. This is occurring across multiple envelopes from the same sender and on multiple devices.Could you please check whether there is a signer profile, cached signature, or recipient setting associated with my account that is causing old signature data to be reused? 

I have an enterprise application which has documents. I need to initiate the signing to my superior to get the signature. The signature should be digitally cerified by eMudhra. What are the step I need to take and explain more about it. I came to know June 2026, Docusign collaborated with eMudhra. 

I’m new to doing Docusign automations. I built a template matching functionality that will recognise a specific invoice layout when I upload it into a new envelope, it automatically applies the template. Working well. However i need this to take the attachments from emails, not folders. So I figured out our docusign email address and sent some documents that were successfully ingested. I can’t find any way though to select these from the Agreements page / completed documents section and initiate a new envelope with these attached, or if I go and manually start a new envelope there are no options to attach ingested documents. How do i achieve this please?

I am currently attempting to sign documents within the Teams portal via Approvals and when I open the document to sign, the document refuses to load and throws the error apps.docusign.com refused to connect. I have seen that another user had a similar problem with ticket number SIGUX-8631. It also gives a similar in the front end logs “Framing 'https://apps.docusign.com/' violates the following Content Security Policy directive: "frame-ancestors 'self' https://approvals.teams.microsoft.com". The request has been blocked.”

We have isolated a recipient email-delivery issue in our DocuSign Demo account.Manual envelopes created in the DocuSign UI deliver recipient invitation emails successfully, but envelopes created through the eSignature REST API do not, even when sent to the exact same recipient from the same Demo account.API-created envelope:Status: sent deliveryMethod: email Standard remote signer No clientUserId No embedded-signing configuration No email-suppression flags Envelope History shows Sent Invitations No bounce, rejection, or autoresponded status Envelope appears normally in DocuSign and can be signed successfully Recipient invitation email never arrivesControl tests:Manual envelope from the same Demo account to the same Yahoo recipient delivered immediately. Separate manual envelope to Gmail also delivered immediately.Controlled comparison:We have specific envelope IDs available for both the failed API-created envelope and the successful manually created envelope, but I have omitted them fr

Using the Android Mobile SDK (com.docusign:androidsdk:2.1.7) to launchcaptive/embedded signing from a pre-generated signing URL (obtainedserver-side via the eSignature REST API's EnvelopeViews: createRecipient),not via SDK-driven OAuth login — our app's signers don't have their ownDocuSign accounts.Setup:  DocuSign.init(context, integratorKey, DSMode.DEBUG)  // integratorKey is a real, valid Integration Key from Apps and KeysCall:  DocuSign.getInstance().getSigningDelegate()    .launchCaptiveSigning(activity, signingUrl, envelopeId, listener)DocuSign.init() succeeds with no error. But launchCaptiveSigning() alwaysfails before the signing UI ever appears, with:  com.docusign.androidsdk.exceptions.DSAuthenticationException:  DSAuthUser data is nullFull stack trace shows the failure originates inside the SDK's ownenvelope fetch:  E DocuSign_Auth: DSAuthUser is null  E DocuSign_EnvelopeRepository: Error while fetching the envelope    com.docusign.androidsdk.exceptions.DSAuthenticationExcep

I’m hoping someone can point me in the right direction. I haven’t been able to find a direct phone number or another clear way to connect with someone at DocuSign to discuss our account needs.Our company currently has multiple individual DocuSign accounts, and we are looking to explore consolidating them under one company-wide tenant or enterprise account.I’d like to connect with someone who can walk us through the available options, account structure, licensing, and what would be involved in transitioning our existing accounts.If there is a specific team or representative I should contact, I’d appreciate someone reaching out or pointing me in the right direction.Thank you!

Has anyone else recently experienced DocuSign reporting an email address as undeliverable and prompting you to correct it, even though the address is already correct? I've encountered this at least three times in the past week. In each case, the email address was verified, and at least one recipient was still able to access the envelope. I'm curious whether others are seeing the same behavior or if there is a known issue with email delivery notifications.The recipient's email provider is not blocking emails from DocuSign because I also have the same domain and I receive Docusign emails just fine. 

Summary-------When a signing session is embedded with docusign.js, the "Electronic Record andSignature Disclosure" dialog's Print button does nothing. Download in the samedialog works. The browser blocks the print call because the iframe that rendersthe signing document is sandboxed without allow-modals.Environment------------ docusign.js v0.0.61 (js.docusign.com/bundle.js and js-d.docusign.com/bundle.js)- Embedded wrapper: @embedded/signing-ui 1.0.208- Classic view and displayFormat: "focused" both affected- Chrome 152 on macOS (also reproduced on Chromium 147)- Reproduced on demo; the identical iframe sandbox attribute ships in the production bundle, so production is affected tooSteps to reproduce------------------1. Create an envelope with an embedded signer (clientUserId set).2. Create a recipient view with frameAncestors/messageOrigins for the host page.3. Mount it: DocuSign.loadDocuSign(apiKey).then(ds =>   ds.signing({ url }).mount('#container')).4. In the consent dialog, cli

Hi DocuSign team, I am connecting the DocuSign MCP server from Cursor (demo environment) for Drew White & Co. Issue: unauthenticated requests to the MCP endpoint return HTTP 403 with body “RBAC: access denied” and no WWW-Authenticate header. MCP clients that follow the auth spec need HTTP 401 plus a WWW-Authenticate challenge to start OAuth. Because of the bare 403, Cursor never reaches the OAuth consent flow, so our Integration Key and Secret are never used. Repro (demo):POST https://mcp-d.docusign.com/mcpResponse: 403, body: RBAC: access denied, no WWW-Authenticate Related discovery issue: https://account-d.docusign.com/.well-known/oauth-authorization-server does not return OAuth authorization-server JSON (redirects to HTML login). Account: Drew White & Co. (developer/demo)Integration Key (DWC Servicing): b788aaf7-6b83-45b5-8255-0640d273736fAccount Base URI: https://demo.docusign.netContact email: **PII removed** Request: please update the MCP gateway so unauthenticated reque

Hi all,On our developer sandbox account, notification emails for one envelope were never delivered to either recipient. Both recipients have since confirmed directly that nothing arrived — inbox, spam and promotions all checked. Two manual resends produced nothing either. The envelope was eventually completed, but only because we reached the signers outside DocuSign; no notification email ever arrived for it.Setup: eSignature REST API, JWT Grant, demo environment (demo.docusign.net), two signers at the same routing order, both ordinary emailed signers.The audit trail records the invitations as sent, and records no bounce. Neither recipient ever moved to autoresponded, and neither carries an autoRespondedReason:  23:22:23Z  Registered        Envelope created  23:22:25Z  Sent Invitations  invitation to recipient 1  23:22:25Z  Sent Invitations  invitation to recipient 2  23:34:32Z  Resent            resent to recipient 1  23:35:12Z  Resent            resent to recipient 1A comparable enve

I am not able to receive the offer letter sent by docusign. When it was first sent, due to email id typo it did not get delivered to me. Now even after correcting the mail ,i am not able to receive, what can be the reason.?

I am creating a new Template for an Envelope. Under “Add Recipients”, it has automatically added the signer section with Name and Email but it has also added a line for Role - how do I remove the Role?  

I built a workflow to save a completed document to a specific SharePoint library.  It does not work.  Support tells me that a “small number” of customers are impacted and this feature does not work for them.  What I see using MS Graph is that Docusign’s connection method to the designated SharePoint library fails (with credentials that should work).  I have a stalled ticket open about this.  This save-to-SharePoint was a major selling point for us, and now it does not even work. What’s the point of this option if it does not work? 

Greetings - long time lurker, first time poster :)I’m writing some apex that creates / sends an envelope from an Opportunity, and it’s my understanding that I need to convert an Attachment SObject to a ContentVersion object in order to add it to the envelope.  I’ve created a method that looks like it should work, however when I try to send the envelope I get dfsle.ValidationException: The envelope is invalid.File type is unsupported.Here’s my code snippet:List<dfsle.Document> docList = new List<dfsle.Document>{};ContentVersion cVersion = new ContentVersion();Attachment attach = [ SELECT Id, Name, Body, ContentType, OwnerId, ParentId FROM Attachment WHERE Id =: attachmentId LIMIT 1];if(attach != null){ cVersion.ContentLocation = 'S'; //S-Document is in Salesforce cVersion.PathOnClient = attach.Name; //File name with extention cVersion.Origin = 'H'; //C-Content Origin. H-Chatter Origin. cVersion.OwnerId = attach.OwnerId; //Owner of the file

I am converting code from the legacy authentication to OAuth and using the new DocuSignClient in .net.  I am able to get the Access Token, but when I call the CreateEnvelope, it returns Misused header name, 'Authorization'.My code (in VB.NET)            Dim docuSignClient = New DocuSignClient("https://demo.docusign.net/restapi")            docuSignClient.Configuration.AddDefaultHeader("Authorization", "Bearer " & accessToken)            Dim envelopesApi = New EnvelopesApi(docuSignClient)            Dim envelopeDefinition = GetEnvelopeDefinition()            Dim results = envelopesApi.CreateEnvelope(clientID, envelopeDefinition)  

I was newbie and just want to explore my bussiness 

When selecting the country code +212 during authentication, the system offers either Morocco or Western Sahara as options.However, selecting Western Sahara is highly problematic because it is an extremely sensitive issue.Docusign states that it cannot remove this option: has anyone else encountered this problem and know how to ensure that only Morocco—and not Western Sahara—is displayed when using the 212 country code?Regards,