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

D

Forum|Forum|1 year ago

17210

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|8 months ago

3905

671 Ideas

Newest First

Most Replies

Most Votes

D

Danielle YNewcomer

Allow selection of account users in send to others option for report schedulingParked

When scheduling a report and selecting “Send to Others”, you have to type in full email addresses. It would be nice if the box would recognize account user emails and allow selection similar to when adding a signer to an envelope. Or maybe if the “Send to Others” option had a dropdown to select account users with radio buttons, etc?

2

M

Forum|Forum|11 days ago

Z

Zainab OlawoyinNew Voice

Request to Update Envelope Summary Behaviour Based on Document VisibilityParked

Currently when document visibility settings are applied, the envelope summary still reflects all events within the envelope. This means that recipients with access to only one document can still see details about other recipients, including witness information. Additionality, witnesses who only have access to a single document have no way of knowing who else can view the personal data they have entered in the eWitnesss pop-up at the start of the process. To address this, the following changes are proposedThe envelope summary should be dynamically tailored to reflect only the documents visible to the user. It should clearly indicate when the summary is a partial extract rather than a full envelope summary Witnesses should continue to have no access to the certificate or summary. These changes will help ensure that document visibility settings are respected throughout the signing process and that sensitive information is appropriately protected.

2

M

Forum|Forum|11 days ago

S

SGSBWNewcomer

Excel Date FormattingIdea Submitted

In reference to many issues users face, including within our own company, when an Excel file is uploaded to DocuSign to be sent out or to be signed, it automatically changes all the formats from the UK/EU date format of DD/MM/YYYY to the US format of MM/DD/YYYY. To comply with our Government policies, we need to have all the dates in all the documents be the same - not some in US format and some in the UK format, especially for a UK company. I have already been in contact with support regarding this and they told me to make an idea for it. There is a walkaround of changing the date field to a text field, but when formulas are involved, this makes it extremely difficult.

0

S

Forum|Forum|11 days ago

U

uclgpNewcomer

Default CC to receive the SIGNED copy onlyIdea Submitted

By default, can CCs receive the SIGNED copy only. Or provide an option to send either before or after signing.I know it is possible to configure the Signing Order with the CCs at the bottom, but that is an additional step to remember.

0

U

Forum|Forum|11 days ago

P

PaulFrancis2704New Voice

Customisable button on confirmation emailDelivered

As I understand it the button on the confirmation email received by a recipient when they have signed a document cannot be edited. When our emails first go out the button is a specific colour but the confirmation email with the button so that recipients can view the completed document cannot be customised and is just transparent.We would like to be able to customise this button as we can the initial email button so that we have continuity of brand in our communications.

2

M

Forum|Forum|11 days ago

E

EricBNew Voice

Auto-Place Fields are Below the AnchorsParked

We are using Auto-Place anchors for our dynamic documents. Unfortunately, the fields are not ending up at the Auto-Place anchors but instead are shifting down. We have been told by Support that this issue is known, but no further updates or changes have been planned for this specific behavior.Please correct this.

2

M

Forum|Forum|11 days ago

G

GiannipvNewcomer

Enable Envelope Metadata Conditions in Agreement Actions to automate document routingParked

1. Executive summaryPlease add “Envelope Data → Email Subject” and “Envelope Data → Envelope Name” as selectable conditions in Agreement Actions.This will let customers trigger post-signature automations, archiving, notifications, based on words that appear in the envelope title or subject line.2. Problem & current workaroundItem Detail Current gap The Agreement Actions condition builder surfaces only: • Document Custom Field • Envelope Custom Field • Recipient • Sender • Template Business impact • Cannot auto-route completed envelopes whose subjects include legal keywords such as “MSA”, “NDA”, or “SOW”. • Users must fall back on manual templates or custom-field work-arounds, adding friction and risk of human error. • Missed opportunity to drive adoption of Agreement Actions as a no-code automation hub. Workarounds 1. Template per agreement type: proliferation of templates, maintenance overhead. 2. Envelope Custom Field (“Subject”): must be filled in manually by end users; error-prone and unpopular with senders. 3. Proposed enhancementArea Proposal Scope list Add “Envelope Data” as a top-level scope in the Agreement Actions condition builder (consistent with other rule builders in DocuSign). Fields At minimum expose: • Email Subject (string) • Envelope Name (string) Operators Equals, is not equal to API Return the same schema in Rules API for programmatic rule creation. UX No net-new screens, just additional dropdown entries. 4. Value & ROIStakeholder Benefit Legal / Procurement Automatic classification & storage of agreement types (“MSA”, “PO”, “Amendment”) into dedicated shared folders IT / Security Fewer external integrations to audit; keeps data flow inside DocuSign & native cloud-storage connector. Senders Zero extra clicks, rule relies on the existing email subject they already fill in. DocuSign Increases stickiness of Agreement Actions, supports upsell to Business Pro/Enterprise tiers. 5. Usage exampleRule:Trigger – Envelope CompletedCondition – Envelope Data → Email Subject → contains → “MSA”Action – Archive to Google Drive → /Contracts/MSA/ Thank you for considering this enhancement. We believe it will unlock significant automation value for customers while reinforcing Agreement Actions as the central post-signature engine inside DocuSign. I’m happy to provide additional context or join a quick call if that would be helpful.

