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...
23940
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
Colors for each recipient should be FAR different in color than they are. Would be great to be able to choose colors.
I need the option of sending out an agreement for partial signature, as we were able to do in Lexion. Reason is sometimes each Party takes care of their own e-signature, but as soon as an enveloppe is completed in DocuSign it adds the agreement as completed and adds it in the repository, although it’s only partially signed. It’s then very complicated to delete the partially signed copy from the Completed (repository) and replacing it with the fully executed version.Another option would be to add a “replace” option in the completed document in DocuSign. That option also existed in Lexion.
would it be possible to have the signing certificate document to be spelled / translated to the users language setting.so when we receive the (SUMMARY.PDF), if my language is set to french, it would show « SOMMAIRE.PDF »
Flexible Visibility of Envelope Custom Fields (ECFs) DocuSign allows Envelope Custom Fields (ECFs) to be used as unique identifiers, such as contract IDs or purchase order (PO) numbers, in envelope email subjects. For high-volume document processing and large campaigns, Bulk Send with CSV uploads is an efficient way to manage envelopes using these identifiers.However, to use an ECF in this process, it must be visible to envelope creators at the account level, even when it is only required for background processing. This can confuse senders and unnecessarily expose technical fields in their workflow.Proposed enhancement Allow ECFs to remain functional while hidden from envelope creators, with more granular visibility controls.Ideally, administrators should be able to:Use hidden ECFs in Bulk Send CSV uploads and envelope email subjects. Configure visibility at the Template or Group level, rather than only account-wide. Control ECF visibility independently of its availability for processing.Suggested implementation priority 1. Initial enhancement: Allow hidden ECFs to be populated through Bulk Send and used in email subjects.2. Further enhancement: Introduce Template- or Group-level visibility settings for greater flexibility across business processes.This improvement would simplify the sender experience, reduce unnecessary training, and enable more flexible automation and identification workflows without exposing irrelevant technical fields to users.BRFrantisek
I would like to remove the expiration in the envelopes.
Topaz branded signature pads with a 4x3 aspect ratio is not supported by Docusign, even though they state they support Topaz.When I opened a ticket, it was explained to me that “the 4x3 signature pads were not available when the feature was initially developed”It was the Mid 2000s when the 4x3 signature pads were developed, so it’s long overdue for engineering to add this functionality.
Description:We need a report that lists every contract uploaded to DocuSign IAM today (or in the last 24 hours).Issue:The Created Date filter in Agreements only takes fixed dates or a date range. It has no relative option like "Today" or "Last 24 hours," so we have to enter dates by hand every time. That also means we can't save the report or schedule it.Request:Is there already a way to report on contracts created today or in the last 24 hours, either in Agreements or in Insights reports? If not, please add relative date options (Today / Last 24 hours / Last N days) to the Created Date filter, and let us save and schedule the report.
Explanation:When a recipient role, such as Customer Signer 1, is used more than once in a DocuSign template, the recipient’s name and email should automatically carry forward to subsequent occurrences of that same role, including when the recipient appears within a conditional routing path.Currently, when Customer Signer 1 appears outside conditional routing, the name and email entered by the user can be reused. I would like this same behavior to apply when Customer Signer 1 appears again within a conditional routing group.Expected behavior:If the sender manually enters the name and email for Customer Signer 1 when sending an envelope through the DocuSign web application, any subsequent occurrence of Customer Signer 1 in the template should automatically use the same name and email, regardless of whether that occurrence is part of standard routing or conditional routing.





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.