Recently active topics

We have been using DocuSign for a few months now.  It is helping us streamline an approval process with invoicing.  Recently, the “Download” option has disappeared when viewing the document (it only allows one to ‘share’).  If you download all of the Documents, the file names change and I waste time renaming them.  Same for the emailed copies, the file name tends to add ‘.pdf’ to certain files even though they were already PDFs.   Thank you for your consideration!

I have some questions about how sender-hosted In Person Signing works and what records it produces.In the PDF of a completed envelope, the document metadata shows a creation date/time and a modification date/time (Producer: PDFKit.NET). Which DocuSign events do these two timestamps correspond to, for example envelope creation or sending for the first, and completion/sealing for the second? In a sender-hosted In Person Signing session, which steps must be completed between the moment the envelope is sent and the moment it is completed: acceptance of the Electronic Record and Signature Disclosure (if enabled), display of the documents, adoption of a signature, completion of each signature field, Finish, the optional signer e-mail prompt, and the host registering the session as complete? Does DocuSign require a minimum time or a scroll-through of the documents before the signature fields can be completed? For an in-person signer, what does the Certificate of Completion record: the host's

Hello folks! Just sharing a quick recap of our latest Finserv Club event on 7th October 2026.We had 11 client attendees from leading financial services organisations. The session explored how financial services organisations can:Understand the value & ROI of AI & automated agreement workflows Build knowledge around Intelligent Agreement Management (IAM) and agentic capabilities Deep dive into financial services use cases such as loan agreements, customer onboarding and contract review use cases, and specifically Docusign IAM + agents can support these use cases.We took the opportunity to introduce the new Finserv Forum, a community for financial services customers to share questions, challenges and practical insights. Harj Mattu, Partner at Deloitte gave a great presentation on the value and ROI of AI for financial services customers, and fielded lots of great questions from the group during the roundtable discussions.We also ran a three-part demo with our Principal Solutions C

Since early October 2026, embedded signing with focused view fails on our demo account. The signer sees "This content is blocked. Contact the site owner to fix the issue." inside the focused-view iframe. The browser console shows:Framing 'https://demo.docusign.net:7802/' violates the following Content Security Policy directive: "frame-src 'self' https://docucdn-a.akamaihd.net/ https://apps-d.docusign.com https://demo.docusign.net ..."Nothing changed on our side: the same code that worked in September fails now, and displayFormat: "default" still works with the same envelopes, so the integration key, recipient view request and frame settings are valid.What we foundWe reproduced it with plain HTTP requests, outside our app and outside any browser. docusign.js (0.0.61, widget @embedded/signing-ui 1.0.221) appends platform=focused to the recipient view URL. With that parameter, the redirect chain ends like this:demo.docusign.net/Signing/MTRedeem/v1/... → account-d.docusign.com/managed_toke

I’m sure other people have asked about this, but I’m not finding it.  The past couple of weeks there was a button on the bottom of our screens to switch back from new navigation view to the classic view. That button is now gone. We work out of the “Inbox” folder 100% of the time and now it is no longer there. We need to see everything that is coming in. Stuff that is now complete and stuff that needs to be signed. Once done with them we move to other folders. Some times we log incoming items that need to be signed but they are move to a side folder where they pend until I get the all clear to complete/sign them.  Not being able to view these separately is causing extreme issues with our productivity. HELP!!!

I noticed that Docusign recently changed the options for how agreements can be displayed. There is no longer a sent option. Does anyone know if there is a way to change it back? Once a document is completed, I have further action outside of Docusign that I need to take, so by having my completed documents all show up in the Completed list display once they are done, I have to now keep a list to track which Completed ones I have processed. When everything showed up in my Sent display, I could move the completed documents to a folder and know they were fully complete. Any ideas?

The new user interface is terrible, I am a real estate broker and need to review legal documents for accuracy while placing signature and initial fields. At 125% document zoom, the fixed recipient/Fields panel and fixed document-navigation panel consume so much horizontal space that the contract is not readable. Reducing document zoom defeats the purpose: at 35%, interface elements such as the recipient's name are several times larger than the contract text.The right-column navigation bar needs to be collapsable, and the Name and Date panel (on the left), need to be shrunk - significantly - to allow users to read the legal contracts they’re working on.

Does anyone know if we can go back to the old view in esignature Agreements.  The new view takes up to much space causing me to scroll to see everything.  I have multiple folders on the left that I file completed envelopes in, I send documents for 10 different companies.  With the update I can’t see the folders without constantly having to scroll and then click the Show More.

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 am customising Subject when creating envelope using C# SDK. But the Email receive by Signer is below one. Kindly help on this 

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 need to contact the support because the signing process of one of my files does not work. When I try to access the support chat here, nothing happens when pressing the button. There is also no html behind the button I could copy to another browser. It’s not working in Chrome (incognito & normal mode), Firefox, Safari  I also can not access any other type of support since I’m not a paying member. I also can’t log in to the support page, because first I’d need to open a chat - which is not working. 

Hello, I often need to place my initials on every page in large documents. These documents are often scans of original documents. Is there a way to automate placement of initials on all pages?  Thanks,J

Hi everyone,I’m integrating DocuSign with a C# application. Before sending an envelope, I want to validate the recipient’s email address.Currently, I can perform basic format validation, for example checking whether the email has a valid format such as user@company.com.However, I would like to know if there is a recommended way in the DocuSign API/SDK to determine whether the recipient email address actually exists and is deliverable before sending the envelope.For example: Can DocuSign validate whether the mailbox actually exists? Is there an API or recommended approach to check email deliverability before creating/sending the envelope? If the email is invalid or undeliverable, can I detect this before the envelope is sent? Any guidance on the recommended approach would be appreciated.Thanks!

Hello, We are using embedded signing with the Focused View (DocuSign.js) for a captive recipient (ClientUserId is set) whose recipient definition includes phone-based Identity Verification (RecipientIdentityVerification with a phone_number_list input option). This works correctly in our demo/sandbox environment, but fails in production. In production the Focused View iframe never renders the document, because the identity-verification step attempts to frame https://eu.verify.docusign.net/ and it is blocked by the Content Security Policy served on apps.docusign.com. Browser console error: Framing 'https://eu.verify.docusign.net/' violates the following Content Security Policy directive: "frame-src 'self' https://docucdn-a.akamaihd.net/ https://apps.docusign.com https://na.verify.docusign.net https://eu.docusign.net ... https://verify-d.docusign.net https://verify.docusign.net ...". The request has been blocked. Key point: the frame-src allowlist in that CSP includes https://na.verify.do

Shared Envelopes is a useful feature to share envelopes among a team, and necessary to our workflow. We regularly need to share access to envelopes that are in process.Shared Access requires us to give full access to our accounts to others. This is not useful. I see Shared Envelopes as a legacy feature, but I am not able to activate it. Please reactivate this feature.We have also looked as Workspaces. This does not allow team members to correct envelopes, which is critical to our workflow.