2

M

Forum|Forum|12 days ago

S

samala780

Upload a document via Box integration would be extremely helpful if it had a search function to search for file in BoxParked

Hi there, First of all, thank you for adding the scroll feature in the user interface for the Upload a document via Box integration (released May 7th, 2025). This has been a helpful new addition. We are hoping that you can expand on that new addition and add a search feature to the user interface for the Upload a document via Box integration as well. It would help with finding a file faster as sometimes there are far too many folders to scroll through for bigger organizations. Please reach out if you need more info and we can schedule a screenshare meeting to discuss further. Thank you in advance!

2

Forum|Forum|12 days ago

A

AnuerismNewcomer

Signature Block with Four Common TagsIdea Submitted

The majority of the commercial contracts we send for signature have a signature block for each signer containing the four common tags - Signature, Name, Title, and Date. Can a single tag be created or configured that includes all four tags stacked vertically so it can be dragged to the signature block rather than dragging each tag?

0

A

Forum|Forum|12 days ago

Z

Zainab OlawoyinNew Voice

Customisable Envelope Type ListParked

Hi team, It would be highly beneficial to enable customisation of the envelope type list within the envelope/template creation process. While the current ‘Other’ option provides flexibility, it introduces the risk of inconsistent or misspelled entries, which can negatively impact reporting accuracy. Introducing a controlled list will help maintain data integrity and streamline reporting

2

M

Forum|Forum|12 days ago

D

David.KafafianNew Voice

Navigator AI TrainingDelivered

I would suggest a core change to the way Navigator's AI functionality works to significantly improve performance: Users should be able to train the AI to look out for specific phrases / sections of agreements and extract the key finding into the structured metadata fields. E.g. our contracts may have custom implementation details in the Appendix of a certain form MSA, if I could create a box around that format, share a couple of examples, and identify for Navigator what the data to pull out from that is, and what new field to store it as, this would allow uses to be in the control of their own destiny and truly customize the Navigator experience.

2

Forum|Forum|12 days ago

Hengfeng GeHero

add email /seal type attributes for the sealsExisting Functionality

No the return for get seals only with sealName and sealDisplayName.{{baseUrl}}/v2.1/accounts/{{accountId}}/seals {"seals": [{"sealName": "10685326-884c-e54d-e4d3-187c8ebbe03b","sealDisplayName": "Testing for FreeLink"},{"sealName": "2a2412d4-7632-13-6d2a-97c48c58e9f3","sealDisplayName": "Legal Person Seal - Hengfeng Ge "},{"sealName": "ceec983d-5c92-cae9-b36c-afaedec170cb","sealDisplayName": "Demo Seal - Hengfeng Ge"}]} we call in the customer’s application do know which seal is who’s. so we need add a mapping table like email/sealName/sealDisplayName. hope can add email /seal type attributes, so we no need add mapping table. 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.

2

Forum|Forum|12 days ago

mshealyEstablished Contributor

esig-ability to migrate a report from demo to prodParked

Right now the only way to get a report in prod from demo is to rebuild it manually. That isn’t very efficient.Need a way to download in DEMO then upload into prod.

2

M

Forum|Forum|12 days ago

C

clairemccloskeyDigital Collaborator

Request for senders to receive notifications when recipient signs a documentUnder review

It would be helpful if senders to received a notification when recipient signs a document, not just when they view it

5

M

Forum|Forum|12 days ago

Scott.NiemanTroubleshooter

Add documentId and documentIdGuid to response body when adding template to envelopeExisting Functionality

Returning the templateId is not good enough. It is normal RESTful best practice to include newly minted identifiers that may be useful for subsequent API calls.In this case, the documentIdGuid is needed for the Agreement Template Builder to update the Sender Fields with values.

3

Forum|Forum|12 days ago

A

auguyNew Voice

Audit log enhancementParked

The information in the audit logs is light on information. To make these logs more useful an enhancement to the logs would be great, such as the following in order of importance…Source IP. What IP were the changes made from? Unique identification of users by GUID or other identifier. Where there’s two accounts with the same name, the audit log just shows the name so which audit logs relates to which of the accounts? Browser user agent. An indication of what was used.Thoughts?Please add other info you’d like to see in audit logs.

