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...
23710
Hello! We would like to share an idea about using the tool “web forms” (if this idea already exists, please inform us). For example, when we enter the company’s EIN (Employer Identification Number), the system could automatically retrieve the information already registered in our database, such as the company’s legal name, address, and other relevant details. This way, there will be no need to re-enter all the informations again.
We have our default setting for the Date Signed Field on our account set to the Recipient, however this is not using the Recipient's Date/Time Zone.Every document is defaulting to the Account's Default Time Zone which is CDT. After a Live Chat session with DocuSign Support, we found the recipients have their Time Zone set to Match My Computer's Time Zone. Based on the chat, we then updated one user to Specify a Time Zone and selected Eastern Time (US & Canada).The Signature Date then updated correctly to Eastern Time. We are providing this feedback to alert you of the potential for legal risk. We also have many recipients who do not have an account, there should be an option to default to the Date Signed to Match My Computer's Time Zone whether they have an account or not. Looking forward to your swift reply. Thank you!
In the Admin panel > Document Custom Fields page, add a tool to download all document custom fields and their attributes as a csv, and a tool to import and bulk update document custom fields from csv. Having to maintain dozens or hundreds of document custom fields by manually editing/removing each one is very time consuming, and having the ability to view and update document custom field attributes in a CSV will make sure that the fields we use in docusign match any corresponding fields in other systems.
Hi Team,I have a customer using Docusign where is regularly encountering the 200 MB maximum combined envelope size when sending large document sets for signature.The customer is requesting that Docusign consider increasing the maximum combined envelope size to 500 MB. This request relates to the total size of all documents within an envelope, rather than the size of an individual PDF.The current Large File Support capability does not address this requirement because the total envelope limit remains 200 MB. We would therefore ask Docusign to consider one of the following options: Increase the standard combined envelope limit to 500 MB. Introduce an opt-in capability for eligible enterprise customers. Offer a controlled beta or other supported workflow for large document sets. This enhancement would reduce the need to split related document sets across multiple envelopes and would provide a more efficient signing experience for customers handling large project documentation.Please consider this requirement for future product planning and advise whether it could be evaluated as a product enhancement.Thank you so much!!
Add the ability to place within a document a read-only field that displays the value of an envelope custom field for that envelope. For example, if I have an envelope custom field called Doc_Type that is a dropdown list, I would like the ability to display the selected Doc_Type value in the documents themselves.
From the admin panel > document custom fields page, add the ability to list all templates currently using the custom field. Until DocuSign adds the ability to update all instances of a custom field in existing templates, it’s up to the admin to know which templates include the custom field that needs to be updated. While this can be done by API, not all accounts have access to an API developer and there are too many quality of life UX features that are being skipped with the excuse that it can be done via API.Related to:
When updating the properties of a document custom field from the admin panel, give the option to update all instances of that custom field across all templates. Without being able to update existing instances of the custom field in templates, the document custom field feature is not very useful.Currently, the admin needs to magically know every template that uses the custom field, manually edit each template, and replicate the field changes. Alternatively, one would need an API developer (an additional cost/resource not everyone has) to identify all templates using the document custom field and then run a script to update each instance of the field in those templates.Another helpful feature for this would be to list all templates in which the document custom field is used. I’ll submit a separate idea post for that.
When attaching supporting documents and using any of the “Accept” actions, we should be able to run a report across all envelopes to verify who has accepted. It is tedious to have to check every envelope when you use this feature across 100s of employees.
We use in our company Full Name build as “LastName FirstName”. DocuSign Doesn’t provide today any functionality in configuration to manage how the Full Name should looks like and its build as “FirstName LastName”.Due to this difference once we get email from DocuSign to sing some envelope, the format of Full Name in email looks strange, as first name and lest name are coming in wrong order.We would apricate to have functionality to specify as customer how the Full name should be build.
Permettre d' avoir plusieurs délégataires et pas une personne unique
Today, DocuSign for Dynamics 365 allows administrators to configure which entities are enabled for DocuSign actions such as Sign, Send with DocuSign, and Bulk Send with DocuSign. However, the DocuSign Log In/Log Out ribbon commands (which I believe came as part of the move to OAuth) appear on entities that are not enabled for DocuSign use.We would like an enhancement that gives administrators explicit control over where the Log In/Log Out commands are displayed, ideally leveraging the existing entity configuration experience within DocuSign Admin.Suggested approaches:Only display Log In/Log Out commands on entities that are enabled for DocuSign integration (e.g. Sign, Send, Bulk Send). Alternatively, add a configurable setting per entity that controls Log In/Log Out visibility, similar to existing DocuSign command configuration options.Business Value I would assume most organizations use DocuSign with only a subset of Dynamics 365 entities. Displaying Log In/Log Out commands across unrelated entities:Creates unnecessary ribbon clutter. Confuses users who will never use DocuSign. Introduces DocuSign-related processing on forms that have no DocuSign business purpose. Limits administrators' ability to tailor the user experience to their business processes.Providing entity-level control would improve usability, reduce user confusion, and better align the DocuSign experience with how customers already configure entity-specific functionality in Dynamics 365.Expected Outcome Administrators should be able to determine exactly which entities expose DocuSign authentication commands, resulting in a cleaner and more relevant Dynamics 365 experience for end users.
It would be helpful if senders to received a notification when recipient signs a document, not just when they view it
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.