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
17980
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
In our Case it would be suitable that Admin could grand normal users the right to create Sets (IAM Navigator) without giving them further contract manager permissions.Solution should be similar to eSignature functionality, where as an example normal users can be allowed to do mass sendings (a tick-box where you can either activate or deativate for user profiles)
Currently as part of the Docusign Apps Launcher package we do get the expiry date field on Docusign status object which is calculated while sending an envelope out for signature based on an end user input for Reminder and Expiration setting.After the envelope is sent, any updates to the reminder and expiration date value made from within the Docusign Account on the envelope, does not allow for these data point to sync back into Salesforce, creating an inconsistent reporting for our Business partners to track document out for signature.The Docusign Connect for Salesforce (webhook) also does not expose these parameters as Docusign Fields for us to map back to the Docusign Status object.
The addition of a Dark/Night Mode feature would improve visual comfort in low-light environments, reduce eye strain during extended use, and match user preferences for a more pleasant and accessible interface experience.
User icons are currently showing up in very ugly/mangled fashion in emails to recipients from dse@docusign.net. Branding looks fine, but recently updated user icons are cut with a circular frame. if the image is a square, the square still shows, but the corners are messed up, because they’re outside of the (unwanted) circle. Since this looks so ugly in emails to recipients, users need the ability to at least delete the existing user icon so that they have none at all, since recipients would then not know what they’re missing. Reference case #15939853
Hello DocuSign Team,In our organization, we use groups with custody transfer enabled so that envelopes automatically route to the appropriate user account within our shared-access setup. This allows large teams to work from a centralized “shared inbox,” which has been extremely beneficial.However, we have working managers who also operate within these groups. While their standard envelopes should auto‑route to the shared inbox, they occasionally need to send confidential documents directly to individual users. Currently, because custody transfer applies universally, those confidential envelopes are also routed to the shared inbox—creating privacy challenges.Feature RequestWe would greatly benefit from an option for senders to choose whether an envelope is PRIVATE (no custody transfer; remains with the sender) or PUBLIC (follows existing custody-transfer routing). This simple sender-level toggle would allow us to maintain the efficiency of shared inbox workflows while also protecting confidential communications.This added flexibility would significantly improve how our organization utilizes DocuSign.Thank you for your time and consideration.Sincerely,Brandy BacaReimbursement Systems Specialist
Hi, it would be important to have the ability to place headers in the top corner of all document pages and automatically apply them.
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.
It would be helpful if senders to received a notification when recipient signs a document, not just when they view it
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.





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.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK