Get Started
Get Inspiration
Groups
Events
Ideas
Release Hub

Start a Post
Log in

Home
Ideas

Ideas

Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.

Featured topics

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...

Forum|Forum|2 years ago

22860

Update on the status of submitted ideas

Hi everyone! We’ve heard your questions about the status of submitted ideas in the Ideas forum.Internally, the Docusign team is actively reviewing you...

Forum|Forum|1 year ago

9708

Filter by Idea status

Filter by category

1017 Ideas

Most Replies

Most Votes

Newest First

EMBG LoCoNewcomer

AI-assisted error identificationIdea Submitted

Docusign error messages can be very confusing for ordinary users (not professional developers). It would be helpful to be able to use a Docusign diagnostic AI to identify exactly where the issue is occurring when you get a “generic” error message.For example, this message tells me something is wrong but it doesn’t tell me exactly what fields are resulting in the error, which makes correcting the issue a very challenging process.I went through and made sure all the fields were used the same locale indicator(s) and the issue still occurs and I don’t know why.

Forum|Forum|28 days ago

GreenLantern22New Voice

Feature request: reopen a completed envelope for correctionIdea Submitted

We have some complex/long forms and occasionally the signer will provide an incomplete/wrong answer to some questions.Rather that void and request them to complete a blank form again - we’d like to be able to reopen and send the form back (with all their existing answers) for them to make the required correction, resign and return.

Forum|Forum|28 days ago

Ivana ForestierNewcomer

filters in reportsDuplicate

Allow filtering as in Excel using the “contains” filter.Select multiple filters: for example, display all contracts that start in June and May, not just one of the two, to avoid having to create two reports.

Forum|Forum|28 days ago

claudia sallustioTroubleshooter

BASIC SORTING AND FILTERS FUNCTIONS FOR LARGE VOLUMN OF AGREEMENTS NEEDED URGENTLYIdea Submitted

BASIC SORTING AND FILTERS FUNCTIONS FOR LARGE VOLUMN OF AGREEMENTS NEEDED URGENTLY. I WOULD ALSO INCLUDE THE NEED FOR TAGS. REPORTING IS ALSO VERY LIMITED. I CANT SORT BY FOLDER WHICH IS THE ONLY WAY I CAN TRY TO KEEP A TRACK OF WHICH AGREEMENTS I HAVE ALREADY DOWNLOADED.

Forum|Forum|28 days ago

Malik PressNewcomer

Docusign Part 11 Signing Reason AssignmentIdea Submitted

Current ChallengeWhen signing Part 11 envelopes, signers must select a "Signing Reason" for every signature applied. Currently, the dropdown menu to select a Signing Reason displays all Signing Reasons defined for the selected system language. By default, Docusign Part 11 provides three Signing Reasons (Author, Reviewed, Approve). Through the "Signing Resource File" of a specific Brand, an Admin can modify these or add custom reasons. However, for GMP documents, there is a fixed hierarchy of required signatures: 1. Author signatures, then 2. Reviewer signatures, finally 3. Approver signatures (Approver signatures are mandatory for every GMP document; Necessity of Author/Reviewer signatures vary by GMP document). Consequently, when we create a Part 11 envelope, the selection and order of signers are based on these requirements. Each signer is assigned a fixed role (Author, Reviewer, or Approver), which dictates exactly which Signing Reason they must select. Currently, we assign these roles visually at document creation via a signature table within the document itself (columns: Role, Name/Function, Signature). We explicitly enter "Author," "Reviewer," or "Approver" in the role column of each signer row. Signers are trained to check this column and then manually select the matching Signing Reason in Docusign. Pain PointsUnfortunately, deviations frequently occur. Despite training and support materials, signers often select a Signing Reason that does not match their assigned role. When this happens, the entire Part 11 envelope must be voided, re-created, and re-sent for signatures. Additionally, I noticed that when adding custom Signing Reasons via the Signing Resource File, they must be added manually for all languages. Otherwise, the custom reasons do not appear if a signer uses a different system language. Proposed Solutions (User Stories)To improve the "First-Time-Right" rate for signers and reduce the administrative burden of managing Signing Reasons, I have defined the following requirements: High PriorityHP1: As an Admin, I want to create, update, and delete Signing Reasons in a dedicated Admin Setting Section, so that they are available for all Part 11 envelopes regardless of the selected Brand.HP2: As an Admin, I want to define a Default Label for each Signing Reason, so that the reason is displayed to all signers even if a specific translation is missing.HP3: As an Admin, I want to define labels for all available system languages for each Signing Reason, so that they appear correctly in the signer's selected system language.HP4: As a Sender, I want to select/restrict the specific Signing Reasons available to a signer when creating a Part 11 envelope, ensuring the signer cannot accidentally select an incorrect reason. Low PriorityLP1: As an Admin, I want to create, update, and delete "Signing Roles" in a dedicated Admin Setting Section.LP2: As an Admin, I want to assign one or more Signing Reasons to a specific Signing Role.LP3 (Alternative to HP4): As a Sender, I want to assign a "Signing Role" to a signer when creating an envelope. This would restrict the dropdown menu to only show the Signing Reasons assigned to that role, ensuring the signer cannot accidentally select an incorrect reason.

