How to Use the Ideas Feature
What you need to know about Docusign Community IdeasThis guide will walk you through the process of sharing your ideas, voting on existing ideas, and...
23980
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
Hello DocuSign Community,We’ve observed a limitation in the DocuSign platform regarding sensitivity labels applied to DOCX files. While DocuSign successfully retains labels for PDF files throughout the signing process, DOCX file labels are lost if the DOCX is used as starting input in an eSignature workflow. 📌 Feature RequestWe request that DocuSign enhance its platform to preserve the sensitivity label of a DOCX file when it is used to initiate an eSignature workflow. This would align DOCX handling with current PDF behavior and support compliance with corporate information protection policies. 🔍 Current BehaviorPDF files retain their sensitivity labels after signing. DOCX file labels are lost if the DOCX is used as starting input in an eSignature workflow. Signed documents are final and non-editable, including their labels. ✅ Why This MattersSupports compliance with corporate and legal standards. Reduces manual intervention and risk of sensitivity label loss. Enhances document traceability and security. Aligns DOCX workflows with existing PDF capabilities.I invite feedback from other users and the DocuSign product team. If this feature would benefit your organization, please upvote or share your use case to help prioritize its development.Thank you for your attention and support!
Hello,I currently use the “Bulk Send Process” for sending compensation plans. The details we upload via the Bulk send are:Name Employee ID Bonus Target LocationThe idea that I have stems from my current use and how to do things faster. I have 4 different templates in Docusign as the “hard coded” wording on the PDF is different for different roles (rep 1 plan vs rep 2 plan vs mgr plan vs mgr 2 plan vs sales VP) despite the upload details being conceptually the same across each template(name, employee ID bonus target & Location). My “idea” is that in these situations you could be able to perform a bulk upload across multiple templates. Maybe on the bulk upload I just have to list the template associated with each person. This would allow me to do 1 bulk upload as opposed to 5.
Please add a feature to allow users to further restrict “Share Access” based on conditions such time of documents sent/received or type of envelops. I understand that users can restrict permission to “Send”, “Edit” or “Manage” but these permission apply to all envelops/documents with no restriction.At the moment if user “A” share access with user “B”, the entire history of user A documents will be shared. If user A is going on a holiday for a week or two and is using “Share Access” to let his/her colleague follow up matters in his/her absent, user B should not be able to have access to all user A’s document, because some of those might be personal/private. It would be great that user A has freedom to choose what type of documents user B should have access during his/her absence, or even how far back user B can see documents via this feature.
I’d like to share a concern regarding email deliverability. Many users who rely on spam filters are reporting that DocuSign emails are being flagged with unusually high spam scores. This could lead to important messages being missed or delayed.It would be great if the email configuration could be reviewed to ensure best practices are followed and spam scores are minimized.Thanks for considering this feedback, and please let me know if there's a more appropriate place to submit it.
Hey there!My idea comes from a problem I have with the reporting. Currently, we use DocuSign’s “Bulk Send” process to send documents internally that contain individualized details to each sales rep (ex: Employee ID, Bonus Target, etc.). We also currently track who has / has not approved their envelopes using DocuSign’s reporting. My issue is that I want to expand off the current reporting options to include the individualized details that we uploaded via the bulk send process.
When a Docusign Gen template with multiple documents is used, all documents are selected by default. This makes it very time-consuming for users to deselect all the documents not needed. As document rules are very limited in terms of only fields of the record can be selected and also only the conditions "equals" and "Not equals" can be used, this would make life much easier and would safe a lot of time for our users.
When creating a DocuSign Envelope on the Legacy version, the PDF files, Notes & Attachments automatically get connected to the DocuSign record (dsfs__DocuSign_Status__c). This does not happen for the new DocuSign Status (dfsle__EnvelopeStatus__c). Can we have the old feature applied on the new feature?Old feature: New feature:
Hello Ideas team,We advice all of our customer migrate to new send view as this document told:https://www.docusign.com/blog/developers/esignature-rest-api-embedded-correct-view-updated?msockid=13eac2ad5d496fc10dc3d62c5c416ee9and also can find the document:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createsender/we find the setting as below:{ "returnUrl": "<url>", // URL required "viewAccess": "envelope", // required "settings": { "startingScreen": "Prepare", // (default) or "Tagger" "sendButtonAction": "send", // (default), "redirect" "showBackButton": "true", // (default), "false" "backButtonAction": "previousPage", // (default), "redirect" "showHeaderActions": "true", // (default), "false" "showDiscardAction": "true", // (default), "false" "lockToken": token_value, "recipientSettings": { "showEditRecipients": "true", // (default), "false" "showContactsList": "true" // (default), "false" }, "documentSettings": { "showEditDocuments": "true", // (def,ault), "false" "showEditDocumentVisibility": "true" // (default), "false" "showEditPages": "true", // (default), "false" }, "taggerSettings": { "paletteSections": "default", // (default), "none", "custom" "paletteDefault": "custom" // "merge", "notary", "seals", // "smartContracts", "annotations", // "smartSections" } } }}Now the customer want disable the send later button. maybe can a parameter like showSendLaterButton, default is true, and can change it to false. so the send later button can hide. becuase they embedded this view in their system, the workflow is control by their system, so no need send later. Now some people may make a mistake, and the process can't go down, stop, and have to modify and increase the workload. thanksFreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024📊 DocuSign Community Leaderboard Top 5 contributor🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/
I receive notifications when someone views a document, but not when they have actually signed.Given the name of the app, DocuSIGN, this seems to be a giant oversight.Please can we have a notification where someone SIGNS.This has been covered elsewhere in the community, but seems to be ignored.Thank you!
We have a big problem with e-Signature APIs. They do NOT report error properly in a RESTful manner. We should NEVER have silent failures where the HTTP status response code states a happy 200 status, but the response body contains an error message. This is an anti-pattern, as we should never be forced to introspect a response body to look for errors and throw our own exceptions. We should be catching these as errors as either 4xx or 5xxx series errors.The renowned Martin Fowler provides a nice Reader’s Digest condensed version of Richardson’s Maturity Model.From https://martinfowler.com/articles/richardsonMaturityModel.html#level2“There is another difference if something goes wrong, such as someone else booking the session.HTTP/1.1 409 Conflict[various headers]The important part of this response is the use of an HTTP response code to indicate something has gone wrong. In this case a 409 seems a good choice to indicate that someone else has already updated the resource in an incompatible way. Rather than using a return code of 200 but including an error response, at level 2 we explicitly use some kind of error response like this. It's up to the protocol designer to decide what codes to use, but there should be a non-2xx response if an error crops up. Level 2 introduces using HTTP verbs and HTTP response codes.”
Hi,For QA purposes the signing order of recipients for my documents usually doesn’t matter. However, when docusign automatically reorders my recipients without my knowledge or consent, it confuses me because i am usually referencing an ordered list. when the names are put out of order, it is more difficult for me to verify that i added all the needed recipients. let me change the order to what i want it to, then toggle off set signing order, but preserve the order i set just for my own view.
When using a Template that contains the Attachment field, a user creates a document for esignature and uploads any kind of document to the attachment field. However, when the user then "Assign to Someone Else" the attachments that were uploaded do not carry over to the other user.There does not seem to be an option to “Collaborate” with the Attachments field.The end result would be that any attachments the first user uploads carry over and remain attached, so the second user can see them and does not have to re-attach.
I recently got asked how to setup the Date Signed field in an Ordinal Date format (e.g. 16th day of July in the year 2025).Right now, there isn’t a way to do this - I think it would require the Date Signed to be broken up into its three parts: Day (and correct ordinal - “1st”, “2nd”, “3rd”, “th”), Month, and Year.Is there any discussion of creating a Date Signed field that will allow this?
It would be highly beneficial for the Agreement Template Builder (ATB) to retain the original formatting of uploaded documents, similar to how the classic editor functions. Many of these documents follow a specific house style, and preserving formatting is essential for consistency and professionalism.Currently, the ATB struggles to maintain original formatting, which results in additional time and effort for users to manually correct layout and style issues. Enhancing this functionality would significantly improve user experience and efficiency when creating agreement templates.
We have 2 docusign accounts. One for real estate sales and the other for our property management company. We have the same notification preferences set for both accounts. The sales account ALWAYS send us an email when any signer first views their envelope. The property management account has NEVER sent us an email when a signer first views an envelope. After multiple back and forth troubleshooting sessions with support they cannot figure out why and suggested that we make an enhancement suggestion here. So that is what we are doing even though this is already a feature in DocuSign that works on one account and has never worked on our other account. Has anyone else experienced this type of issue?





Docusign Community
Code of ConductAlready have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.