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...
23960
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
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.
I am requesting adding the Email authentication settings to the Powerform reports. It would be helpful to monitor our standard configurations and do any necessary clean-up when needed.
Currently, the “Autogenerate” button for Access Code is available only for the recipient types Receives a Copy and Needs to Sign. For the EU Advanced signature type, the Access Code must be entered manually, as no autogeneration option is provided.We request the addition of the “Autogenerate” button for the EU Advanced signature type, functioning the same way as for other recipient types — allowing users either to manually enter or automatically generate a random access code, with the option to modify it afterwards. Business rationale:This enhancement would ensure consistent behavior across all signature types, reduce manual input errors, and streamline envelope preparation for workflows using EU Advanced authentication. It will as well make the life of users easier as they don’t need to create the code from scratch for EU AES
When I send out an envelope with a Word document attached that has a .docx file extension, the final signed document comes back with .docx.pdf on the file name. It would be great if the final file name stripped out the .docx and created a final document with only the .pdf extension. Currently the only way to fix this is to upload the Word document, and then re-name it to remove the .docx before it is sent. This is painful - especially when I’m sending many documents in the envelope.
Docusign: CFR-Part-11When uploading attachments, a maximum of 5 documents can be selected at once. The order of the documents often changes during the upload process. Furthermore, it is not possible to insert an additional document between them.Suggestion for improvement: Please add a feature that allows uploaded files to be rearranged via drag and drop. Also, please allow a larger number of files to be uploaded simultaneously.
Based on our current understanding, onboarding an agent or broker into DocuSign Rooms involves several disconnected steps. To streamline this, we are already implementing OIDC Connect for user onboarding. We are looking for an API (programmatic access) to allocate seats to new agents and brokers and linking their NAR IDs to enable form access. Could you please provide information regarding an API that would allow us to programmatically allocate a Rooms seat and map the corresponding NAR ID for form access? We are looking to automate this process to ensure a more seamless integration for our users. We look forward to your guidance on the available technical options.
Please consider introducing a new feature that allows users to create standalone message templates, essentially a way to save and reuse email subjects and body text without requiring a document or a full envelope template.This would remove unnecessary steps, reduce template clutter, and streamline high‑volume or multi‑scenario workflows. Many organisations (including ours) have numerous use cases where the document changes frequently, but the message content remains consistent. A dedicated “Message Templates” feature would make DocuSign more efficient, reduce errors, and eliminate the need for workaround templates. Users would be able to select the appropriate message from a personalised library and insert it directly into an envelope (whilst in the “Send an Envelope page”) ensuring consistency and reducing preparation time.Thank you for considering this enhancement. It would make a meaningful and practical difference to everyday users and administrators.
To avoid the risk of documents being completed without visible signatures in the designated fields, I suggest adding a warning during the envelope-sending process.If no signature fields are added, the system should display a clear message such as:“No signature fields have been added to this envelope. If you continue, recipients will only need to click ‘Finish’, and the document will be marked as completed without capturing a visible signature. Do you wish to proceed?”This type of warning would help ensure that senders are fully informed of the consequences before sending the envelope and would reduce the likelihood of completed documents being rejected due to missing visible signatures.
We have various templates with scenario that if one text field is filled out a different text field should not be. I know there is the ability to do a radio button group requiring only one button selection and conditional logic to then display the appropriate text field and make required, however the forms we have this for, a radio button placement would not make sense and would cause confusion for the recipient.I’d like to see DocuSign templates enhanced to allow grouping selected text fields with the requirement options that Radio Button Groups have today.
Hi , It would be really helpful if CLM Object API v2 supported creating and updating Clause Options via API. Today there is an POST Api /v2/{accountId}/clauses (Text/Notes) but this does not add the clause option, the GET /v2/{accountId}/clauses/{clauseId}/options returns no options for the previous post API. We’ve been advised by DocuSign Support that currently options are created through UI-only(Case Id: 16951191). Could you please enable API endpoints to create/update/delete clause options (e.g., option name/label, text, notes, order/active) so customers can automate clause library migrations and keep DEV/UAT/PROD in sync without manual UI work.





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.