Forum|Forum|29 days ago

ErveNewcomer

Define brand ID via API for multitemplate useIdea Submitted

Connected to our CRM, we are calling Docusign to generate envelopes based on some templates. As we have many brands, we standardized the documents in order to use global template on which we would like to set brand when generating envelope via API.Unfortunately, APIs don’t have any brand id parameter that we can set to generate envelopes with the correct brand, and working with 100 different templates is not possible when it comes to maintenance and update.Is it possible to add the brandid as parameter when calling for a templated envelope generation? Regards

Forum|Forum|29 days ago

KennyFllNewcomer

Support PDF Embedded Attachments and Require Recipient Acknowledgement Before SigningIdea Submitted

ProblemPDF files can contain embedded attachments, such as Excel spreadsheets. For example, a commercial proposal may include the main offer as a PDF and a detailed scope of work or pricing calculation as an embedded Excel attachment.These embedded files can be opened when viewing the PDF in applications such as Adobe Acrobat. However, when the same PDF is uploaded to DocuSign, the embedded attachments are not visible or accessible to the recipient.As a result, important contractual information may not be available during the signing process, even though it is technically part of the original PDF.Requested functionalityI would like DocuSign to support the following capabilities: Display embedded PDF attachments When a PDF contains embedded files, DocuSign should detect and display them separately in the envelope or signing interface. Senders and recipients should be able to view or download these files without having to extract and upload them manually as separate envelope documents. Require acknowledgement before signing Senders should be able to mark an attachment as required reading. Before the recipient can continue to the signature fields, the recipient should be required to: open or download the attachment, confirm that they have reviewed it, and only then proceed to sign the document. The acknowledgement should be recorded in the envelope history or certificate of completion, including the recipient, attachment name, date and time.Example use caseA company sends a proposal for signature. The main PDF contains the commercial terms, while an embedded Excel file contains the detailed project scope.The recipient should be able to download and review the Excel file directly within the DocuSign signing process. After confirming that the file has been reviewed, the recipient can proceed to sign the proposal.Business valueThis functionality would:ensure that recipients can access all relevant contractual documents, reduce the risk of recipients overlooking important attachments, improve transparency and auditability, avoid the need to manually extract and upload embedded files, and provide evidence that required supporting documents were made available and acknowledged before signing.

Forum|Forum|29 days ago

Rhys HNewcomer

Workflow Building for Document EventsIdea Submitted

Hi, It’d be a really great addition to be able to have workflows based on the status of a contract. For example, if we could send a renewal contract when an existing one is due to expire automatically that’d be ideal! Kind regards,

