Unanswered questions

Has anyone else had people complain about email subject lines coming from your Docusign account with this as the Subject line?Do you recognize this document?My clients are pushing back, not signing, and slowing down the legal approval process.  They fear that it is spam, even when being sent by Docusign.Then, when the document is signed and sent back to myself for signature it has the same Subject line.  It is like Docusign itself is sending emails that feel like Phishing emails to end users and customers alike.

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

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?

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? 

Hi :)I have a document in my template which, when sending the envelope, I used to replace with an updated version using the ‘Replace’ option, but that option has disappeared. Is there a way to get it back?Here it is missing:But here I can still see it: Thank you for any help :)

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)  

No matter how well I line up my fields when preparing an envelope, they are ALWAYS out of alignment post signing. What am I doing wrong? This makes my signed documents look terribly untidy, no matter how much I try.Example here where the fields are perfectly aligned and centred within each section of the document. However, the final result has them both unaligned on the left-hand side, and also out of alignment with my document. 

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, 

I am implementing DocuSign with Salesforce for a customer.  We will use DocuSign on the Contract object in Salesforce.  I would like to be able to create custom object that would have a lookup to Contract so that I could dynamically add as many signers as I want to this child custom object.   I would add a Contract lookup onto this custom object.  I wanted to use the ‘Related Lists’ feature when I am on the ‘Add Recipient’ screen when setting up my template.   But it seems like that only supports a very limited number of related objects… Salesforce / DocuSign Apps launcher - I need to add a recipient from a related list of a Custom Object in Document Envelope template. | CommunityIs there a best way to do this dynamically?  The client really does not know the maximum number of potential signers for a given Contract/Envelope.  I do not want to have to add 20-30 lookup fields to Contact on the Contract object.Is there a best practice way to do this?  I am very comfortable with Flows/Apex

I need to share a template with my team , so that we can all use the same template. I have saved it to Share Folders, but it only shows for me and not other team members. When I select the template and select share with other users, it fails  Any ideas would be really helpfulThanks 

Hello,I need assistance with my free DocuSign account.I use the account only to upload a document, sign it myself, and download the signed document. I do not send documents to other people for signing.I have already signed two documents, but when I try to sign a third document, I receive the following error:ENVELOPE_SEND_ERRORThe error appears after I click the “Sign document” button on the Home page, upload the file, and click “Sign.” The error then appears and I am unable to proceed any further.DocuSign states that the free version does not have a limit on the number of documents that can be signed.I would be very grateful for your assistance in resolving this issue.

Hello, when I send a document to be signed the original text starts to fade. After sending a few times for signatures you can hardly read the original text. Signatures seem fine but the original text is almost not legible. Any ideas on how to fix this. Thank you

Hello,I am using the Doc Gen step within my workflow to generate a document based on initial form data.The issue I'm facing is related to data coming from a table in the initial form (multiple entries/rows). When I use the “TableRow Select” or “Repeat Select” tags in my Word template to display this data in a table, only the last row of data entered in the form is showing in the generated document. The previous rows are being overwritten.For example, if I enter 2 lines of data in the form's table, the generated document only displays the second line.This is the initial form:I tried both ways:Later, in the WF, the message I get in the Doc Gen step: And the result is:How can I ensure that the tags properly iterates over ALL rows of my input table data and dynamically creates a new table row for each entry in the generated document, instead of just showing the last one?Any guidance would be greatly appreciated. Thanks!!

Is there a way to remove or disable certain options in the signer’s “Other Actions” menu for a specific document or template? We wan to remove Decline to Sign, Assign to someone Else, and Print & Sign, while keeping Finish Later available.Can these options be controlled at the document or template level? I’m a sender, not an account administrator.