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

Jake FasciaActive Voice

Completed Envelopes Unable to Access when Using Shared Access instead of Shared 'Dept' UserIdea Submitted

In short - In an Org-managed + SSO environment, only recipients involved in the signing process can access Completed envelopes through a Docusign email, even if they have been granted Shared Access with the sender of the envelope. Processors of the Completed envelope receive an authentication error when they click the link in the email, and they must login to Docusign environment and go through all the steps to locate the envelope with Shared Access. Solution - Users with Shared Access should be able to access the Completed envelope if the Sender/Recipient is a User they were granted access to. Or the ability to lighten the restrictions on accessing Completed Envelopes could be added to the Admin Settings. Background - Our Mortgage department asked for a Department User and they would all share the login credentials. I thought I could replicate the experience with Custody Transfer + Shared Access.With all their envelopes being sent on behalf of the Department User, they all receive the email notifications but only the individuals directly involved in the signing process are able to access the Completed envelope. (No issues while signing in process)With the error message and inconvenience of finding the envelope through Shared Access, the Mortgage department would rather login manually to the Department User so they can access the envelope directly from the email link.

Forum|Forum|15 days ago

AMWNewcomer

Enable eml Format eMail for drag and drop into EnvelopesIdea Submitted

The new Microsoft Outlook email format is eml. Currently we cannot drag and drop them into an envelope as it is not a supported Format and we need to save the email first as PDF to upload it. To facilitate the upload, please enable eml format for drag & drop/upload into an envelope.

Forum|Forum|15 days ago

Javier.DominguezNewcomer

Include Decline Reason in Email Notifications Sent to CC RecipientsIdea Submitted

Hello,I would like to suggest an enhancement regarding envelope decline notifications.Currently, when a signer declines an envelope and provides a reason, the decline reason is included in the email notification sent to the sender. However, recipients who are included in the workflow as CC recipients only receive a notification that the envelope was declined and do not receive the actual reason entered by the signer.This can create challenges in organizations that use a shared or service account as the sender (for example, through an integration), while business users and stakeholders are added as CC recipients to stay informed about the envelope status.Suggested enhancement: Provide an account-level or envelope-level option that allows the decline reason entered by the signer to be included in the decline notification emails sent to CC recipients.Benefits:Improved visibility for all stakeholders involved in the signing process. Reduced need for manual follow-up with the sender. Better support for integrated and automated DocuSign environments that use service accounts. Faster resolution of issues that caused the signer to decline the document.Ideally, administrators could enable or disable this behavior according to their organization's security and privacy requirements.Thank you for considering this enhancement. I believe it would improve transparency and communication throughout the signing workflow. **information removed due to PII**

Forum|Forum|15 days ago

DebKoscinskiNew Voice

Docusign Popup after moving envelope to folderIdea Submitted

PLEASE add a turn off box for the new notification every time you move an envelope to another folder as it is SUPER ANNOYING!! It stays there until you close out EVERY popup notification.

Forum|Forum|16 days ago

clawqerNewcomer

Allow new support requests from deleted email threadsIdea Submitted

When a support request created from an email thread is deleted, any subsequent replies to that same thread are ignored and do not create a new request. This can easily lead to important customer responses being missed.It would be helpful if deleted requests no longer blocked new request creation from the same email thread, or if there were an option to automatically create a new request when a reply is received after the original request has been deleted. Alternatively, allowing related requests to be linked together would also improve the workflow.This would help prevent lost customer communication while preserving the context of the conversation.

Forum|Forum|16 days ago

Matt CNewcomer

Enable System Sender in the GUI instead of having to program the APEXIdea Submitted

It is a good feature to have but hidden behind Apex Tool kit. While this can be done, Maintaining the UI is easier for team with less dev experience.

Forum|Forum|17 days ago

FoxiCleopatra4021Newcomer

Adding fields while in a signing sessionIdea Submitted

As notaries we should be able to adjust, edit, or add fields while inside of a live signing session with a signer. It has never made sense to me that I can’t do this on Docusign. I love the notary platform, I enjoy how easy it is to use, and it is my platform of choice in general; however, the ability to adjust, edit or add a field during a session is a feature of most other notary platforms, and I've not understood why this isn't the case for Docusign.It would save a lot of time to see that a field is missing in the session and be able to place it right away, instead of either ending the session to correct it and starting over, or completing the session then creating another one to correct and sign again. Especially for something like a loan closing package that often has 100+ pages to filter through to place these fields, it’s only natural to accidentally miss one and catch it during the session. Please add the ability to adjust, edit, or add fields while inside of a live signing session with a signer.

Forum|Forum|18 days ago

maiConversation Starter