Forum|Forum|29 days ago

LohaineNewcomer

Combine Envelope Documents When Using the "Archive To" Agreement Rules in EsignatureParked

Combine Envelope Documents When Using the "Archive To" Agreement Rules in EsignatureCombine envelope documents into a single PDF file to save files in directories (SharePoint, OneDrive, etc.) when using "Archive To" agreement rules in Esignature. Currently, the system only provides the option to save the files in a zip folder or as individual files in the directory.

Forum|Forum|30 days ago

Nikoleta M.Newcomer

The email attachments exceed 5 MB.Duplicate

Increasing the email attachment limit beyond 5 MB would simplify communication and improve efficiency. Users could send larger files directly by email without relying on external file-sharing services, making the overall process faster, easier, and more convenient.

Forum|Forum|30 days ago

Tracey RaeNew Voice

increase the size of the documents from 5 MB limit.Parked

We would love to send a range of sized documents to our customers and partners. if we could increase the size of the documents from 5 MB limit.Having the documents go from an email attachment to a downloaded link if the size is reached is an extra step for both parties unfortunately.

Forum|Forum|30 days ago

JesseMNew Voice

Stop prioritizing “smart” automation over user controlIdea Submitted

DocuSign continues to introduce updates that appear designed to make workflows “easier,” but in practice they are making the platform less intuitive and more frustrating for experienced users.The recent change requiring users to drag documents by a small, greyed-out outline instead of the actual document itself is a perfect example. This is not an improvement to usability — it hides the function users are looking for and makes a simple task unnecessarily difficult.The same issue exists with automatic signer arrangement. DocuSign increasingly tries to make decisions on behalf of the user instead of allowing the user to control the workflow. When preparing legal documents for signature, users need predictable behavior and direct control, not automation that has to be corrected.Please prioritize:Clear, visible controls User-selected ordering instead of forced automation The ability to disable “helpful” automatic features Testing updates with real-world users before rolling them outA good user interface should reduce clicks and confusion, not require users to discover hidden tricks after an update breaks a workflow that previously worked.DocuSign is a critical business tool. Please focus on making it more reliable and user-friendly rather than adding changes that create unnecessary friction for the people who use it every day.

Forum|Forum|1 month ago

bpm-energyNewcomer

Resize a signature field to tailer to your documentDuplicate

It would be an improvement from my point of view to be able to size the signature box freely, to tailor its shape to the document being signed, similar to BlueBeam etc.

Forum|Forum|1 month ago

apersonaNew Voice

Resizing a Signature Field is impossible... WHY????Idea Submitted

I have been sent a document for me to sign and then to forward to a countersignee.The document already has dotted lines for signature name and date.The Docusign signature field is a tall rectangle, which does not permit resizing, only scaling. This means that it simply does not fit in the available space. This is ridiculous. Why on earth is it not possible for a user to resize their own signature field?

Forum|Forum|1 month ago

daniel.krcmarDigital Collaborator

Add More Data Types for Envelope Custom FieldsDuplicate

Add More Data Types for Envelope Custom FieldsProblemCurrently, Envelope Custom Fields only support Text and List field types. This limits how metadata can be captured and validated for envelopes.Suggested EnhancementExpand Envelope Custom Fields to support additional data types, such as:Date Number Boolean (Yes/No) Email Phone Number Currency Decimal Date & TimeBenefitsImproves data quality through built-in validation. Reduces the need for custom integrations and manual formatting. Makes searching, filtering, and reporting on envelope metadata more reliable. Enables downstream systems to consume correctly typed data without additional parsing. Aligns Envelope Custom Fields with common business use cases such as contract renewal dates, invoice amounts, approval flags, and reference numbers. Example Use CaseA company uses an Envelope Custom Field to store a contract expiration date. Since only text fields are available, users must manually enter the date in a specific format, increasing the risk of inconsistent or invalid values. A native Date field would provide a date picker, enforce valid formatting, and improve data consistency across integrations and reporting. Requested EnhancementPlease extend Envelope Custom Fields to support additional data types beyond Text and List, starting with Date, while allowing future support for other commonly used field types such as Number, Boolean, Email, and Currency.

