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...
23070
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
Love the Idea of the Mark-up Tool but needs a few advancements.Line option - make available for recipients also (put the option under the comments option.) Move the Mark-up option (while in recipients hands) from the [Other Actions] button to under Add Comments icon. Currently if recipient adds Mark-up to document, next signer cannot visually see what was covered. Within the document, wherever there was a Mark-up added: add an Icon to the left of that Mark-up and add a feature where the next signer can click on that icon and the mark-up will briefly disappear. This will allow all parties to view the original language. While other parties can edit other people’s mark-ups, you can delete all, change and revise, however, you can only change or revise within the size of the original mark-up’s box size. Allow this to be resized. Require all signers to initial mark-up. Any Changes to mark-up, needs to be rerouted to all who have not seen. (similar to the collaborative option of text fields) Allow any user to reject just the Mark-up...or allow it to be deleted from another signer Allow SENDER to change mark-up formatting if they want, particularly Font Color.
Currently, custom field types in Docusign are fixed, which limits how workflows can be set up for reporting and notifications. I'd like to propose two new field types:1. Lookup fieldAllow admins to import a reference list (e.g., via CSV) containing a code and description — similar to a lookup table. Users would select a code from this list when filling in the field, and both the code and description would be available for use in reports and Insights.Use case: Cost center codes, project codes, department codes, etc., where the value needs to map to a standardized, centrally maintained list rather than free text.2. User List fieldAllow a field to reference a Docusign user or an email address (e.g., "Budget Holder"), selected from a list rather than typed manually.Use case: Assigning a budget holder, approver, or responsible party to an agreement, so that this person can be automatically notified — for example, via Insights or reporting — when a related event occurs (expiry, renewal, threshold reached, etc.).
ID verification fails due to special signs in name. Customers are being denied because ID verification fails despite name being correct.ID verification provider changes values and because of that customer needs to identify multiple times.All 3 examples failed because of the first name being misspelled.
The messages in the Agreement Desk requests shows the previous emails trail for every new message, which makes it cumbersome. The new message only should appear.
With greater than 50 + templates to administer and update, I locating and updating a subset of templates is time consuming. Having a easy way to filter templates by folders available on the template page would help me easily locate templates. A template report is available for on all templates by date created. I compare the report with ones that were updated. Also adding a search filter by templates updated greater than would also be helpful. As the number of templates grow, the slower the page loads when you choose 50 templates. Lastly, i am only able to upload one template at a time, does anyone know if there is a way to upload several templates at the same time?
In IAM Agreement Desk, when a request is already opened, and I receive a new email to my work email (not into the Request), I need to be able to forward it into DocuSign (which will create a new request) and then merge this new request into the old one. This is how I was doing it in Lexion, we had a “merge” option. It’s a really important feature because a lot of emails are being sent outside of the request, and it’s the only way to keep a trace of it.
Hi DocuSign Team,We recently received feedback from one of our recipients regarding the experience when viewing a document sent as a copy-only recipient.The recipient opened the document for review but did not complete any fields, apply a signature, or take any action other than viewing the document. Upon closing the document, they were presented with a confirmation message indicating that the "Agreement signed." This understandably caused confusion, as no signing activity had taken place.To improve clarity and the overall recipient experience, we would like to suggest that when a recipient has view-only permissions or simply reviews a document without signing, the closing confirmation message be updated to something more appropriate, such as:"Thank you for viewing this document.""Document review completed.""You have successfully viewed the document."Providing a clear distinction between viewing and signing actions would help avoid misunderstandings and offer greater reassurance to recipients, particularly advisers, legal representatives, and other parties who receive agreements for information purposes only.Overall, we have found DocuSign to be an excellent platform, and we believe this small enhancement could further improve the user experience and reduce recipient confusion.Thank you for considering this feedback. We appreciate your continued efforts to enhance the platform.Kind regards,Chepyala BapurajuSenior Application Support EngineerApex Group Ltd.
At this time, admins must review two different reports to see authentication used for legacy and modern authentication. It would be more efficient to have a single report showing all envelopes sent and the authentication method used in the envelope. The two reports are the Envelope Authentication Report and the Application Identity Verification Report.We are limited by Salesforce integration having only legacy authentication available through Nintex, so we have to monitor both reports. We are also limited by the 24hour skip authentication setting only being available for legacy authentication methods, so we have our wire teams on legacy so that we don’t stop production in a time sensitive business function. Our ideal state would be to use only modern authentication, but we need proper reporting to monitor all authentication methods in use.





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