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.
Add a new configuration to the ‘Signing Settings’ page to address the security flaw of being able to forward envelope email notifications to someone else. Forwarding the email allows this person to sign on behalf of the intended signer. Existing setting: “Prevent users from forwarding completed envelopes”New setting: “Prevent users from forwarding envelopes’ If this forwarding allowance is a requirement of being able to delegate another signer, perhaps they should be tied together:Existing setting: “Allow recipients to change signing responsibility” New setting: “Allow recipients to change signing responsibility and forward envelopes” - leaving this blank would produce an error if the user tried to open a forwarded envelope. The solutions I’ve read for this to ‘simply add ID verification’ is not a viable solution because this cannot be enforced at the global account level. There’s too much responsibility on the sender and we’re not ready to retrain the entire organization to always add Access Codes.
There should be an option to set whether or not the context for fields in the document appears for the recipient. In other words, I would like to be able to set in the properties of a field that the context for this field does not appear (context that specifies whether the field is optional or mandatory).
I was told in a case that there is no ability to download/upload PowerForms from demo to prod. You have to download the template from demo, upload it in prod, then recreate the PowerForm in PROD.This needs to have the ability to download the powerform. Anytime you have to manually build in prod you can have mistakes. We need the capability to download/upload PowerForms.
It would help based on the volume of documents we have to be able to sort the documents alphabetically.
Hello,We are using Docusign integration with our Document Management System. We noticed that signer can add any metadata field instead of Signature field and then Finish button thus allowing to complete signing task.We had conversation with Docusign support via this ticket CaseDetail but support didn’t offer something useful.
When checkbox is checked in Docusign, it becomes ✅ and show as X after signing, and this X is not easy to understand, and we hope it will continue to ✅ be displayed FreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🏆 2024 APAC Reseller Growth Partner of the Year🔧 The first in APAC to pass the DocuSign eSignature Technical Consultant certification.🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries.Feel free to reach out for collaboration opportunities.
Checkbox and RadioGroup fields show "X" instead of checkmark or filled circle in final signed PDF
When recipients select Checkbox or Radio Button fields, the completed/signed PDF displays an “X” as the selection indicator.In many business and compliance scenarios, a tick mark (✓) is the expected standard and looks more professional. An “X” can sometimes cause confusion or appear as a rejection.Request:Please add an option at the account or envelope level to choose the selection style (✓ or X) for completed PDFs.This would improve clarity and better align with common form standards.
I have a field that needs to have a % at the end. On a template, I can make a field number that has a $ at the beginning, but not one that has a % at the end. I saw some documentation using doc gen to make that happen, but we don't have doc gen. Would you please incorporate the functionality that doc gen has into template fields for this.Thank you
Product AreaseSignature / API / ConnectProblemHigh-volume senders (e.g., >1,000 envelopes/day) frequently face “recipient didn’t receive email.” Today we must open Support cases to confirm whether the recipient’s mail server returned SMTP 250 (accepted). This creates a compliance loop (customer consent), long MTTR, and heavy manual workload (~1% delivery exceptions already strain teams). Delays impact our customers’ business and increase complaint risk.Proposal Envelope History: Email Delivery pane Show per-recipient metadata only: accepted (Y/N), smtpCode (e.g., 250), masked smtpMessage snippet, acceptedAt timestamp masked mxHost, tls (Y/N), retryCount, bounceCategory (soft/hard/other) Controls: admin-toggle, configurable retention (30–90 days), CSV export. Default OFF to respect privacy by default. This gives frontline users immediate, self-serve evidence for “accepted by recipient server vs. blocked/quarantined later.” Connect: Deliverability events Add webhooks to enable automation: EmailDeliveryAccepted (fire when recipient MX returns 250) EmailDeliveryFailed (fire when explicit rejection or retries exhaust) Payload includes minimal, masked metadata (e.g., smtpCode, timestamp, hashed MX) so customers can trigger automatic fallbacks (e.g., SMS notification, re-send from alternate channel, or internal admin review) without opening Support cases. Security & Compliance Metadata-only (no email content or PII beyond standard recipient identifiers). Feature is opt-in (admin-controlled) and fully audited (access and events). Data minimization: masked MX/message details; configurable, short retention. Behavior is backward-compatible: when disabled, nothing new is exposed. Acceptance Criteria (examples) When the recipient server returns 250, Envelope History shows accepted=true with timestamp; if enabled, an EmailDeliveryAccepted event is emitted. When delivery is rejected or retries exhaust, UI shows non-250 details (masked) and an EmailDeliveryFailed event is emitted. CSV export reflects exactly the on-screen metadata fields. With the feature disabled, neither UI elements nor events appear. Impact / PriorityP1. Dramatically reduces Support cases and MTTR, removes compliance friction, enables at-scale automation for exception handling, and protects customer NPS as send volumes grow. This solution focuses on what operators need most: clear, self-serve deliverability evidence inside the envelope and machine-readable webhooks to close the loop automatically. FreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🌟The only DocuSign Partner globally with two Certified eSignature Technical Consultants🏆 DocuSign 2025 APAC Growth Engine 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📬 For business inquiries, feel free to connect via :WeChat/微信: +86 1381880287WhatsApp: +65 97796938
I would like to submit a suggestion for improvement regarding envelope notifications.Currently, the prefix “Completed with DocuSign” is automatically added at the beginning of the email subject line.Would it be possible to make this prefix optional or configurable?This would help improve the overall user experience.Thank you in advance for considering this suggestion.
Our Maestro workflows come back to us after the customer signed and go through several backroom departments. We would like the ability to add comments to the document that are not seen by the customer that signed and do not show up on the Certificate Summary.
In an eMaestro workflow, after sending an e-signature template for signature, no further steps can be performed until the sent envelope is closed. Is there a way to change this? Specifically, to execute the further steps upon sending the envelope instead of only after it's closed?
It would be extremely useful to be able to run a report on Reminders that have been automatically sent for envelopes so that we can check if and when they are going out and who the recipients are.
Problem: Currency field in CLM docgen forms The CLM Currency control currently enforces US-style number formatting (decimal “.” and thousands “,”). EU-style formatting (decimal “,” and thousands “.”) isn’t supported, which creates usability and data-entry issues for European users.
DocuSign recently changed the information available on the individual envelope pages. I prefer having the envelope number on the main page without having to click through to “Details” and, similarly, I prefer having the information about whether a signer has merely received or actually viewed the envelope email on the main page as opposed to having to click through to History under the three dots (kebob).
I have the below fields:Quantity-text field-validation is custom, regex patter ^\d+$ to make sure they enter a whole numberDuration of storage-text field-validation is custom, regex pattern ^\d+$Rate 2-Text field-Add text is 4.89 for a constantTotal Charge 2-formula field-formula is [Rate 2]*[Quantity]*[Quantity]. It will not allow this formula unless the quantity and duration validation is none or a number.But they will not work because I don't want to allow decimals but only whole numbers.





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