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

2 years ago

23950

Filter by Idea status

Filter by category

1117 Ideas

Most Replies

Most Votes

Newest First

tnewmanNewcomer

Create a Folder for Sent EnvelopesDuplicate

Picture it: the envelopes you’ve sent, in the order they’ve been sent, regardless of current status. You could quickly identify envelopes that have been stalled in the process and follow up on those. I suspect little novel code would be required to implement such a feature.

6 days ago

sahil.shettyNewcomer

Recipient-specific masking of field values during signing, with full values on the completed documentIdea Submitted

Use caseWe’re an ISV in financial services. We send multi-signer envelopes through the eSignature REST API for brokerage account documents (joint, trust and entity accounts). Each signer’s sensitive data (SSN/Tax ID, date of birth) is prefilled on a shared document that every owner or trustee signs.RequirementEach signer should see their own sensitive values in full so they can confirm them. Every other signer on the envelope should see those values masked, for example ***-**-6789 for an SSN or the year alone for a DOB. The completed, signed document must contain the full, unmasked values. Custodians and back-office teams need the complete signed form to process the account.Why existing features don’t meet itconcealValueOnDocument (“Hide text with asterisks”) hides the value from other signers, but it also masks it on the completed PDF. The value can then only be retrieved from form data, and custodians won’t accept that. It isn’t supported on preFillTabs, and it masks the whole value with no option to show part of it. Default prefill visibility, or the “write initial value for all recipients” setting, controls when other signers see a value, not whether they see it. Signers later in the routing order still see earlier signers’ data. Document visibility works per document. Here, all owners sign the same page.Requested enhancementA tab-level property, such as maskForOtherRecipients, with an optional partial-mask pattern (for example, last 4 digits). The value is masked for every recipient except the tab’s assigned recipient during signing, and written in full to the completed document and certificate.ImpactThis applies to any regulated industry where several signers share one document and each signer’s PII must stay private from the others but complete on the executed record.

6 days ago

amillerNew Voice

Replace option needed in IAMIdea Submitted

When a document is partially signed in Docusign and countersigned outside Docusign, it would save significant time to have a dedicated Replace option where we can replace a document in IAM with the fully executed version. It takes significant unnecessary time to (1) Upload the fully executed document as a new agreement, (2) Delete the prior version, if appropriate, then (3) Reapply any required metadata, tags, or agreement-set assignments. This is not a scalable solution when working with a large volume of agreements.

7 days ago

awe1Newcomer

Provide option to opt-out of Docusign promotional emails for an entire accountIdea Submitted

I would like an admin, account-wide, setting that allows me to turn off all promotional emails from Docusign for users in my account. The emails are distracting and not part of a process or work item, so it brings a lot of confusion for our envelope signers. This has received negative feedback from our users and sours the entire Docusign experience. Currently, each user has to ‘Manage Preferences’ on the promotional emails.

8 days ago

khulslanNewcomer

add ability to disable email attachments at the template levelIdea Submitted

It would be great to be able to turn off email attachments at the template level. Some templates collect have PII and we don’t want to email that data. But other forms that don’t have sensitive information need to be attached in an email. Using asterisks to hide the PII data isn’t ideal for our users that need to see the completed form for their processing. Currently the only solution is to have 2 different accounts. One to house sensitive forms and another for non sensitive forms. Having this setting at template level would eliminate this need.

8 days ago

alessandra.souzaNewcomer

Retiraram o atalho de Visualização Necessaria e isso é muito ruimIdea Submitted

a nova versão já não permite usar a versão anterior e não tem a opção de verificarmos os contratos pendentes de visualização, ele se mistura em todos os outros, e corremos o risco de não liberar um contrato. Para o nosso negócio isso é muito ruim.

8 days ago

SheilaPNewcomer

Sending Experience options in DAL eSignature Envelope Template settingsParked

The sending experience options within Docusign Apps Launcher (Salesforce) aren’t flexible enough. We have agreements with approved terms and conditions language that the sender is not authorized to manipulate in any way. Our senders in this case should only have access to attach the document (either from the Salesforce record or upload the PDF) and assign the recipient. They should not have access to add any additional input or merge fields (the correct signer tags are already included in the source documents). We’d like to see a sender experience option in the envelope template settings that bypasses the full featured “prepare & send” page. It appears my only option to accomplish this today is a completely customized Apex Toolkit code solution.

8 days ago

alexandrefurNewcomer