【IAM】【契約期限管理】Upcoming renewalsのcsvにセットを反映Idea Submitted

契約の期限管理として、Upcoming renewalsのcsvから、各部署へのヒアリングシートを作成しようと考えています。csvにあるsetの列が空欄というのがデフォルトのようですが、ここにセットのID？を反映していただけると、ヒアリングシートを作成する際に、どこの部署が管轄している契約なのか、把握ができます。逆にここが空欄だと、向こう12か月（適宜設定）に通知がくるすべての契約書がcsvに反映されてしまい、せっかくのセット機能が有効活用されていないように思います。

Forum|Forum|18 days ago

Laurie.LeeNewcomer

When you have a system glitch, outage, or dysfunction of any kind, create an alert that would go out universally to adminsIdea Submitted

Be proactive in alerting customers (at least account administrators) that Docusign is glitching and that people may experience problems. This way, we don’t spend time unnecessarily trying to research what is happening and can be prepared with a Plan B, again, without having to waste time wondering what is going on.

Forum|Forum|20 days ago

Lara MooreNewcomer

Enable Send Later (Scheduled Sending) when using Shared Access with Send permissionIdea Submitted

Currently, users with Shared Access and Send permission can create and send envelopes on behalf of another user, but they cannot use the Send Later (Scheduled Sending) feature. This limitation requires users to either send envelopes immediately or log in directly as the shared user to schedule delivery.Many organizations use Shared Access for centralized mailboxes (such as HR, Benefits, Payroll, or Legal) so employees can send documents from a shared account while maintaining their own credentials and audit trail.A common use case is preparing onboarding or HR documents in advance and scheduling them to be sent at a specific date and time. Although Scheduled Sending is available when working in the account directly, it is not available when acting through Shared Access, forcing organizations to choose between security best practices and scheduling functionality.Requested enhancement:Allow users with Shared Access and Send permission to use Send Later (Scheduled Sending) for envelopes they create while acting on behalf of the shared user.Business benefits:Supports secure use of Shared Access without requiring users to log in as shared accounts. Enables HR, Payroll, Benefits, Legal, and other administrative teams to prepare and schedule communications in advance. Improves workflow efficiency by eliminating the need to manually send time-sensitive envelopes. Provides feature parity between direct account access and Shared Access for users with Send permission.This enhancement would make Shared Access a more complete solution for organizations that rely on centralized sending accounts while following security and governance best practices.

Forum|Forum|21 days ago

Tijana BozicNewcomer

Feature Request – Default Copy Recipient at Account LevelIdea Submitted

Hi team,We would like to submit a feature request, as our research indicates that this functionality is currently not supported in DocuSign eSignature.Feature descriptionThe requested functionality is to have a default recipient of a copy automatically added to every envelope created by specific groups of users. To clarify, this would not be a default recipient configured on individual templates, but rather an account-level configuration that automatically adds the designated copy recipient regardless of whether the sender uses a predefined template or creates an envelope from scratch.Ideally, this would be configurable so that different groups of users could have different default copy recipients. For example, most users could have one designated mailbox automatically added, while HR or other departments could have different mailboxes configured.Additionally, users should have the ability to remove the automatically added copy recipient for individual envelopes whenever necessary.Business use caseThe main objective of this feature is to ensure that fully executed agreements are automatically copied to the appropriate shared mailbox, providing centralized visibility, governance, and document retention without relying on users to manually add the recipient each time they send an envelope.Today, users can easily forget to include the appropriate mailbox, which may result in executed agreements not being centrally stored or visible to the teams responsible for contract management. An account-level configuration would significantly reduce this risk while still allowing flexibility when exceptions are needed.We explored the suggested workaround of using eSignature templates with predefined copy recipients. However, this approach does not fully meet our business needs. It introduces additional steps for users when sending documents, removes the ability to use the drag-and-drop sending experience if template usage is enforced, and would require users to always select the appropriate template before sending.In addition, we would prefer not to make template usage mandatory for users who do not otherwise need templates as part of their workflow. We are looking for a solution that works seamlessly regardless of how an envelope is created, while preserving users' existing sending experience.Workflows and users that would benefitThis functionality would benefit multiple departments across our organization that use DocuSign eSignature. Different business units require different shared mailboxes to receive copies of executed agreements (for example, Legal, HR, or other operational teams), making group-based configuration important.The feature should apply regardless of how an envelope is created, whether users send documents from templates or create envelopes from scratch, and should support organizations with multiple teams that have different document management requirements.Could you please let us know whether this feature would be feasible to implement? If so, is there any estimated timeline for when it could potentially become available?Please let us know if you need any additional information from our side. Thank you!

Forum|Forum|21 days ago

PslimNew Voice

