Docusign eSignature 26.1.00.00 Release Notes: March 2026

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

🚀 What's new?

• Docusign Workspaces availability for FedRAMP and GovRAMP Customers
  This update is crucial for U.S. government customers, as it expands Docusign Workspaces access to those on FedRAMP and GovRAMP compliant plans starting in March. By ensuring compliance and availability for government sector use, Docusign helps secure and streamline essential workflows for state, local, and federal entities.
• Redesigned eSignature Home Page
  Experience a faster, more organized signing and sending workflow with this eSignature home page refresh, which surfaces recent actions and tasks directly on the main screen. This redesign aims to simplify your daily tasks and help you manage your documents more efficiently across all activities.
• AI Summary and Q&A Now Support Multi-Document Agreements
  Signers can now gain clarity and confidence in complex agreements with AI-assisted features that support multi-document envelopes up to 150 pages. This powerful enhancement allows users to get concise summaries and document-based answers to their questions across large agreements.
• Manage eSignature and Digital Signatures Together in a Single Account
  Simplify your account management by handling both standard electronic signatures and qualified digital signatures within a single Docusign account, eliminating the complexity of using separate sub-accounts. This key improvement provides greater flexibility and reduces administrative overhead for organizations with mixed signature requirements.
• Modifications to Account Email Sender and Domain
  Docusign is migrating account-related emails to a new sending domain and "From" address to improve email deliverability and ensure that important communications like security and login notifications land reliably in your inbox. This migration aligns with security best practices, reducing the chance of your account emails being flagged as spam.
• WhatsApp Delivery: Enhanced Recipient Safety and Reporting
  This enhancement adds an "I don’t know this sender" button to WhatsApp delivery messages, allowing recipients to report suspicious activity directly to Docusign for investigation. This vital security update helps reduce fraud and ensures a safer signing experience for all users who receive agreements via WhatsApp.
• Bulk Send Now Supports Excel (.xlsx) Recipient Lists
  Streamline your bulk sending process by directly uploading native Microsoft Excel (.xlsx) files as recipient lists, removing the need to convert to CSV format. This feature simplifies list preparation and helps eliminate common formatting errors, making large-scale envelope sending much faster.
• TLS 1.3 support for Connect
  Docusign is enabling the latest Transport Layer Security protocol, TLS 1.3, for all Connect traffic in demo and production environments by the end of April. This security enhancement will improve the performance and security of Connect integrations without requiring any action from existing customers who use TLS 1.2.
• Organization Bulk User Export Update
  A fix is being deployed for SCIM-enabled accounts that were experiencing failures when trying to export a list of users, and the export CSV will now include a SCIMManaged column. This update ensures reliable bulk user exports and provides better visibility into user management status within your organization.
• Senders no longer need to set signing order for IDnow EU Qualified signatures
  Envelope setup is simplified by removing the requirement for senders to configure a signing order when adding recipients who use the IDnow EU Qualified signature type. This change streamlines the preparation process, making it quicker and easier to send envelopes that require this highly secure electronic signature.
• Docusign App Center Release Notes
  Account administrators now have enhanced control to approve or un-approve any third-party application for their Docusign accounts and individual users. This feature strengthens security and governance by centralizing control over which external apps can integrate with Docusign data.
• Persistent SMS Re-authentication for QES Agreement Access
  Security for European Qualified Electronic Signature (QES) agreements is improved by requiring recipients to re-authenticate via SMS every time they access an already signed agreement. This measure ensures that only the intended party can view highly sensitive, QES-signed documents, even after the signing process is complete.
• Starter Workspaces for Faster Workspace Setup
  Quickly begin using Docusign Workspaces with this new feature, which offers preconfigured content for common use cases like New Patient Intake and Hiring. By providing tailored draft envelopes and upload requests, this tool significantly reduces the initial setup time, allowing you to start automating processes immediately.
• Support for Additional Formatting Functionalities in Agreement Template Builder
  Users with access to Agreement Template Builder can now apply enhanced formatting options like strike-through, text highlighting, and clear formatting when creating and editing document templates. These new tools offer more control and precision, improving the visual quality and clarity of your agreements.
• Account Level Connect Dashboard Improvements
  Improvements to the Connect Dashboard dramatically increase the maximum number of downloadable logs from 500 to 10,000 and add a new filter to track manually republished envelopes. These changes provide administrators with greater visibility and more comprehensive data for monitoring the success and failure of Docusign Connect webhooks.
• Connect Failures Page Deprecated
  The legacy Failures page in Docusign Connect has been replaced entirely by the modern Connect Dashboard, which offers expanded log details and complete coverage for all Connect events. Customers should transition to the new dashboard for enhanced monitoring and deep-linking capabilities to streamline webhook management.
• Retrieve IDnow Evidence Directly Using Docusign APIs
  Customers can now simplify their compliance and evidence retrieval workflows by directly accessing IDnow partner evidence through Docusign APIs, eliminating the need for separate integrations. This new centralized process is set to accelerate time to value and make managing identity verification evidence more efficient.
• Legacy Authentication Migration Final Phase
  This is the final warning phase for the deprecation of legacy authentication methods, which will be fully disabled by March 31st, 2026. All integrations using basic user password authentication must migrate to the secure OAuth 2.0 protocol immediately to prevent service interruptions and align with industry best practices.
• Next Gen eSignature Experience Timeline Update
  An update is provided for the ongoing rollout of the bold new eSignature experience, which is transforming the document sending process for faster template preparation and better user conversion. Customers can review the status and opt-in details for the new user interface, which is set to become the standard experience.
• Advance Notice: Deprecation of Weak TLS 1.2 Ciphers (April 2026)
  Docusign is providing advance notice that it will discontinue support for the remaining two weak AES CBC ciphers in April 2026 to ensure the highest security standards across its APIs and endpoints. Customers must update any custom integrations or third-party connectors to support modern TLS 1.2 or TLS 1.3 cipher suites to maintain service continuity.

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 👇