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...
22860
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
Hello Ideas team,We advice all of our customer migrate to new send view as this document told:https://www.docusign.com/blog/developers/esignature-rest-api-embedded-correct-view-updated?msockid=13eac2ad5d496fc10dc3d62c5c416ee9and also can find the document:https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/createsender/we find the setting as below:{ "returnUrl": "<url>", // URL required "viewAccess": "envelope", // required "settings": { "startingScreen": "Prepare", // (default) or "Tagger" "sendButtonAction": "send", // (default), "redirect" "showBackButton": "true", // (default), "false" "backButtonAction": "previousPage", // (default), "redirect" "showHeaderActions": "true", // (default), "false" "showDiscardAction": "true", // (default), "false" "lockToken": token_value, "recipientSettings": { "showEditRecipients": "true", // (default), "false" "showContactsList": "true" // (default), "false" }, "documentSettings": { "showEditDocuments": "true", // (def,ault), "false" "showEditDocumentVisibility": "true" // (default), "false" "showEditPages": "true", // (default), "false" }, "taggerSettings": { "paletteSections": "default", // (default), "none", "custom" "paletteDefault": "custom" // "merge", "notary", "seals", // "smartContracts", "annotations", // "smartSections" } } }}Now the customer want add validate parameter for send button. We can define paramter for signature in the setting, so it will check whether the sender have drag signture for every signer before send. sometime the sender forget drag signature for other signer except the first one. if the sender not drag, will throw the error that he need to drag the signature for which signer. FreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🌟 The only DocuSign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024📊 DocuSign Community Leaderboard Top 5 contributor🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng/
When you use the copy button it would be valuable to be able to see which envelope the new envelope was copied from. In my opinion, something should tie those envelopes to each other for reference. We can’t find any ties between them even via the API and metadata. It doesn’t show anything in the envelope history or certificate of completion noting that the envelope was copied (yet).
We want raise enhancement request for adding RecipientIPAddress attribute as part of JSON connect event through Webhook. Currently this attribute is as part of XML event that follow SOAP API. But we want that field to be included in the Docusign JSON event that follows REST API schema.
We are capturing date fields on a Web Form as part of a Workflow Builder (formerly Maestro) Workflow. We are pushing the date fields collected into Salesforce. Salesforce has validation rules on some fields that will not allow dates that are in the past.This will cause the Workflow Builder (formerly Maestro) Workflow to fail upon SF Update and/or the Salesforce processing to fail.We would like to see the ability to allow restrictions on the Date field (e.g. current and future dates only)
Similar to Envelope Custom Fields and the way they show up on Envelope Reports, we would regular text/tab fields to also have the option to display on reports, as we have key identify features like ‘Loan Number’ or ‘Member Number’ we would like to include. This should also extend to Powerforms, as we’re currently utilizing this for most of our processes, which makes ECF not an option.
Description:Currently, redirect URLs can only be configured at the Account or Brand level through the “Destination URL” setting, or dynamically specified when generating an embedded signing view.However, for email-based signing, there is no option to define a per-recipient redirect URL when creating an envelope via API.In some business scenarios — for example, our customer needs to have external merchants sign agreements — they would like each signer to be redirected to a custom application form or confirmation page after signing.We have tried: Embedding the form link in the email body → but since the domain differs from DocuSign’s, this often triggers mail security gateways and increases the chance of messages being quarantined or blocked. Using the Brand-level Destination URL → but this applies globally across all envelopes and recipients, which is too broad and affects other workflows. Therefore, we suggest enabling the ability to specify a recipient-level redirect URL at the time of envelope creation, similar to how embedded signing supports returnUrl.Additionally, it would be very helpful if this redirect could be triggered immediately upon completion of signing, even for standard email-based flows — to provide a smoother, more seamless end-user experience.Benefits: Enables finer-grained control for different workflows or recipients; Reduces email deliverability risks by avoiding external links in the signing email body; Provides a more integrated experience between DocuSign and customer business systems. FreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🌟The only DocuSign Partner globally with two Certified eSignature Technical Consultants🏆 DocuSign 2025 APAC Growth Engine Partner of the Year💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024📊 DocuSign Community Leaderboard Top 5 contributor🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng📬 For business inquiries, feel free to connect via :WeChat/微信: +86 1381880287WhatsApp: +65 97796938
Title:Description:According to the current process, if an SMS subscription needs to be revoked within 7 days, customers must open a Support Case and wait for the Docusign Support team to process the request.For customers with large and growing envelope volumes, this creates several challenges: Users may accidentally subscribe SMS authentication, but they are not immediately aware of the mistake. By the time they realize it, the SMS subscription link has often expired, making recovery more difficult. Submitting a Support Case for each incorrect subscription introduces significant operational workload, slows down business processes, and reduces overall system usability. We would like to propose adding the ability for account administrators to directly revoke SMS subscriptions through the Docusign Admin Portal or via API — without requiring intervention from the Support team.Benefits of this enhancement: Dramatically improves efficiency for high-volume enterprise customers; Reduces reliance on manual Support cases and shortens the response cycle; Minimizes business disruption caused by accidental SMS subscription issues; Enhances the overall self-service capabilities of the Docusign platform. Providing an online, self-service revocation option would significantly improve the customer experience and reduce operational friction for organizations that rely heavily on SMS authentication. FreeLink/甫连信息🌍 DocuSign Partner | Partner Profile🌟The only DocuSign Partner globally with two Certified eSignature Technical Consultants🏆 DocuSign 2025 APAC Growth Engine Partner of the Year💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024📊 DocuSign Community Leaderboard Top 5 contributor🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries🔗 Connect with me on LinkedIn: https://www.linkedin.com/in/gehengfeng📬 For business inquiries, feel free to connect via :WeChat/微信: +86 1381880287WhatsApp: +65 97796938
Most of the document are legally approved documents and should not be edited. Requesting for a Docusign enhancement where the user can adjust the height of the standard and/or custom fields to enable developers to use fields in limited/narrow spaces without the fields overlap the document text.
When document visibility is turned on for any organization, the ability to fax envelopes is disabled.I would like to propose an enhancement that allows fax functionality to remain available when document visibility is enabled.This improvement would greatly benefit our organization by enabling us to send multiple documents in the same envelope with the document visibility selection options, and still fax envelopes as needed to support our customers.Thank you for considering this request.Brandy
Currently upon sending envelopes/upload requests to a participant from a workspace the user gets an email about assigned tasks. This email is not found in the resource file so we are unable to modify it. Please allow for us to modify the email template.
Data on DocuSign Envelope Volume Report and DocuSign Dashboard do not agree. It would be a nice enhancement if the data in these two areas agreed.
Workflow Builder (formerly Maestro)’s “Store files in SharePoint” step can currently save completed workflows to only one folder. While agreement action rules can save to multiple SharePoint folders, they offer very limited naming variables.Use case: For public volunteer/department events, appearance release forms are processed in Workflow Builder (formerly Maestro). The workflow includes an event-name dropdown (5 pillar events + “Other”) that is a document custom field. Because Workflow Builder (formerly Maestro) can’t route saves to multiple folders, agreement actions are used so each event option saves to its own SharePoint folder, but file naming is constrained.Request: Either (1) add multi-folder save routing in Workflow Builder (formerly Maestro) similar to agreement action rules, or (2) expand variable options in agreement actions to match Workflow Builder (formerly Maestro)—ideally also supporting saving the envelope, attachments, and certificate of completion together in one PDF as Workflow Builder (formerly Maestro) does.
Hi All,Our business requires a solution for the current behavior where, upon clicking the Send button, all documents attached to the agreement are automatically selected by default.However, the expected behavior is that documents should not be pre-selected. Instead, users should have the flexibility to manually choose only the specific documents they want to send, rather than having all documents selected automatically.Could you please provide a solution to address this requirement?





Docusign Community
Code of ConductAlready have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.