Forum|Forum|1 month ago

daniel.krcmarDigital Collaborator

Add More Data Types for Envelope Custom FieldsIdea Submitted

Forum|Forum|1 month ago

akosNewcomer

Ability to add custom attributes to partiesIdea Submitted

Currently using the Parties module is limited due to the low number of pre-defined fields and no option to create/ add custom ones.A great point about CLM is the level of customizability, but this module is completely against that as it does not provide any option to expand parties to a usable level.In our case: The limitation of party attributes stops us from properly moving supplier data into CLM, it also prevents us from abandoning the currently used solution for contract generation, as we cannot rely solely on CLM.

Forum|Forum|1 month ago

saumyaNewcomer

Versioning of Docusign templatesIdea Submitted

Hi Team, Currently we have the capability to track who made edits in the docusign templates and when, however we currently dont have activity tracking history for the templates. This will help us to understand what change was made in the template also

Forum|Forum|1 month ago

J.MahonNewcomer

Enhancement Request: Support for Multi‑Word First Names in Recipient FieldsDuplicate

Proposed Enhancement:Some recipients have multi‑word first names (for example, names like “Mary Anne” or “Jean Paul”). When these names are entered into a template, Docusign interprets the second word as a middle name and only transfers the first word into the “First Name” fields. This leads to incomplete or inaccurate recipient information in templates.It would be helpful to have a way to correctly capture multi‑word first names. This could be supported through a sender‑side function, an optional field setting, or another mechanism that ensures the full first name is preserved when mapping recipient data into template fields.

Forum|Forum|1 month ago

AP-EMDNew Voice

Behavior of Standard First & Last Name fieldsParked

Our company manages a couple hundred DocuSign accounts for our customers. Many of the forms used require “First Name” and “Last Name” & so we use the Standard name field & change it from Full Name to either First Name or Last Name, as needed. However, we have found that the expected behavior of those fields in DocuSign is to pull in the first word of each name rather than the full name. For example, if my first name is Mary Ann (not Mary), using the Standard First Name field only pulls in Mary, which is incorrect. If my last name is Smith Jones, the Standard Last Name field only pulls in Smith.We are using these fields for legal documents & the format happens to sometimes ask for First Name vs Last Name, which is why we can’t use the Standard Full Name field as a work-around. In addition, although Custom First & Last Name fields will also work, it’s extra clicks to go get those, they are harder to copy/paste, & it’s harder to educate users to select those when the Standard fields are the first thing you see.Please update the behavior of the Standard First & Last name fields to pull in the full text that a user identifies as the First or Last name.

Forum|Forum|1 month ago

KellieNNewcomer

Enhancement Request - make webform fully available in language other than what Docusign account is set up asIdea Submitted

The request is to have a web form fully available in a language other than what the account is set up as for all recipients/signers.The language for non-configurable "system" labels and descriptions (these are error messages and other non-configurable text (for example, "Loading…", Finish Later, Next, Back, etc.) on the form as well text in the header/footer of invitation and completion emails) is determined when the web form is initially created based on the form creator's language settings in their Docusign account. Updating the web form configuration file as well as branding worked for the first recipient/signer to have their web form fully available in another language other than the account. However, this did not affect the experience of the second recipient/signer - their non-configurable "system" labels and descriptions were still only available in the language of the Docusign account.

Forum|Forum|1 month ago

DELDRIDGEFBBNew Voice

Enhancement Request - Recipient Authentication Skip OptionIdea Submitted

