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...
21380
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
Making this change would apply to all users on our company account — currently 2,034 people — which is not an acceptable solution for our needs. This seems like a basic customization feature that should reasonably be available at the user level.
Ability to use "retryEventForEnvelope" for any envelopes. Not only failed notifications on the auto-retry queue.
We need the ability to schedule a specific time of day for reminders to be sent on, we currently had customer complaints about the reminders coming in at 1am.We should also have the ability to send on weekdays only.Regards
Although this can be handled in workflow post submission, there are times when we need to ensure that only one document is added at the outset.One common example of this would be those cases where users are asked to pick a document in CLM that is the parent document of the one being generated (e.g. an Amendment form). In this case it makes more sense if the user could only pick one document.This requirement come up time and time again.
Please add Lock Recipient Name under the Customize dropdown box by each recipient for all users when creating a Docusign envelope. I feel it should not be just an admin-based feature as it is difficult for users to get a hold of our admin to make the change. It is more time efficient if it was a user-based option.
I think an enhancement to the eSignature and Agreement Manager - (formerly Navigator) workflow would be the admin ability to restrict custom envelope fields to specific user groups. I’ve run into instances where one custom field is required org-wide, but another additional custom field should only be restricted to a team within our business that uses Docusign.
Other just doesn’t cut it. CRA now requires signatures for efiling tax documents. The plans are ridiculous. Either 5 per month or 100. Tax season is 4 months, maybe sometimes more. More than 5 but less than 100 per month. There should be a volume allowed instead of per month number. For example; 0-100 documents, 200-500 something like this.
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.
The Docusign template library is fantastic and contains a lot of sample envelope templates that you can use when building your own envelopes. However, there’s not currently a way to extract the PDFs from those envelope templates for usage inside a document template. I was told by the support team that if I wanted to use a template from the Docusign library, I would have to copy it by hand into a new document template. This is rather difficult to do, especially for documents that have a lot of conditional formatting and formulas in them (such as the W-4 template that I downloaded myself).
It would be helpful is envelope senders received a notification when an envelope is due to expire. This often causes issues as the senders do not realise their envelope is due to expire and it is then completely voided. A reminder notification, or the ability to set one, would help avoid this.
It would be very helpful if the envelope sender was notified before the envelope expired. Envelopes often expire as the sender has been unaware that they were reaching the expiration date.
We miss to receive a notification as a Sender when an envelope has expired. If a signer do not sign for some reason, the envelope simply is voided in connection with expiry, and it is hard for us to keep track of which envelopes that have expired. Besides receiving a notification, it would be great if the expired envelopes automatically could be found in a folder called “Expired envelopes”.
CLM Workflows can be exported/imported as JSON — Document Generation Forms should have the same capability.Current limitation:No way to export a form's configuration as a readable file (JSON, XML, etc.) The only transfer method is Component Packages (.spackage), which are proprietary and cannot be inspected or edited No way to compare, audit, or bulk-update field structures across multiple forms without opening each one manually in the Form BuilderRequested feature:"Export as JSON" and "Import from JSON" options for Document Generation Forms Exported file should include: sections, fields, field types, validations, dropdown/CSV references, conditional rules, and attribute linksUse case: Managing 10-15+ forms that share common sections. Currently impossible to efficiently align them, version-control them, or analyse them with external tools.





Docusign Community
Code of ConductAlready have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK