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...
20430
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
all I keep seeing online are apologies as to how you can’t make them stop, despite requests specifically to do so - it’s annoying and WE PAY for this service - you should listen to your customers
Right now this is the only formatting.It would be nice to allow for the transparent background of the text and the ability to make the background of the text another color. Right now it looks like this:
We want to create a template with word document and the sender text tags will have values varying from 10 to 50 characters, so we tried using Agreement Template Builder but Approve and Decline buttons are not available. If we use classic editor, we can have Approve and Decline buttons, but the content is the word document is static. If the word document content is static and in the sender text tags is having less characters, empty space is visible and when the characters are more, text is overlapping on the content.
Problem:CLM Attribute groups display all fields regardless of relevance, creating clutter and increasing user error.Proposed Solution:Enable rule-based visibility (e.g., IF Field A = “Yes” THEN show Field B).
Problem:Currently, auto-renewal CLM attribute in contracts is not represented as a dedicated boolean attribute in the XML/data model (for example in xml output of step find document). Instead, it is implicitly derived from related fields such as auto_renewal_count and auto_renewal_unit. This creates challenges when building workflows or performing change detection, as users must implement custom logic to infer whether auto-renewal is enabled or disabled.Proposed Solution:Introduce a dedicated boolean attribute (e.g., autoRenewalFlag) in the CLM data model and XML output:true → auto-renewal is enabled false → auto-renewal is not enabled
ProblemIn the current CLM design, the Auto Renewal Term Count field:Only accepts positive integers (1, 2, 3, etc.) Cannot be set to 0 Cannot be cleared (set back to blank) once populated via the Edit CLM Agreement Attributes workflow step The same limitation applies to Auto Renewal Term Unit and auto renewal yes/noThis creates friction when agreements need to:Remove auto-renewal behavior Transition from renewable → non-renewable contracts Correct data entry mistakes via workflow automation
I have about 3000 documents all needed to be signed by the same person and have inserted signed date. All documents are identical conserning the location of the signature and the date. As of now all the documents have to be signes individually. I am looking for a “sign once, apply to all” function
Hello, I would like a way for a signatory to make a single signature, automatically replicating that same action across multiple envelopes for mass mailings. At our institution, directors sign many documents, which ends up taking up a lot of their time. Currently, we have about 477 documents to sign. Replication would make our daily work easier. Would this improvement be possible?
Today, Access Codes are set per recipient, which gets painful when an envelope has multiple recipients (repetitive setup, easy to miss someone, hard to manage).Request:Add an envelope-level option: “Require access code for this envelope” → automatically applies to all recipients. Add an option to send the access code in a separate DocuSign system email, so it’s not included in the envelope invitation/email thread (helps when invitations get forwarded).This would reduce admin effort, improve consistency, and strengthen real-world security.
I want to be able to create custom text fields (addresses of property’s) so that they can be selected as required into a Sender pre-fill text box. Currently this is not possible under the Sender Prefill “user” as far as I can see. I can only create them under my own name. If this is possible I would be delighted to hear how to do this. If not, DocuSign developers can you get this implemented asap. Thanks Richard
Problem:We currently work with six banks, each having its own MPA PDF format. Additionally, we have 200+ partners whose MPAs follow the same structure and mapping, but each partner requires different header and footer branding. Because of this variability, adding static headers and footers in the source Word file is not feasible. Maintaining over 200 partner–bank combinations as separate documents is not scalable and would be extremely difficult to manage in real time. Previously, we only had five banks and four partners (20 combinations), which was manageable. Now, with a significantly larger set, we require the ability to insert header/footer images dynamically—similar to how we already populate text using text tabs.Our configuration:We are using DocuSign Envelope Templates in a partially customized setup. Envelope creation is triggered via ApexToolkit because some related objects are not directly connected to Salesforce Contract records.Idea:We need the capability to dynamically insert header and footer images into the document at runtime through the API, similar to the way dynamic text tabs or signature tabs are currently supported.





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