Agreement Manager - Use Folder-Level Path as Categorization Metadata on Bulk UploadIdea Submitted

When bulk uploading agreements into Agreement Manager, categorization currently relies on AI content analysis after ingest, or manual assignment to agreement types/categories/sets. There's no way to leverage the folder structure of the files being uploaded (e.g., from a mapped drive or cloud storage) as a source of categorization metadata.Many organizations already store historical agreements in a meaningful folder hierarchy, such as:/Sales/MSAs/2026//Procurement/Vendor Agreements/2026/Today, this structure is lost on upload — every file lands in Agreement Manager as an individual record, categorized only by what the AI infers from the document content, or by tags applied manually afterward.Request: When uploading a folder (or nested folders) of agreements, allow the folder path to be captured and mapped to categorization fields, for example:Auto-populate or suggest an agreement type, category, department, or custom field based on the folder name(s) in the path Let admins define a mapping between folder structure and metadata fields before or during upload (e.g., top-level folder → Department, second-level folder → Agreement Type) Preserve the original folder path as a searchable attribute on the agreement record, even if the user doesn't set up a mappingWhy it matters: Migrating agreements from network drives, SharePoint, or other DMS tools into Agreement Manager means re-doing categorization work that already exists in the folder structure. Using folder-level information would speed up migration, reduce manual tagging, and give AI categorization a stronger starting signal instead of relying on content inference alone.

Forum|Forum|21 days ago

TishMNewcomer

Feature Request: Adjustable Date/Time Field Sizing for Better Document CompatibilityDuplicate

Hello, we’ve been struggling with customer signatures overlapping the date/time field with one of our third-party vendors for our new account opening. Our third-party vendor has had to change their documents several times to accommodate for this and it seems like just when we have it working the way we want it to, an update or something changes and the box gets moved. I’ve work with DocuSign support, and they’ve confirmed that the date signed field cannot be adjusted as it automatically fills and will resize to fit the content. This also causes issues because customer signatures are all different sizes. It would be nice if this field was adjustable or font size was adjustable for the date/time to help it be more flexible when being used with third party applications. DocuSign support suggested I post on the community for evaluation for a possible feature update. Thanks for considering!

Forum|Forum|21 days ago

LLealNewcomer

How Does DocuSign Still Not Have a "Select All" Button for Contacts?Idea Submitted

I'm genuinely baffled that in today's age of technology, DocuSign still doesn't have a simple "Select All" option when managing contacts.I recently needed to replace my contact list by importing an updated one. Before I could do that, I had to delete my existing contacts. Unfortunately, I had 779 contacts, and because there isn't a Select All checkbox, I had to manually select every single contact before deleting them.This turned what should have been a 5-second task into a frustrating and time-consuming process.A simple Select All button along with options like Delete Selected or Delete All would dramatically improve the user experience for anyone managing large contact lists.Is there a technical reason this functionality doesn't exist? It seems like a very basic feature that most modern applications provide.I hope the DocuSign product team considers adding this. It would save users a tremendous amount of time and frustration.

Forum|Forum|23 days ago

MattLNewcomer

Update "Select your verification method" Physical ID languageIdea Submitted

At some point the language used to describe the “Physical ID” verification option changed to “Verify by taking a photo of your ID and a selfie” even if only the ID is required. Speaking with Support, I was informed “ the "selfie" word was included there by default, so we won't be able to remove that specific word for the verification setup in your account.” This is baffling. We’re losing clients because they have no interest in providing a selfie. Please update this language or allow us to update it on our own. Edit: It also now gives “Clear” as an option even though that is not selected as an option in Identity Verification Accepted IDs.

Forum|Forum|23 days ago

ThomasHConversation Starter

Improve Signing Group inclusion in Power Automate FlowsIdea Submitted

Are you a DocuSign heavy user or maybe just a bit lazy/annoyed to download envelopes after signing them? Wouldn’t it be convenient to retrieve signed envelopes in real-time or on a fixed schedule? Maybe not just downloaded into one folder but following a defined routine to be stored at the right places?😱 *mind blown* right?!So here is the pitch: Include Signing Groups in more Power Automate Actions and Triggers to increase the potential for more automated flows.Currently Signing Groups are only supported in a handful of Power Automate actions:Add recipient to an envelopeUpdate recipient on an envelopeCreate envelope using template with recipients and tabsCreate envelope using composite templatesRefer also to: Help needed to automate DocuSign pdf download via Power Automate | Community

Forum|Forum|23 days ago

valmObserver

Document Delivery Failed StatusDuplicate

"Delivery Failure" does not get written back to the Docusign Status component in Salesforce when an envelope fails to deliver to an email address. It would be very helpful if senders could be notified in Salesforce when this happens as well as earlier than after the final bounce. We had a rep who was notified via email three days after she sent the envelope and had not idea the signer had not received the email.

