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...
19560
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
We have a number of users who use “Sign a Document” rather than “Send and envelope”. Currently the default font when self signing is Lucinda Console and there is no way to change that. Are you able to configure this so it will use the default font set at account level, or even allow users to format the font field in the same way as when they send an envelope?
If multiple word documents are part of a Salesforce DocuSign Gen template, the order of the documents can only be defined by uploading them in the correct sequence. If, for example, only the first document needs to be updated and therefore re-uploaded, all documents must be deleted first and then re-uploaded in the correct order.A drag-and-drop feature or document numbering within the DocuSign Gen template would make this much easier, so only new/updated word documents need to be uploaded.
Hello, when creating a brand profile and the header background is white, the pencil or document icon on the preview appears to be black. However, it is still white on the actual email making it invisible if the background is white. When the icon is downloaded, it is confirmed to be white and has a transparent background therefore it only is visible if the background is in a different color. It would be helpful for its color can be controlled as well or the preview to be accurate. Brand PreviewScreenshot from an email The pencil or document icon which appears to be black since it is white with transparent background. Please see the attached images for reference. Thank you!
When a witness opens an envelope to witness/sign, they are presented with a screen in which they have to enter their Occupation and Address details. These fields are mandatory and the witness must complete these details before they can open the envelope to complete/sign/witnesses the document(s). It would be useful if these fields could be available to the creator of the envelope when they are adding fields to documents so that these details are auto filled into the document once completed by the witness. Currently, if the witness name, occupation, address etc. are required information on the documents the creator has to create text fields for these and the witness has to re-key this information into the document after they have already entered these details on the mandatory screen when accessing the envelope. This can result in the witness updating the text fields to say: as already entered etc. and the document not being populated with the required information. We are using tooltips in an attempt to resolve this issue but witnesses continue to complete the document fields in this way. Is it possible to make these fields available (like the Company, Title fields we have for standard users)?
I think its essential that critical actions should be recording in the audit log and be reportable from the front end. Actions such as moves/adds/changes should all be auditable and visible via reports/logs. In my specific example an admin deleted multiple templates in a very short space of time and this was not traceable in the system. These audit logs are essential for compliance and picking up malicious activity.
I am a DocuSign administrator. I am also a notary and official signer for our department. I occasionally assist with the remote online notarization. If I conduct a RON, I am not able to sign on behalf of our entity as my official capacity. I must choose to be one signer or the other. I really need to be able to sign as both. The current workaround is to use a different email address (personal or someone else’s) for my official capacity to sign for my agency. I should be able to sign in two different transactions/signing sessions in one envelope as they are two different positions - notary vs. attestation.
Idea Description:Recent incidents in the SaaS ecosystem have highlighted critical security gaps where third-party applications accidentally exposed Access Tokens or API credentials, leading to unauthorized API activity. As described in Okta’s analysis of recent breaches, enforcing strict network-based controls on API usage is an essential layer of protection.https://www.okta.com/newsroom/articles/first-drift--now-gainsight--closing-the-gaps-in-saas-hygiene/Today, Docusign API integrations often require developers to access private keys or integration secrets during building and maintenance. However, once developers leave the company or when keys unintentionally end up in code repositories, these credentials may still be used to call Docusign APIs from unauthorized locations. This creates significant security risks for customers, especially considering that contracts are among the most sensitive enterprise assets.To mitigate these risks, we propose that Docusign introduce network-level security controls for API integrations, similar to Okta and Salesforce:Requested Features Network Allowlist / Blocklist per Integration Key (Apps and Keys) Allow administrators to restrict API calls to specific IP ranges, corporate networks. This ensures that even if tokens or keys are leaked, attackers cannot call Docusign APIs from unapproved networks. Network Conditions as a Core Security Feature (available across all plans) Since this is foundational security—similar to Salesforce’s Login IP Ranges—it should be available to all customers, not limited to higher editions. Optional enforcement policies “Block API requests from unknown networks” “Allow specific IP ranges only” “Alert or log when API calls come from new locations” Audit Trail Enhancements Show the source IP, geo, and network of each API call for monitoring and incident investigation. Customer Value Protects against leaked API keys or tokens being used from unauthorized networks Helps customers meet compliance and internal security standards Reduces risk when developers rotate, offboard, or change roles Provides essential zero-trust protections in a growing threat landscape Aligns Docusign with industry-leading security practices (Okta, Salesforce) 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
Per our audit team, it would be helpful if there was a way to report on templates that use authentication methods verses templates that do not. As a financial institution any envelope that leaves our bank we have to have an authentication method in place, but did not catch this when we first built templates. A report to check this would be helpful instead of having to check each template one by one.
Enable the ability to customize the display format of the Date Signed field (e.g., “March 18, 2026” or “Mar 18, 2026”) at the account and/or template level, independent of recipient locale.Current limitations: Only global date formats are available, with limited options No support for “month spelled out” formats in some tenants No per-template or per-field override Workarounds (e.g., text fields) require manual input and reduce reliability Requested outcome:Provide flexible, enforceable date formatting options (including month name formats) for system-generated signing dates to eliminate ambiguity across regions.
Scenarios:People who were cc’d in templates changed Company domain changedProblem:When there are multiple templates involved, currently we have to individually “edit” every template, which is very frustrating and time consuming.Idea:There’s already functions to filter and select multiple templates, a simple text function to “find-and-replace” in the selected template emails would save the day.
We would like to request support for font sizes below 7pt in document fields. In some of our contracts, even the minimum supported size of 7pt results in text overflow due to limited space, and having the ability to use a smaller font size would help us accommodate necessary content without altering the document layout.This enhancement would greatly improve flexibility for scenarios where space is constrained.Best regards
Date stamp / Insert Date option should utilize a wrap text feature to contain the data within the length of the date itself. The additional digits and values infringe on subsequent fields or run off the page if oriented to the right side margin.





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