3

M

Forum|Forum|12 days ago

H

Han.ChenActive Voice

Change misleading wording in Download users pop-upIdea Submitted

The interface for Download Users for admins can be a bit confusing, as there’s no selection box at all on User page.

0

H

Forum|Forum|12 days ago

W

wshields987New Voice

Inconsistent period in "document has been completed" emailDelivered

The "document has been completed" email has internally inconsistent punctuation between other notification emails, and depending on how signature is performed. All other notification emails contain a period after the initial sentence. Furthermore, If you sign "in person" you get a period, however electronically, no period. I have attached screenshots of relevant emails for comparison.

2

J

Forum|Forum|12 days ago

N

Nick.LernerNew Voice

DocuSign should make Drafts Easier to AccessParked

I would love it if one of the action buttons on the top of the screen is a direct link to my DocuSign drafts on the home page. There is no direct way to access my drafts, that I’m aware of, unless I click one of the four options (Action Required, Waiting for Others, Expiring Soon, and Completed), then click Show More on the left pane, and then the drafts finally show up. Other than Completed envelopes, the most often envelopes I’m in need finding are Drafts. It would be nice to have a direct link.

2

J

Forum|Forum|12 days ago

Scott.NiemanTroubleshooter

Agreement Template Builder (DocGen) -- allow recipient Fields (not just sender Fields) to enable the recipient to complete a dynamic table and other recipient fields prior to signatureParked

Business Case: Our attestation process for sustainability programs (Carbon, Methane) includes data collection of farming practices for a specific calendar year, with signature /approval of the data collection (the attestation). We have been working with ATB, but we cannot seem to pre-populate the dynamic tables with a subset of the sender fields and prompt the recipient to complete the missing information (highlighted in yellow).Ask: We believe the Template Assistant could be updated with a drop list choice that indicates that the DocGen Field is either a senderField or recipientField. This would also exist in dynamic tables (currently only simple text is supported). When recipientField is selected, the recipientId property is added to the JSON.{ "docGenFormFields": [ { "documentId": "6331379d-67fc-4957-9c05-451e6f629627", "docGenFormFieldList": [ { "label": "RetailerName", "type": "TextBox", "required": "False", "name": "RetailerName", "value": "Harvest States Coop" }, { "label": "FarmerBusinessDBAName", "type": "TextBox", "required": "False", "name": "FarmerBusinessDBAName", "value": "Crops R Us" }, { "label": "FarmsteadName", "type": "TextBox", "required": "False", "name": "FarmsteadName", "value": "Grandmas Farm", "description": "The name of the farmstead" }, { "label": "FarmerEmail", "type": "TextBox", "required": "False", "name": "FarmerEmail", "value": "stnieman@landolakes.com" }, { "label": "Current_Year_Reenrollment", "type": "TableRow", "required": "True", "name": "Current_Year_Reenrollment", "rowValues": [ { "docGenFormFieldList": [ { "label": "FieldName", "type": "TextBox", "required": "True", "name": "FieldName", "value": "Davis" }, { "label": "FieldUUID", "type": "TextBox", "required": "True", "name": "FieldName", "value": "daa0fa1b-bb5d-42df-a9d2-244b3bfe71bb" }, { "label": "CurrentYearCropType", "type": "TextBox", "required": "True", "name": "CurrentYearCropType", "value": "", "recipientId": "1" }, { "label": "TillageChanges", "type": "TextBox", "required": "True", "name": "TillageChanges", "value": "", "recipientId": "1" }, { "label": "BiomassResidueRemoval", "type": "TextBox", "required": "True", "name": "BiomassResidueRemoval", "value": "", "recipientId": "1" }, { "label": "FertilizerChanges", "type": "TextBox", "required": "True", "name": "FertilizerChanges", "value": "", "recipientId": "1" }, { "label": "PlantedCoverCropsBeforeWinter", "type": "TextBox", "required": "True", "name": "PlantedCoverCropsBeforeWinter", "value": "", "recipientId": "1" } ] }, { "docGenFormFieldList": [ { "label": "Field", "type": "TextBox", "required": "True", "name": "Field", "value": "Nelson 40" }, { "label": "FieldUUID", "type": "TextBox", "required": "True", "name": "FieldName", "value": "fd0ba46a-567f-4215-8686-273b98ee36b6" }, { "label": "CurrentYearCropType", "type": "TextBox", "required": "True", "name": "CurrentYearCropType", "value": "", "recipientId": "1" }, { "label": "TillageChanges", "type": "TextBox", "required": "True", "name": "TillageChanges", "value": "", "recipientId": "1" }, { "label": "BiomassResidueRemoval", "type": "TextBox", "required": "True", "name": "BiomassResidueRemoval", "value": "", "recipientId": "1" }, { "label": "FertilizerChanges", "type": "TextBox", "required": "True", "name": "FertilizerChanges", "value": "", "recipientId": "1" }, { "label": "PlantedCoverCropsBeforeWinter", "type": "TextBox", "required": "True", "name": "PlantedCoverCropsBeforeWinter", "value": "", "recipientId": "1" } ] }, { "docGenFormFieldList": [ { "label": "Field", "type": "TextBox", "required": "True", "name": "Field", "value": "Greenbelt" }, { "label": "FieldUUID", "type": "TextBox", "required": "True", "name": "FieldName", "value": "fd0ba46a-567f-4215-8686-273b98ee36b6" }, { "label": "CurrentYearCropType", "type": "TextBox", "required": "True", "name": "CurrentYearCropType", "value": "", "recipientId": "1" }, { "label": "TillageChanges", "type": "TextBox", "required": "True", "name": "TillageChanges", "value": "", "recipientId": "1" }, { "label": "BiomassResidueRemoval", "type": "TextBox", "required": "True", "name": "BiomassResidueRemoval", "value": "", "recipientId": "1" }, { "label": "FertilizerChanges", "type": "TextBox", "required": "True", "name": "FertilizerChanges", "value": "", "recipientId": "1" }, { "label": "PlantedCoverCropsBeforeWinter", "type": "TextBox", "required": "True", "name": "PlantedCoverCropsBeforeWinter", "value": "", "recipientId": "1" } ] } ] } ] } ]}Attempts:If we don't use the docgen API endpoints and Use the template from the portal, a CSV is prompted. If we do populate sender fields with the farmer's arable field names, the CSV prompt is no longer an option. We tried omitting the dynamic table, and the upload option is not presented to the recipient.We tried the WebForms, thinking the WebForm may prompt the recipient row-by-row, but it seems that WebForms currently does NOT support ATB templates.Adding recipient tabs are not possible with the dynamic table as xy coordinates are not returned with the PUT call, therefore we don't know where to place the tabs in the cells of the dynamic table.PUT {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/docGenFormFields