Automatically populate the recipient's WhatsApp number when sending an envelope.Idea Submitted

Currently, when sending an envelope using WhatsApp delivery, DocuSign does not automatically populate the recipient's phone number from the saved contact information. Even when the recipient's phone number is already stored in the DocuSign address book, users must manually enter the number every time an envelope is sent. Automatically populating the phone number from the saved contact record would save time, improve efficiency, and reduce the risk of data-entry errors.

8 days ago

PslimNew Voice

IAM - Unable to revert those changes within the AI-Assisted Review chat experience.Idea Submitted

Business Case: Revert Changes in AI-Assisted ReviewExecutive SummaryAfter uploading an NDA document, initiating an AI-Assisted Review, and submitting edits, users currently cannot revert those changes from within the AI-Assisted Review chat experience. The absence of an automated or one-click “Revert Changes” action creates operational risk, increases recovery effort, and may reduce user confidence in the review workflow.This business case proposes introducing document versioning and a clear revert capability within the AI-Assisted Review chat panel. Users should be able to undo the latest submission or restore a prior document version without manually recovering the original document or repeating the review process.Business ProblemAI-Assisted Review allows users to submit document edits based on AI-generated recommendations. However, once edits are submitted:There is no one-click option to undo or revert the changes. Users must manually restore the original document or recreate the previous version. Mistakes may remain undiscovered until after the document has been circulated or approved. Legal and business users may hesitate to use AI-assisted editing for sensitive agreements. Support teams may receive avoidable requests to recover or restore documents.This is particularly important for NDAs, where wording changes can affect confidentiality obligations, exclusions, term length, permitted disclosures, and liability exposure.Business ImpactThe current limitation creates several risks:User experience riskUsers expect document-editing workflows to provide a safe recovery mechanism. Without one, a single incorrect submission can make the experience feel irreversible.Legal and compliance riskA user may unintentionally accept an inappropriate change and lack an immediate way to restore the prior wording. This increases the possibility that an incorrect version progresses through approval or signature workflows.Adoption riskLegal, procurement, and sales teams may avoid AI-Assisted Review if they believe experimentation could permanently alter a document.Operational inefficiencyUsers and support teams may spend time locating previous files, comparing versions, and manually restoring content.Trust riskThe inability to reverse AI-generated or AI-supported changes undermines confidence in the reliability and controllability of the product.Proposed SolutionAdd a “Revert Changes” capability to the AI-Assisted Review experience.The feature should allow users to:View the current document version and the version created before the submitted edits. Revert the latest submitted changes with one action. Confirm the revert before it is applied. Continue the AI-Assisted Review from the restored version. Access a version history for older changes, where appropriate. See clear status messaging indicating which version is active.The product should preserve the original uploaded document and maintain each submitted edit as a recoverable version rather than overwriting content irreversibly.Recommended User ExperienceWithin the AI-Assisted Review chat panel, provide:A visible “Revert Changes” action after edits are submitted. A confirmation message, such as: “This will restore the document to the version before the last submitted edits. Your current changes will remain available in version history.” A success notification after the revert is completed. An optional “View Version History” link. Appropriate permissions and audit logging for revert actions.The revert action should be disabled when no prior editable version exists.ScopeIn scopeReverting the most recent submitted edit set. Preserving the original uploaded document. Maintaining document versions or snapshots. Displaying the active version in the AI-Assisted Review experience. Recording revert activity in the audit trail. Supporting common document formats used in NDA workflows.Potential future scopeReverting individual edits. Comparing any two document versions. Restoring a specific historical version. Undoing multiple edit submissions. Role-based controls for reverting approved or locked documents. Integration with broader document lifecycle and approval workflows.BenefitsImplementing this capability would:Reduce the risk of unintended contractual changes. Improve user confidence and trust in AI-assisted editing. Encourage adoption among legal and business teams. Reduce manual recovery work and support requests. Improve the overall quality of the review experience. Provide a stronger foundation for document version control and auditability.Success MeasuresThe following measures can be used to evaluate the feature:Reduction in support tickets related to restoring edited documents. Increased completion rate for AI-Assisted Review workflows. Increased usage of AI-assisted editing after release. Reduction in abandoned review sessions. Number of successful revert actions. Time required to recover from an unwanted edit. User satisfaction and trust scores for AI-Assisted Review.Risks and MitigationsRisk Mitigation Users revert changes unintentionally Require confirmation and provide clear messaging Version storage increases system costs Apply retention policies and configurable version limits Reverted content creates workflow confusion Clearly label the active version and show version history Revert conflicts with approvals or signatures Restrict reverting locked or finalized documents Users expect granular undo Clearly define initial scope as reverting the latest submitted edit set Implementation ConsiderationsThe solution will require:A document versioning or snapshot mechanism. Metadata linking edits to the AI-Assisted Review session. Revert APIs and backend validation. UI updates to the AI chat panel. Audit logging for edit and revert actions. Permission checks for documents in approval or signature workflows. Testing across supported document types and concurrent editing scenarios.RecommendationPrioritize the addition of a one-click “Revert Changes” capability for AI-Assisted Review. The feature addresses a clear usability, legal, operational, and adoption risk with a relatively focused product enhancement.The recommended first release should support reverting the latest submitted edit set while preserving all prior versions and recording the action in the audit trail. More advanced version comparison and granular undo functionality can be evaluated as future enhancements.ConclusionAI-Assisted Review must provide users with control over the changes they submit. Without a reliable revert mechanism, users face unnecessary risk when reviewing sensitive legal documents such as NDAs. Introducing version-aware editing and a clear “Revert Changes” action will improve safety, trust, efficiency, and adoption while establishing a stronger foundation for future document collaboration features.