Forum|Forum|23 days ago

OpsGirlNewcomer

Stripe payment failures and envelope delivery failures NotificationsIdea Submitted

I would like some assistance in turning on notifications for stripe payment failures and envelope delivery failures. As of today, Docusign is unable to notify our internal team and we do not receive notifications when an envelope has a "payment failure” nor when the envelope has a “delivery failure”. Additionally, an enhancement to have recipient delivery failure status sent back through the API to salesforce would be extremely efficient and helpful. Our team would then be able to flag and process our transactions more efficiently.

Forum|Forum|23 days ago

ehaggardNewcomer

Exceptions in Shared AccessIdea Submitted

It would be beneficial when users have shared access within a group to be able to restrict template/document types when needed.For example we recently began sending our employee reviews for signature through docusign and when sending to an employee all other employees with shared access can view this. Being able to say that the employee review is excluded from shared access would be a big help.

Forum|Forum|23 days ago

stephanieabieObserver

Add more users in smart filters for SetsIdea Submitted

Allow the smart filter for sender email to include more than one user/sender email.I am trying to create a smart filter for several senders to be considered, but it’s only allowing me to choose one email.

Forum|Forum|24 days ago

momathewsonNew Voice

Add IAM notifications to Teams appIdea Submitted

Add IAM notifications to Teams app

Forum|Forum|24 days ago

momathewsonNew Voice

Add IAM Request notifications to mobile appIdea Submitted

Add IAM Request notifications to mobile app

Forum|Forum|24 days ago

ConsultantTFNewcomer

Make Form Data Print to PDF and .csv Export Authoritative Copies for Compliance with ALCOA ++ Principles for Data IntegrityIdea Submitted

Make Form Data print to PDF and .csv export Authoritative Copies suitable as audit-facing reports to comply with ALCOA ++ principles for data integrity.The PDF Form Data is traceable to the EnvelopeID and identifies fields and values associated with the document.The .csv export is also traceable to the EnvelopeID but also includes the recipient's name and email associated with the fields and values (Attribution) and the Recipient Signed date and time the fields are populated with a value (Contemporaneous and Original).This is requested so it can support the validation of the Part 11 module for Regulatory Agency Quality GxP-related regulations.

Forum|Forum|24 days ago

Mathyas ValasekNewcomer

Enhancement Requests for Template Permissions, Advanced Settings, and User GuidanceIdea Submitted

Restrict senders from modifying recipient roles Allow administrators to define recipient roles within templates and prevent senders from changing those predetermined roles (e.g., changing a recipient from "Needs to Sign" to "Receives a Copy"). Disable or limit access to advanced options Provide administrators with the ability to disable or restrict certain advanced options, particularly the "Recipients must be signers to view signed documents" option, to ensure consistent access and visibility requirements across the organization. Provide in-app guidance for users Introduce contextual help features, such as pop-ups, tooltips, or information bubbles, to guide users while creating and configuring envelopes, helping them better understand available settings and their impact.

Forum|Forum|25 days ago

backofficeNewcomer

Improving workflow for compelling applicants to complete the signing process (gateway leading applicants from the ID verification step to signing relevant documents)Idea Submitted

After the recipient processes the identification step during the E-signature process, recipients are asked to sign the fields they're assigned. However, if recipients did not complete the process by clicking the correct buttons such as Sign or Complete, the envelope will not be considered completed and shall remain in a limbo as pending which implies unnecessary follow up frictions with recipients.This is so because in DocuSign, recipients have the option to skip their signing at a later time. They can also leave their signature on the envelope, and if they do not properly complete the signing, the signature will be saved but will not be completed.Our past experience tells that clearing the ID verification to signing relevant paperwork is very often confusing or not properly guided within your current workflow display. We suffer ongoing failures from recipients failing to complete the signature process after having been identified. They think they have completed the process but the actual processing status at DocuSign is recorded as signature pending. We understand the purpose of expecting clients to push a button to confirm submission after they have signed the forms. However, this extra layer of requirement for the final submission should be smoothen by clearly disclosing to recipients the need to push the “Complete” button.We think that there is a lack of specific guidance needed while recipients are processing the entire signature process. This could be perhaps quite easily upgraded by disclosing:Step 1- ID verificationStep 2 - SignatureStep 3 - Confirming submission by clicking the “Complete” button. Recipients that would have signed documents BUT forgot to also push the “Complete” button should be warned about the resulting pending status of their submissions, prompting recipients to Complete it if they want to move ahead.It would be great if you'd take this into account for quality improvements at your end. Thank you

Forum|Forum|27 days ago