Skip to main content

Docusign eSignature 26.2.00.00 Release Notes: June 2026

Categories:Release Notes
  • May 15, 2026
  • 0 replies
  • 21 views
Forum|alt.badge.img+6

Docusign is pleased to announce that the Docusign eSignature 26.2.00.00 Release Notes: June 2026, is now available on the Demo environment for customer testing.

🚀 What's new?

  • Redirect notices when navigating away from Docusign
    This change strengthens security by clearly notifying users when they are navigating to a non-Docusign URL from within the product. This makes it much clearer to users when they are leaving the secure environment, preventing misuse of Docusign URLs.
  • Introducing Concurrent API Limits
    New concurrent call limits for specific API actions are being introduced to ensure platform stability and protect infrastructure from long-running requests. Developers should be aware of this change to maintain integration performance, although it is expected to not impact 99.99% of normal traffic.
  • Support for Bulk Send API Customizable Pre-fill Tabs
    Bulk Send Lists and Send APIs now support Prefill tabs, allowing you to populate envelopes with customizable prefill tab values. This enhancement streamlines the bulk sending process by enabling you to set default values at the envelope level, saving time and ensuring consistency across batch sends.
  • Reduced Friction During Digital Signature Completion Process with New Customization Capabilities
    Signers can now complete the identity verification for Advanced and Qualified electronic signatures after reviewing the document, rather than before. This updated flow reduces friction and improves completion rates by ensuring only engaged signers proceed with identity verification.
  • Improvements to the Docusign ID Verification Participant Flows
    The identity selection screens for participants completing ID document verification will be updated with a new UI. These design improvements make it easier for participants to select their reusable or electronic IDs, streamlining the overall verification experience.
  • Federal UX Optimization for PIV/CAC Signers
    Critical user experience enhancements, including the elimination of the mandatory Signing Reason field, are being introduced for Federal Market users signing with PIV and CAC smart cards. This significant change will streamline the authentication steps, resulting in a much faster and more reliable signing experience.
  • Spanish and Portuguese Support for AI Summary and Q&A During Signing
    AI-assisted features in the signing experience now support Spanish and Portuguese, expanding the global accessibility of agreement summaries and Q&A tools. This enhancement allows signers to interact with crucial document information in their native language on both desktop and mobile devices.
  • German, French and Japanese Support for AI Summary and Q&A During Signing
    AI-assisted features will soon expand support to include German, French, and Japanese signing experiences. This continuous multilingual expansion ensures that users around the world can leverage agreement summaries and Q&A tools in their preferred interface language.
  • Support for Improved Document Formatting in Agreement Template Builder (ATB)
    Word documents uploaded into the Agreement Template Builder now retain more complex formatting, such as lists and styling, for a higher fidelity result. This crucial improvement reduces manual cleanup and allows users to transition more seamlessly from Word to template creation.
  • Support for Collapse and Expansion of Left hand Panel in Agreement Template Builder
    Users can now collapse and expand the left panel in the Agreement Template Builder, which is particularly beneficial for those on smaller screens. This simple, effective UX improvement provides more space and focus for template building by hiding distractions.
  • Custom ID Verification Configurations Now Enforce Accepted ID Restrictions for Simple and Advanced Signatures
    Docusign is implementing stricter enforcement of accepted IDs in customized identity configurations to improve the accuracy of ID Verification for simple and advanced signatures. This change ensures that recipients can only submit ID documents that administrators have specifically selected, thereby enhancing security and compliance.
  • Deprecation Notice for listRecipientNamesByEmail RestAPI Endpoint
    Support for the listRecipientNamesByEmail REST API endpoint is being removed in July 2026 to improve overall system architecture and security posture. Developers must act now to review active integrations and transition away from this endpoint to avoid API failures, especially if they use the legacy Docusign eSignature for Salesforce managed package.
  • Next Gen eSignature Experience Timeline Update
    The eSignature experience is receiving a bold new makeover to transform the sending process, accelerating template preparation and envelope sending to help drive conversion. The rollout is currently at 50% while customer feedback is incorporated, so administrators should prepare for the eventual full standardization of the new experience.
  • Connect Mutual TLS Certificate Changes
    Docusign is moving to a new mutual TLS certificate implementation to ensure reliability and preserve existing functionality, in response to industry-wide changes reducing certificate lifetimes to 47 days. Customers using Connect who explicitly pin or validate specific certificate thumbprints must complete necessary changes before August 2026 to ensure continuous security and service.
  • Docusign Admin Release Notes
    This section directs users to the dedicated release notes for Docusign Account and Organization Administration, App Center, and Monitor. Users can find important administrative updates and changes related to account management and organization administration in these conveniently located resources.

For full details, check out the complete release notes. 

📌 Feature availability notice

  • Not all product features are available at the time of this announcement.
  • Product features are planned for delivery by the end of the month for which the release notes are written.
  • Check the release notes for the expected release schedule of a feature.

đź’¬ We want to hear from you!

  • What update are you most excited about in this release?
  • Are there any features or fixes you’re hoping to see next?
  • Do you have any questions about this release?

 

Share your thoughts in the comments below 👇

Â