2

Forum|Forum|13 days ago

D

Devin Moore FMNewcomer

Delay signature to prevent user from signing too earlyExisting Functionality

I couldn't find a solution to this issue on the Docusign Community, so I'm offering a suggestion. We need to prevent signers from signing agreements too early. The current recommendations like "Send Later" or adding a delay aren't helpful because "Send Later" doesn’t allow our recipients to view documents immediately. Adding a delay doesn't work with our use of merge field data, causing errors (see image below).We suggest Docusign provide an option to add a validation or setting that prevents signatures until a specified time, such as X days or Y hours. Example: Signer should not sign until 2 weeks from when they receive the Docusign envelope for a “consideration period”. If they sign too early we need to void their agreement and send a new one.

5

M

Forum|Forum|13 days ago

mshealyEstablished Contributor

esig-Allow addition filters for esig reportsParked

Envelope Status should allow to choose which status’s you want to include. Not just one. In other words if I want it to include SENT and DELIVERED only.

2

M

Forum|Forum|13 days ago

C

Charlene.CBUrbanNewcomer

Create a new option for dropdown - YOUR SIDE: Referral (When creating a new room!)Parked

Would love to see the option to choose: Referral under your side when creating a new room. That way when overseeing many rooms as a administrator the room will have this label, creating efficiency and organization for anyone using this program for Real Estate.

2

M

Forum|Forum|13 days ago

M

Mike CunninghamNewcomer

Vague Error: The response assertion is missing a required attributeParked

When we receive a SAML response assertion from an Identity Provider and it’s missing one or more of the required attributes, the error could be more specific. Currently, it just says: “Something went wrong The response assertion is missing a required attribute”We recommend adding the names of the missing attributes in the error message. It would save time with troubleshooting.For example, it could read as follows: “Something went wrong The response assertion is missing a required attribute: <Attribute Name>”

2

M

Forum|Forum|13 days ago

S

shaylynstefNew Voice

Ability to Add Numerous Fields at Once?Existing Functionality

Just wondering if you could come up with a way to add in numerous fields at once? Such as a field that has the signature and date underneath? Custom fields don’t work as each document looks different and there’s no where consistent to place these fields we use together all the time. Or to create a type of customizable DocuSign “stamp” where you can add in what fields you want?For examples, I have two types of formats I use all the time. Usually I stack them but it’s a lot of pressing when you’re dealing with many documents. So to have one stamp that is the following fields:Approved By:SignDate SignedThen another that is just:SignDate Signed

2

M

Forum|Forum|13 days ago