The account-wide "Recipient Authentication Skip Option" rules exclusively apply to the legacy KBA (ID Check) engine. Because the newer KBA on IDV platform is built on an entirely separate, high-security identity architecture, it enforces re-authentication on every single transaction. It deliberately does not support or inherit the 24-hour browser-caching or "remember this signer" settings.If an organization chooses to use Recipient Authentication Skip Option settings, it should apply to any authentication method used by the organization. Limiting it to a single form of authentication results in mixed client experiences when senders are using different forms of authentication. This is also not user friendly when Salesforce only uses legacy KBA while Docusign direct can use a variety of authentication methods. Organizations should be able to have modern authentication and consistency across system usage.

Forum|Forum|1 month ago

DELDRIDGEFBBNew Voice

Reporting for envelopes - creation to completionIdea Submitted

We need a single report that captures every activity from the time and envelope is created until it is completed to show a full history for researching. This includes templates used, authentication method changes, resend or corrections performed, and file name for each document in an envelope. Right now, multiple reports and the certificate of completion have to be pieced together to research. Ex. Fraud occurs and you want to know who sent the envelope, who it was sent to, all documents in the envelope, if a template was used, changes to the template authentication, pass/fail status of every authentication attempt, resend/correction steps, and any other activity that occurred in the process.

Forum|Forum|1 month ago

daniel.krcmarDigital Collaborator

CLM Report Exports: Export numeric columns as actual number values in Excel (not text)Idea Submitted

When exporting a CLM report to Excel, numeric columns (e.g. contract Value) are exported as text instead of numbers. Excel only recognizes the value as a number after manually double-clicking into each cell. This behavior also interacts poorly with regional settings (e.g. Dutch locale, where the decimal separator is a comma), making the values unusable without manual conversion.Customers use exported reports for downstream analysis — SUM, COUNT, pivot tables, financial reconciliation. With values exported as text, none of these Excel functions work out of the box. For reports with hundreds or thousands of rows, manually converting each cell is not workable. Support has confirmed this is currently expected behavior, but for business users the export is effectively broken for its main purpose: calculating on numeric data.Enhancement:Export numeric and currency columns with a proper Excel number data type (e.g. via native XLSX cell typing), not as text. Respect the user's locale/regional settings (decimal and thousands separators) so values parse correctly in Dutch/European Excel configurations. Optionally: allow the report designer to define the data type per column (text / number / currency / date) for exports.Workaround today: Manually double-click each cell, or use Excel's Text-to-Columns / VALUE() conversion — both impractical at scale.

Forum|Forum|1 month ago

sahil.shettyNewcomer

Add formatting control for [[Data:DocumentNames]] merge field (line-separated / list output)Idea Submitted

The [[Data:DocumentNames]] merge field renders all document names as a single comma-separated string. Please add support for controlling how the list is formatted — at minimum a line-break/newline delimiter, ideally a bulleted or line-separated list option.Problem / use case:When an envelope contains several documents, a comma-separated string on a single line is hard to scan. Recipients skim the notification email quickly, and a run-on list makes it easy to miss that multiple documents are enclosed. This is especially relevant in regulated industries (e.g. financial services) where signers need to clearly see each form they are being asked to sign. Presenting each document name on its own line materially improves readability and reduces recipient confusion.Requested behavior:A supported option to output document names one per line (or as a bulleted list) instead of comma-separated — controllable within the email body / Email Resource file. For example, a delimiter parameter on the merge field, or a companion merge field that emits a formatted list.Current behavior (confirmed with DocuSign Support, Case #17666072):The merge field does not support any formatting options. Output is always comma-separated, the behavior is identical across signer/sender/CC notifications and within Email Resource files, and there is no alternative merge field, repeatable region, or formatting mechanism to display names on separate lines. Support advised submitting this as an enhancement request.Impact if delivered:Clearer, more readable signer notifications; fewer "which documents am I signing?" support questions; better experience for envelopes with multiple documents.

Forum|Forum|1 month ago