Skip to main content
arrow-left Back to Docusign.com

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

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

    Filter by Idea status

    Filter by category

    1017 Ideas

    L
    Docusign Employee
    L.WojciechowskiDocusign Employee

    CLM - Modernized Search - Improve Search to Handle Case and Quote Variations in Phrase SearchesIdea Submitted

    Problem / User Pain Users performing exact/phrase searches in CLM can miss relevant results when the document text differs from the query by:Case (e.g., searching agreement's records vs. document text AGREEMENT’s records) Punctuation style (e.g., straight apostrophe ' vs. curly apostrophe ’, and straight vs. curly double quotes)This is especially confusing in quoted phrase searches, where users expect “exact phrase” matching but not failure due to common formatting differences introduced by OCR or word processors. User Expectation Because CLM functions as a document repository, users reasonably expect search behavior similar to word processing tools:Curly and straight quotes/apostrophes should be treated as equivalent for matching. Exact/phrase search should support a case-sensitivity toggle, so users can choose whether case must match exactly.  Proposed Enhancements Case-Sensitivity Toggle for Phrase Searches Add an option (e.g., checkbox or advanced search setting) to enable/disable case-sensitive matching for exact/phrase searches. Example: Allow "agreement's records" to match AGREEMENT’s records when case-sensitivity is off. Normalize Quote/Apostrophe Variants in Search Matching Treat punctuation variants as equivalent during indexing and/or query parsing: ' and ’ " and curly double quotes (e.g., “ and ”) Ensure phrase searches do not fail solely due to punctuation style differences.   BenefitsMore intuitive and consistent “document repository” search experience Fewer false negatives in search results (especially in OCR-derived text) Reduced support burden and improved user confidence in CLM search accuracy  Interim Workarounds (until implemented)Remove quotation marks to broaden results Try both curly and straight apostrophe styles when searching exact phrases [Internal reference: 16843931]

    0
    L
    Docusign Employee
    Forum|Forum|5 months ago
    C
    Troubleshooter
    ClutterbugTroubleshooter

    requesting the ability to replace or insert a page within an existing templateIdea Submitted

    ​@Alejandro.Ramos ​@Jeff.Daviscourt this is a feature in Adobe E-sign which is very handy. Being able to move pages in and out of a document before sending. When a client changed something on their estimate, I was able to take the already made PDF, and swap in a new page in the correct order, without having to remake the whole document and hence, redo all the fields. Docusign really falls short on this. This should be a feature that Docusign should consider.I just needed to change a 13 page template that I had put about 85 fields in. I needed to add a new page, in the middle of this template. No can do in Docusign without a whole, time losing, redo.Please put this feature in your suggestions!CheersClutter-bug

    1
    J
    Forum|Forum|5 months ago
    L
    Docusign Employee
    Luis.PradoDocusign Employee

    Enable Bulk Signing for High-Volume EnvelopesDuplicate

    Customer is helping a vendor to send docusign envelopes to (est.) 10,000 clients. After each client completes their docusign, they’re considering routing the envelope to the supplier. But this only works if the supplier has the ability to complete dosusigns in bulk.It will be good to have a feature/setting/capability, on a special project basis (not an ongoing process basis) that would allow the vendor to complete 10,000 docusigns in bulk (instead of clicking through 10,000 emails?)

    1
    M
    Forum|Forum|5 months ago
    C
    Active Voice
    christinecActive Voice

    Allow the ability to turn of Copy EnvelopeIdea Submitted

    Please allow organizations the ability to turn off copy of a completed envelope so that managers cannot utilize this.  We have managers who have started copying envelopes and it’s causing an issue due to signing structures etc. 

    1
    M
    Forum|Forum|5 months ago
    D
    Newcomer
    DC125634Newcomer

    Expand Smart Sections functionality to large devicesIdea Submitted

    Currently collapsing sections within a document is reduced to smaller devices (tablets and mobile). We would like the signers to have collapsible fields no matter where they are opining it form so all signers are seeing the same feature. As well as make it a template or an option to select full documents that were uploaded to the docusign. There is information and documents where our clients have already reviewed and approved that we keep in the signature packets for a easy filing while collecting signatures. To streaming signatures, we would like this option across all devices.

    0
    D
    Newcomer
    Forum|Forum|5 months ago
    M
    Newcomer
    MTDobsonNewcomer

    Improve Limit Document Visibility (LDV) Defaults and Grid for Safer and More Flexible Document SharingIdea Submitted

    Idea Summary:As a law firm regularly sending highly confidential documents, we rely heavily on DocuSign’s Limited Document Visibility (LDV) feature. However, the current configuration presents a risk of unintended document exposure due to default settings and limited sender control. I propose a change to how LDV behaves to improve user experience, reduce risk, and enhance platform flexibility.Background & Context:We use DocuSign eSignature and have explored LDV settings extensively with support (Case #15948495). Francis from support has been excellent in explaining the nuances, but the current behavior still poses challenges.There are two key LDV-related settings:Drop-down: Document Visibility Off Must Sign to View, Unless Sender Must Sign to View, Unless Member of Sender’s Account Sender can set either of the above Checkbox: Allow Sender to Specify Document VisibilityThese settings influence the Document Visibility Grid (Matrix) during envelope setup.Problem:There are two risky scenarios based on sender assumptions: LDV is OFF but assumed ON → Recipients may see documents they shouldn’t.Potentially serious consequences, especially in legal contexts. LDV is ON but assumed OFF → Recipients may not see documents they should.Less severe, but still problematic. Currently:If LDV is OFF, the grid is editable, but the sender must take action to restrict visibility. If LDV is ON, the grid becomes read-only, and there is no way for the sender to override visibility and enable LDV —even if needed—without adding fields to every document for every signer (which is impractical for large envelopes).Proposed Enhancements: Make LDV Default Configurable but Always Editable: Allow LDV to default to ON or OFF based on admin preference. Always allow the sender to override visibility during envelope setup (unless explicitly restricted by admin). Improve Grid Behavior: Keep the “Allow sender to specify document visibility” checkbox functional regardless of LDV default. Make the Document Visibility Grid read-write in all configurations where sender control is permitted. Clarify that the checkbox relates to the Grid functionality. Benefits:Reduces risk of unintended document exposure by allowing LDV to be enabled by default, but disabled by the sender where required.   Improves sender control and flexibility. Enhances user experience by avoiding unnecessary workarounds. Aligns with best practices for secure document handling.Discussion Invitation:Would love to hear from others—especially those in legal, healthcare, or finance—who rely on LDV. Have you faced similar challenges? How are you currently working around this? Would these changes help your workflows?

    1
    M
    Forum|Forum|5 months ago
    R
    Newcomer
    RandyDiSimoneNewcomer

    Change Email Subject line before sending.Idea Submitted

    I notice that agents never change the subject line. I think that it’s because of its location low on the page where documents are uploaded (past recipients). It would be nice if before we send the DocuSign it let us change the subject line as the last step. It could also have a reminder to label the subject line with the property address and what the documents are pertaining to. Example “1234 Main St - Buyer Counter Offer 1“. I know this is such basic stuff but I never get emails that are property labeled with the right subject line. Thank you. 

    1
    M
    Forum|Forum|5 months ago
    W
    Active Voice
    wojtektpActive Voice

    Get An Email Notification When Any Of The Recipients Sign The DocumentDuplicate

    As a document sender, I would like to receive a notification when any of the recipients sign a document.Scenario:There are two recipients without order Once one of the recipients signs we need the other to perform a certain action offline before signing the document We just had a situation where we lost of 7 days of revenue for a big account because we missed a signature by 7 days.

    4
    J
    Forum|Forum|5 months ago
    A
    Docusign Employee
    Ana.RochaDocusign Employee

    Improve error messaging when template tabs are placed off-page during envelope creationIdea Submitted

    When using document template, the sender sees this error when creating an envelope: "We're unable to create a new envelope. Check your connection and try again."However, the real cause (visible only in a HAR file, not in account API logs) is:"TAB_OUT_OF_BOUNDS" - "Tab is placed off of the page. Tab is located off of page [number]"Based solely on the error message displayed on Docusign web page, the user has no way to know that a field was off-page. A clearer message would have let them fix it themselves without having to contact Docusign Support.For this reason, the customer requests that, when envelope creation fails due to out-of-bounds tabs in a template, show a clear, actionable message, for example:"We couldn’t create this envelope because one or more fields are placed off the page in template <template name>, page <page number>. Please move the field(s) within the page boundaries and try again."This will reflect the real cause of the issue and indicate template and page so the user can correct it.

    0
    A
    Docusign Employee
    Forum|Forum|5 months ago
    S
    New Voice
    SB.BCTNew Voice

    X-DocuSign-Act-On-Behalf does not allow creation of envelope viewsIdea Submitted

    When you attempt to create an envelope view using the X-DocuSign-Act-On-Behalf header you get the following error:{ "errorCode": "ACT_ON_BEHALF_USER_NOT_ALLOWED", "message": "An 'Act on Behalf Of' user is not permitted for this operation."}I replied on a different post about this same issue (Attempting to create a Sender View using Shared Access fails: ACT_ON_BEHALF_USER_NOT_ALLOWED | Community), however it is marked as solved though I don’t believe it really is as the “solution” was to use an admin account, as admin accounts can always create sending views for any envelope for any user in the account, but this has some issues because it’s not like you can make everyone an admin. The issue I am facing is that in our system we allow creation of sender views for the users own envelopes, we also respect shared access allowing a user to see any envelopes created by other users who they have been granted shared access to through DocuSign. However, we cannot let a user edit an envelope that was created by another user. As that other post suggests, we could use an admin account to allow this, however that has some issues. Firstly that view will have full access to that envelope within the view so can potentially do things they should not be allowed to, for example if they have shared access at the “edit on behalf of” permission, they can should be able to edit but would not be able send, but as it was created via an admin account the send button will be available. They will also lack the banner on top of the page making it clear they are acting on behalf of the other user, e.g.:The most important thing is that when you generate a view in this way, the envelope history lacks the audit information indicating that it was being carried out by an additional user on behalf of the envelope owner and would always show as the admin user performing the edits meaning you lose any history of who performed the actions on the envelope.  As this functionality is available in the UI already, can this not be added into the envelope view APIs to allow sending the X-DocuSign-Act-On-Behalf header to allow correcting creating sending views when acting on behalf of another user who has provided shared access?

    0
    S
    New Voice
    Forum|Forum|5 months ago
    J
    New Voice
    JulieKelleherNew Voice

    Option to Not Send Empty ReportsIdea Submitted

    I have setup daily reports to get emailed to me, and many days the reports are empty. It would be beneficial to have the option to not receive a daily email if there is no data in the report.

    1
    M
    Forum|Forum|5 months ago
    M
    New Voice
    mikecallaghanNew Voice

    Enhancement Request: Granular Control for Knowledge-Based Authentication (KBA)Idea Submitted

    Currently, Knowledge-Based Authentication in DocuSign is an all-or-nothing setting at the enterprise level. We have business use cases where KBA is essential for certain documents, but not for all outgoing envelopes. Having more granular control would significantly improve usability and efficiency.Proposed Enhancements:Default KBA on All Outgoing Envelopes with Override OptionKBA should be enabled by default for all outgoing envelopes, with the option for the sender to remove it when it is not required. This shifts the decision-making to the sender, ensuring that sensitive documents are always protected unless explicitly exempted.Profile-Level Default SettingsAllow KBA requirements to be set based on user profiles or roles. This would enable departments or teams handling sensitive information to have stricter controls, while other teams can operate with fewer restrictions.Internal vs. External SignersProvide an option to automatically disable KBA for internal signers (e.g., employees using company email domains) while keeping it enabled for external recipients.Template-Level ConfigurationAllow KBA defaults to be set at the template level. This would ensure that documents using specific templates automatically have the correct security settings applied without manual intervention.Conditional Logic Based on Document Type or MetadataEnable rules where KBA is triggered based on metadata such as document type, sensitivity classification, or department origin.Reporting & Audit ControlsAdd reporting features to track when KBA was enforced, who disabled it, and for which documents, to maintain a full audit trailsAPI Support for KBA ControlsProvide granular API endpoints to manage KBA settings programmatically for automated workflows.

    1
    M
    Forum|Forum|5 months ago
    S
    New Voice
    Sourabh0208New Voice

    Enhancement request - Multiple Signing documentDuplicate

    When we send out a document to be signed to Multiple recipients, the sender only gets notified if the document is being viewed by the recipients and only after all the recipients have signed, sender gets the notification that all signs are now completed.Can this be changed to a setting where the sender gets notification when each recipient signs the document?  This would help Sender to timely get notified where does the application lies and not when it is viewed.

    1
    M
    Forum|Forum|5 months ago
    Z
    Newcomer
    zukramNewcomer

    signature obscuringExisting Functionality

    I’ve noticed that sometimes the DocuSign signature at the top of the document overlaps with the text when the margins are tight. You may want to consider a solution for this, as it can obscure part of the content. Perhaps you could allow us to move the DocuSign code to another location, or even display it vertically on the left or right side of the document. Just a thought to help improve your system. 

    2
    J
    Forum|Forum|5 months ago
    D
    New Voice
    donaldinhoNew Voice

    Each custom field must appear as separate column when I generate reportIdea Submitted

    Our use case involves adding multiple custom fields in envelopes to ensure we have a complete record. For example, if I’m signing a contract with Alphabet Inc. and it has been requested by Bruce Wayne, I need both of those information captured as custom fields in my envelope. Now, when I download reports, all custom fields are clubbed into a single column making a mess of the information. I’d like each custom field to be a separate column in the reports. 

    1
    M
    Forum|Forum|5 months ago
    L
    New Voice
    LanaBNew Voice

    Dynamic Routing GroupsExisting Functionality

    I would like to propose the ability to have dynamic routing groups in DocuSign. Currently, in a template, I can save a role without a name or email address, to be entered later via the API. However, with a routing group, there is no way to save it without the name and email address.In my use case, I am populating the recipients when the envelope is generated from the template via the API. I only want the envelope to go to certain signers if a checkbox is checked/unchecked. If I try to save the routing group with a name and email address and then try to set it via the API, it creates a duplicate signer and throws a ONESIGNALLSIGN_NOT_SATISFIED error, despite having fields assigned to each role.

    2
    Raileen.Del
    Forum|Forum|5 months ago
    B
    Newcomer
    Bertrand CHENINNewcomer

    Option to integrate the signatory's name in the signed documentExisting Functionality

    Dear DS teamWould it be possible to get an option to integrate the signatory’s name into the file name of the signed document.Same for the date of signature We would then have :Document name _ Signatory’s name . PDF ORDocument name _ Signatory’s name _ Signature date .  PDF Thank you

    2
    J
    Forum|Forum|5 months ago
    S
    Newcomer
    SSobkaNewcomer

    Enable SMS Delivery to VOIP & Short Code NumbersParked

    Problem:Many of our clients and their representatives rely on cloud-based or on-premises VOIP phone systems (e.g., RingCentral) for SMS.  Currently, DocuSign’s SMS service cannot deliver to these numbers, citing “VOIP not supported due to security...” even though those platforms accept messages sent from standard short code phones. Why This Matters to Our Law Firm:SMS has become the preferred communication/notification channel for many clients. Clients often ask us to send “consent to sign” texts on their behalf; they may have VOIP numbers. Failing to reach them by SMS delays closings, jeopardizes deadlines, and forces inconvenient workarounds (email links, phone calls) they don’t want to deal with.Evidence & Competitive Impact:We successfully received verification codes and SMS via short code on the same RingCentral number that DocuSign SMS fails to reach from HIPPA complaint vendors. DocuSign competitors such as Adobe Sign, by contrast, supports SMS delivery to VOIP numbers; clients are already asking us to switch.Proposed Feature Request:Whitelist major VOIP providers (RingCentral, 8x8, Zoom Phone, etc.) in DocuSign’s SMS routing. Enable short-code delivery to any SMS capable number, regardless of whether it’s identified as VOIP. Offer diagnostic logs for failed SMS, showing provider responses available to me directly without going through the support channels. (this transparency speeds troubleshooting.) Communicate roadmap and expected timeline.Business Benefits:Improves customer satisfaction and retention in legal/financial sectors that mandate SMS OTP. Reduces help-desk tickets and support costs by eliminating “unsupported number” errors. Prevents revenue loss to competitors who already support VOIP SMS.Please prioritize this enhancement in your product roadmap. Without SMS support for VOIP, our firm and many others will be forced to migrate to other platforms that meet our business needs. 

    2
    J
    Forum|Forum|5 months ago
    P
    Newcomer
    psiNewcomer

    signature template to multiple documentsDuplicate

    I need to sign the same training certificate for several users. Currently I upload a document, apply a template, and repeat these steps for each document individually. the possibility to apply template for multiple documents at once would be very helpful

    1
    M
    Forum|Forum|5 months ago
    Jake Fascia
    Active Voice
    Jake FasciaActive Voice

    Add 'Date Last Login' to other User ReportsIdea Submitted

    I usually struggle to find information on a User’s last login date.  This can only currently be found when you go to Org Admin > Bulk Actions > Users > Export Users > Domain Users.       Places this value could benefit from being added:Org Admin > Bulk Actions > Users > Export Users > Users and MembershipeSignature Admin > Users > Download Users

    0
    Jake Fascia
    Active Voice
    Forum|Forum|5 months ago
    Jake Fascia
    Active Voice
    Jake FasciaActive Voice

    Add 'Date Last Used' to the Templates Usage ReportIdea Submitted

    If the date the last time the Templates was used is available as data, it would make the ‘Template Usage Report’ more meaningful.  

    0
    Jake Fascia
    Active Voice
    Forum|Forum|5 months ago
    Jake Fascia
    Active Voice
    Jake FasciaActive Voice

    AI Data Controls page should always be visibleIdea Submitted

    I was told the reason we don’t see the AI Data Controls page is because we haven’t agreed to share our data with the AI tool via contract agreement.     This lacks transparency and our Risk team would feel more comfortable seeing that this option exists but is disabled.   I believe this page should always be visible but be grayed out (cannot modify the settings of this page) until the customer has agreed to share their data via contract agreement.    

    0
    Jake Fascia
    Active Voice
    Forum|Forum|5 months ago
    N
    Active Voice
    NBKPRActive Voice

    Add A Column on the Agreements page to show the origination of the agreement: Envelope Template or Web FormIdea Submitted

    Enhance the current Agreements and Send pages by adding a column to show the origination of the agreement template:  Envelope or Web Form.  Having this column would make updated the template easier.Name                Origination  Template          Progress                             Date           TypeAgreement 1     2/1/2026   Envelope              3 out of 7Agreement 2     2/2/2026    Web                     2 out of 5etc. See photo below 

    0
    N
    Active Voice
    Forum|Forum|5 months ago
    M
    Active Voice
    MarvinActive Voice

    Show additional recipient informationIdea Submitted

    We want to show additional recipient information (yellow space below).Our use case: Different users use different signature types (IDNow or Docusign ID Verification). Therefore we want to show the users signature type. Ideally there would be a field “Signature type”, but we could use any of the existing fields (e. g. “Job Title”).  

    3
    M
    Forum|Forum|5 months ago
    B
    Newcomer
    bsmithNewcomer

    Enable signature with ppa with QeSIdea Submitted

    Using a qualified electronic signature does not allow to choose from your own signatures. When required to sign with ‘ppa’ in front of your signature QeS can not be used in the current state (confirmed by support).It should be possible to select from all the signatures in the user profile the same way as it is without QeS.Alternativley the user should be able to add abbreviations like ‘ppa’ in front of the default signature.In the current state our general managers can not use DocuSign for signatures where they are legally obligated to sign with ‘ppa’.

    3
    M
    Forum|Forum|5 months ago

    Filter by category

    • All capabilities
    • All Capabilities

    Leaderboard

    Awarded Badges widget

    • 1st Question Posted
      goodrich4bkhas earned the badge 1st Question Posted
    • 1st Question Posted
      ame2026has earned the badge 1st Question Posted
    • 1st Question Posted
      MeganB88has earned the badge 1st Question Posted
    • 1st Reply Posted
      KatSaghas earned the badge 1st Reply Posted
    • 1st Question Posted
      Muhammad Alihas earned the badge 1st Question Posted
    Show All Badges
    Code of ConductAccessibility statement

    Docusign Community

    Code of Conduct