9 days ago

jRinconNewcomer

Add a manual Thank You note for recipients after signingIdea Submitted

Add an option to send a quick closing/thank you note for recipients who have signed a document.Example: I receive a signature from a customer. By clicking on a button “Send Thanks/Closing” a brief (or long) closing message (customizable) is sent to the customer (thus encouraging future signature requests).Thank you.

9 days ago

HennaNewcomer

Add a "Processed" / "Archived" status for completed agreements per users choiceIdea Submitted

I am quite new user, and there might be things that I do not yet know, but I haven’t been able to find a solution for this.Currently, DocuSign marks an agreement as Completed once all signatures have been collected. However, often additional work is still required after signing, such as downloading documents, filing them in internal systems, or sending them to external parties (not signatories). (However, my question is not about integration or automatic archiving files outside the tool some other location set by organisation).As a result, the All Agreements/Completed view contains both:Newly completed agreements still requiring action Completed agreements that have already been fully handledWhile folders can help organise agreements, they do not remove the items from the All Agreements view, just add “tag” of the folder name in the row. As agreement volumes grow, the All Agreements (Completed) view becomes increasingly cluttered because newly completed agreements and agreements that have already been fully processed appear together. This makes it difficult to quickly identify how many and which completed agreements still require follow-up actions.It would be very helpful if this could be added:A user-controlled Processed or Archived status, and/or A way to hide/filter agreements that have already been fully handled by the sender.This would make it much easier to manage high volumes of agreements and distinguish between "signatures completed" and "all follow-up actions completed".

9 days ago

Jake FasciaTroubleshooter

Template Reporting EnhancementsIdea Submitted

Issue: Our organization has hundreds of actively used Templates and understanding who has access is impossible with the current Template Report because it does not show which Groups / Users have access. Resolution: Enhance the Template Report to include a column for ‘Groups’ to show who has access.

12 days ago

MarielMActive Voice

Audit ReportsParked

Need audit reports for the following information:to view who has access to each Shared Folder (what folders each user/user group has access to) consolidated report to view who has shared access to other users’ envelopes who has access to what templates (what templates each user/user group has access to) Sent envelopes and their sent by methods (i.e., bulk send, mobile, api, etc.) Or a high level on the account where we can see what send by methods are mostly used Identify bulk send envelopes and their status/who sent it/ date sent/ recipient etc.Overall these are useful for security audits performed internally to ensure access is restricted appropriately and to inform us how we are utilizing the tool.

12 days ago

DanielaPuglieseNewcomer

Prevent External Updates of Recipient Company InformationIdea Submitted

