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...
23190
Want to shape the future of Docusign? Add your ideas for dream features and upvote others you love.
Right now this is the only formatting.It would be nice to allow for the transparent background of the text and the ability to make the background of the text another color. Right now it looks like this:
Hello, The current capacity of Attachment field has been confirmed as follows. ==================================="Each signer attachment file can be up to 25 MB in size, and the total size of all signer attachments you upload for a single recipient cannot exceed 50 MB."===================================However, the VoC of users who need large-scale attachments is increasing. Do you plan to increase the size of your attachments?
Allow Docusign document templates to connect directly to HubSpot CRM so that when sending an envelope, contact/company fields (name, title, company, address, etc.) are automatically pulled and prefilled without requiring a custom API integration or workflows. Desired behavior:Map Docusign template fields (e.g. customer_name, customer_company) to HubSpot contact/company properties in the template editor When sending, Docusign auto-fetches the mapped values from HubSpot
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.
The standard Docusign password policy does not provide an administrator-configurable list of prohibited words or strings. The available controls cover password length, password age, and required character types. Spaces and angle brackets are not permitted in passwords.Ideally administrators should be able to block the use of specific words when user setting up or updating passwords.
When user authenticating the option to "remember this device" is available, currently admins don’t have the capability to change the settings (increase, reduce, change the amount of time) for this option and would be helpful if Docusign can make this configurable.
When the user is signing using a screen that responds to touch, allow the user to lock the screen position so the drawing process does not move the signature box.
Make filtering options “sticky” when in the All Agreements folder.I’ve spoken with DocuSign Support regarding the removal of the Inbox option for end users and the available filtering options in the All Agreements window. The only successful filtering choice available to me is Quick Views: Action Required to see only those envelopes that require my attention. Otherwise I see every single envelope regardless of the current status.The only downfall is that the filtering is removed every time I move away from the All Agreements window and come back. It would be great if the filtering choices would stick for the entirety of the user session. We have power users in our office that can have up to 100+ envelopes in states of flux, so having to refilter every single time is very time consuming and tiresome.
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**





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.