Skip to main content

    Filter by Idea status

    Filter by category

    817 Ideas

    Barry BNewcomer

    Make it easier to control the geolocation capturing settings for signers of documents/envelopesIdea Submitted

    Currently in eSignature, it is not easy to control the settings that capture a signers’ geolocation. We have discovered a potential security concern that if a signer is at their personal, home location when signing a document, this will be visible under the ‘Signed in location’ link, to all signers of a document -  This is personal information that someone may not want to be visible to 3rd party signers or colleagues. The Docusign steps to amend the geolocation settings involve creating a ‘brand’ (if one doesn’t exist already), downloading the master xml resource file, amending the following value -<data name="DocuSign_DisableLocationAwareness">true</data>and then uploading a copy of the edited xml file to the signing resource file section. The problem with this is it appears that the setting doesn’t work at all, it’s all dependant on the geolocation sharing settings in the browser. In theory, if you set this up correctly in the Admin - Brands area, even if a user chooses ‘Yes’ if asked by the browser if they allow the Docusign website to know their location, it should not capture the location the document was signed. From our testing this does not appear to function as expected. Also, from what we have seen, after changing the required settings and clearing your browser cache, the prompt to choose whether you allow the Docusign site to know your location only appears if you login to Docusign first to sign a document. If you click on a link from an email request to sign a document, it does not ask you if you want to allow the Docusign site to know your location and takes you straight to the signing page of the document. The easiest way round all of this is to just go into the browser settings and disable the geolocation settings specifically for the Docusign URL. I feel that the existing way to configure the location capturing in Docusign is far too convoluted. The settings to control geolocation capturing for signers should either be a switch in the Admin area, or configurable when creating an envelope. Please can this be reviewed for a future release of eSignature? 

    CarmenHuberNew Voice

    Allow visibility into incomplete web form responses before submissionIdea Submitted

    Currently, there is no direct way to view a recipient’s entered data in a DocuSign web form before the form has been completed. Visibility is only possible in a limited case when the web form is based on a template and the recipient has already moved into the signing environment, but has not yet completed the resulting envelope.It would be very helpful if web form creators could see the current input status of an incomplete web form before final submission.Suggested featurePlease add a function that allows web form creators to view partially completed responses, ideally including:entered field data before completion current progress/status of the recipient clear indication that the form is still incomplete optional access to saved draft or interim dataBenefitThis would significantly improve customer support and usability. If a customer has trouble completing a form, the sender could directly see where the issue is and what information has already been entered, instead of asking for screenshots or relying on support.This would help:reduce support effort improve the user experience lower abandonment during form completion make troubleshooting much more efficientExample use caseIf a customer needs help while filling out a web form, the creator currently cannot see the entered information until the form is completed. Access to partial responses would make it much easier to provide fast and accurate support.

    Allow customers to directly apply for Electronic Seals via API or Admin ConsoleIdea Submitted

    Currently, to apply for a Docusign Electronic Seal (eSeal), the Docusign Sales team need to initiate a Docusign envelope signing process, attach the seal information, and then open a support case for approval by customer or partner.This multi-step process is quite time-consuming and requires coordination between business and technical teams.We would like to suggest that customers or account administrators be able to submit and configure Electronic Seal information directly from the Docusign Admin Console or via API, with Docusign performing the approval and verification afterward.This improvement would: Greatly streamline the eSeal application process; Reduce manual case creation; Improve the overall user experience for enterprise administrators managing Electronic Seals configurations.  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

    JoshBrownRSANew Voice

    Comments appearance changeIdea Submitted

    When using the Add Comment feature when signing an envelope in DocuSign, I think it would be great if we could call more attention to Comment that have been posted by the following:When the email with the full text of the comment is sent, clicking the “View” link button takes you directly to the comment, not the first page of the packet. Our comments are likely going to be somewhere within 100 pages or more, it would be nice not to have to hunt for the comment(s). If a comment is added to a page, making it pop/standout via changing the appearance of the thumbnail of the page it appears on might be helpful. Such as highlighting the thumbnail border a bright color, or using some kind of colored flag in the top right or left hand corner of the thumbnail image. The dull blue color the comment “bubble”/”dot” appears on the page once it has been posted actually matches a common color used in our documents we create envelopes for. If the user could alter the color to be a range of different colors, I think that would help the comment be easier to find. Also, the shape of the comment, and possibly having the comment appear on the page, not off past the far right border of the page, would all be nice options to give users.These are my three best suggestions at the moment for how to make comments more user friendly. I think they would be good ideas for DocuSign to at least consider making available to users in the future.Thanks,Josh

    RachelKLNewcomer

    Feature Request: Template-Level Control for PDF vs. Link Delivery to Support Data Privacy & Industry ComplianceIdea Submitted

    DescriptionIn today’s environment - where data privacy, cybersecurity, and regulatory compliance standards are increasing across all industries, it has become critical for organizations to control how completed DocuSign documents are delivered on a per-template basis, not just at the account level.Currently, DocuSign only allows PDF vs. Link delivery settings at the account level.This creates significant challenges for organizations that manage different types of documents with different data-exposure risks.Why Template-Level Delivery MattersMany industries regularly send documents that contain PII, PHI, financial data, employee data, and other sensitive information. For these types of documents, Link Delivery is the safer and more compliant option because:• Access requires authentication into a DocuSign account• Documents are not transmitted as unsecured PDFs• Exposure risk is reduced in the event of an email compromise or downstream data breachConversely, many other templates, such as vendor contracts, NDAs, media agreements, or documents without PII—do not need link-level protection and are more efficiently consumed as PDFs.Real-World ImpactThis limitation affects:• Financial institutions (loan docs, ACH forms, identity verification)• HR and payroll departments (I-9s, tax forms, onboarding docs)• Healthcare and insurance (claims, patient forms, PHI-containing documents)• Enterprise legal teams (sensitive amendments, personnel agreements)• Any organization with mixed-risk document typesToday, companies must choose one single delivery method for the entire account - even though the sensitivity of documents varies dramatically.Security & Compliance RisksWithout template-level control:• Sensitive PII documents may be forced to send as PDFs, creating unnecessary exposure• Low-risk templates may be forced into Link Delivery, creating inefficiency and confusion• Corporations must invent manual workarounds (file padding, extra pages, etc.) to force the preferred method—none of which are scalable or secure• The current model does not align with modern privacy frameworks (SOC 2, ISO, GDPR, HIPAA, GLBA)Proposed EnhancementDocuSign should allow each template to specify its own final document delivery method:• PDF Delivery• Link Delivery (Account Login Required)This empowers organizations to:• Meet compliance requirements• Reduce data-breach exposure• Simplify workflows• Eliminate workaround solutions• Better support enterprise-level governance and security needsConclusionA template-level delivery setting would be a major step forward for organizations that rely on DocuSign as an enterprise system of agreement. With data privacy and cybersecurity threats rising across every industry, having granular control over document delivery isn’t just convenient, it is essential.