Business NeedWe request a setting that allows organizations to prevent external DocuSign accounts from modifying or populating recipient profile/contact information, specifically the standard Company field, when signature requests are sent from external organizations.Current BehaviorWhen a recipient completes the standard Company field during a signing process, the value may be stored and reused in future envelopes associated with the same email address. If an envelope is sent from an external DocuSign account, the external organization can indirectly cause updates to information that may later appear in subsequent signing experiences.Currently, there is no administrative setting that allows organizations to:Block updates to the Company field originating from external DocuSign accounts. Lock recipient profile information against external modifications. Define trusted sources authorized to update recipient contact information. Disable the persistence of externally provided Company values.Business ImpactThis behavior creates governance and compliance concerns for organizations operating in regulated environments.Specifically:Company information can be overwritten by individuals outside the organization. Data displayed to users may originate from external sources without validation. Internal administrators have no visibility or control over how these values are populated. Incorrect company information may be inherited across future signing transactions. Organizations cannot ensure the integrity and provenance of recipient profile data.For our organization, it is not acceptable that information such as the Company field can be freely overwritten by external users and subsequently propagated without any control or validation by the recipient's organization.Requested EnhancementIntroduce one or more administrative controls, such as:Prevent external updates to recipient profile/contact information. Block persistence of Company values provided through external envelopes. Allow only internal senders to update recipient contact data. Enable administrators to lock the standard Company field. Provide auditing and reporting of profile changes and their originating sender organization.Expected BenefitThis enhancement would improve:Data governance Regulatory compliance Information integrity Auditability Administrative control over recipient profile datawhile maintaining flexibility for organizations that wish to continue using the current behavior.We believe organizations should have full administrative control over recipient profile data. Information such as the Company field should not be editable or persistable through external DocuSign accounts without an explicit tenant-level policy and administrative consent.Thank youDaniela

12 days ago

Reynaldo1Newcomer

I've been building a post quantum hashing certificates for docusign envelopes using AlgorandIdea Submitted

The idea Give completed envelopes a proof that (1) uses a post-quantum signature and (2) can be verified years from now without DocuSign's servers. As a first step, expose a stable SHA-256 of the completed document in the eSignature API, so integrators can anchor and verify it themselves. Why it matters - The certificate of completion and the PDF seal use RSA, which a large enough quantum computer would break. NIST finalised ML-DSA (FIPS-204) in 2024, and US federal guidance (CNSA 2.0) expects the move to post-quantum cryptography in the early 2030s. Agreements signed today will need to verify in 2040. - There is no stable fingerprint to build on. Downloading the same completed envelope twice (documents/combined?certificate=true) gives two different SHA-256 hashes. The XMP dates, the PDF /ID and the adbe.pkcs seal change on every download, so a hash taken today never matches a copy downloaded later. I built a working prototype to show it can be done today - DocuSign Connect sends envelope-completed. The service confirms the status through the API, downloads the combined PDF once, and hashes it. - The hash is anchored on the Algorand public ledger, and a receipt is signed with ML-DSA-65 (post-quantum). The receipt records DocuSign's completion time and the capture time. - The signer gets a private link to that exact copy and can verify it in the browser or with an open-source tool, without trusting DocuSign or my service. Change one byte and verification fails. - In three sandbox test runs, completion to anchored took 23–26 seconds, with no Connect delivery failures. Only hashes go on-chain. Try it in under a minute (sandbox, free, no account or email needed; you sign a demo contract with embedded signing): https://pq-verifiable-archive.vercel.app/try Open-source code and a guide for running it on your own sandbox: https://github.com/m-reynaldo35/pq-verifiable-archive Step-by-step test write-up: https://github.com/m-reynaldo35/pq-verifiable-archive/blob/main/docs/live-tests.md

12 days ago

mingNewcomer

Option for "Attach documents to completion email"Idea Submitted

Is there an option that allows the sender to decide whether to attach documents to the completion email on a per-envelope basis?

13 days ago

PslimNew Voice

IAM - Tool to convert Web Form to Agreement Desk Request FormIdea Submitted

Automate the conversion of Webforms into Request Forms using AI, eliminating tedious manual data entry. This would enable captured external data to flow seamlessly into internal systems for efficient record-keeping, reporting, and charting.

13 days ago

herbert500Newcomer

Conditional visibility for sender fields in the Document Generation pre-fill form (Agreement Template Builder)Idea Submitted

We use the Agreement Template Builder to build one dynamic template for employment contract amendments instead of maintaining many separate templates. Each optional section is controlled by a sender dropdown field (Yes/No), and a rule shows or hides the section in the generated document. This works well.The problem is the sender pre-fill form. It always shows all sender fields, including the data fields inside sections that are hidden by a rule. For example, if the sender selects "No" for "Change of job title", the fields "Start date" and "New job title" are still shown in the form.This leads to two issues:The form becomes long and confusing, because senders see fields that are not relevant to their case. We cannot mark these fields as required. If we do, senders must fill them even when the section is not used. So we make them optional, which means nothing prevents a sender from forgetting a field when the section is used.Requested feature: Allow sender fields in the pre-fill form to be shown or hidden based on the value of another sender field, using the same rule logic that already exists for document content. Ideally:Fields linked to a rule are only shown when the rule applies. Such fields can be required, but only when visible.This would make dynamic templates much easier to use and reduce errors before sending.A related request for the Word add-in exists here, but the answer there only refers to conditional document content, not to the pre-fill form: https://community.docusign.com/ideas/enhancement-request-conditional-logic-for-form-fields-25032

14 days ago

mshealyEstablished Contributor

Formula fields in eSig that are collaborativeIdea Submitted

I have a formula field that takes fields S2, S2 and S3 and sums them.I need fields S1, S2 and S3 to be collaborative. Currently, I get an error.I noticed here that the functionality isn’t available to do that.Please change this so that it is allowed.https://support.docusign.com/s/document-item?language=en_US&rsc_301&bundleId=gbo1643332197980&topicId=hck1578456359426.html&_LANG=enusThanks

14 days ago

VirgiViNewcomer

Assign Agreement Sets During Envelope CreationIdea Submitted

Currently, Agreement Sets can only be assigned after an envelope has been completed and the signed agreement has been ingested into Agreement Manager. This creates an additional manual step and may delay access to agreements by the appropriate stakeholders.It would be valuable to allow users to select or assign an Agreement Set directly when creating and sending a DocuSign envelope. Once the envelope is completed and the agreement is automatically uploaded to Agreement Manager, the document would automatically be placed in the designated Agreement Set.Organizations that rely on Agreement Sets to manage access and organize agreements would benefit from having completed agreements automatically routed to the correct set based on configuration made at the time the envelope is sent.

16 days ago

Mike_KNewcomer

Forwarded envelopes should inherit account settings for reminders and expirationIdea Submitted

This idea came as a result of a support case that I opened. We discovered that forwarded envelopes within an account do not have the customized account settings for reminders and expiration applied to them. Forwarded envelopes instead have the DocuSign default settings of no reminders and 120 day expiration. Support stated the product team confirmed that “this behavior is expected by design”. This contradicts the wording on the Reminders and Expiration settings page that states “Set default reminders and expirations for all envelopes sent from this account.” Support suggested that we enable sender override which is not something that we can do.My suggestion is that forwarded envelopes behave in the same way as new envelopes. Currently there is nothing that indicates forwarded envelopes work any differently than new envelopes. Or since this is “expected by design”, allow the admin to configure the settings for forwarded envelopes instead of applying DocuSign defaults with no way to change them.

16 days ago

Mel HabipNew Voice

Distinguish re-sent links upon expiry from net-new links sent originallyIdea Submitted

Currently, if a user opens older “completed” docusign email link, it sends a new link to the same recipient (email address) with a new link. That email looks exactly like a brand new “completed” email, as if the documents were just completed on DS. In an enterprise situation, this causes issues because of automations and volume of emails. For instance, we receive over 100+ of these emails a day in the same inbox, so it’s borderline impossible to pick the right one when it comes through, and it still ends up going through various circles/automations before it does that, becuase there is no way to tell this is an older document. Ideally, these would be differentiated, even if it’s very little, with some indication in the subject or email body that this is a “new link for an older envelope” (or something to that effect).

16 days ago

ali-hasNewcomer

Access Code Requirement for SenderIdea Submitted

Our company requires an access code for every envelope sent. While this can currently be enforced at the template level, there is no administrative setting to enforce it across an entire organization or account. We would like an account level toggle that requires an access code on all outgoing envelopes.

19 days ago

GiampaoloNewcomer

To sign directly a document with a QESIdea Submitted

The DS’ shortcut Envelope > Sign a Document works only with a SES: Simple Electronic Signature.It would be useful to use the same path and be able to select the kind of signature. Otherwise, to sign a document by myself with a QES I have to create an envelope and execute the whole process.Any thoughts? G

19 days ago

MarielMActive Voice

Report to identify Documents stored in Envelope TemplatesIdea Submitted

It would be useful to know what documents (by document name) are linked to each envelope template. There isn’t any report that shows the linkage between envelope templates and the documents linked to them. Having this inventory helps with document clean up and updates needed, especially when transitioning over to document templates.

20 days ago