Docusign is pleased to announce that the Docusign eSignature 26.1.02.00 Release Notes: May 2026, is now available on the Demo environment for customer testing.
🚀 What's new?
- Expiration date setting now matches Advanced Options setting
This fix ensures that the expiration date shown in the Advanced Options (Prepare) panel now uses the same logic as the Envelope Details view, correcting a prior mismatch. This is a UI-only change that provides senders with accurate information about the envelope's expiration time. - Limit Reminder Count for Envelope Recipients
A new account-level setting allows administrators to cap the total number of reminder emails sent to recipients for an envelope. This feature is key to reducing over-notification and gives both administrators and senders finer control over reminder behavior. - Branding resource files API access for senders
Authenticated senders can now retrieve brand resource files (email) for the brands they use via the eSignature REST API. This expands access beyond just logo and color metadata, enabling senders to ensure their branding is correctly applied in API-driven workflows. - Concatenate Text Fields in Maestro Write Steps
Process Builders can now combine up to three string variables with custom text when configuring writeback steps in Maestro. This capability is useful for dynamically generating unique identifiers, such as combining multiple IDs and names into a single contract name field before writing it back to a system of record. - String Field Concatenation in Maestro Read and Writeback Steps
Maestro's read and writeback steps now support concatenating multiple text variables and hard-coded text into a single field value. This feature helps Process Builders dynamically create string values to match or write to connected third-party systems. - Currency fields in Read and Writeback Maestro steps
Maestro now natively handles currency data when reading values from or writing them back to third-party systems like Salesforce and SAP Ariba. This simplifies workflows involving financial data by properly managing both the numeric component and the currency code. - New Option to Retrieve Multiple Records in Maestro Read Steps
Process Builders can now configure Maestro read steps to retrieve up to five matching records, instead of just a single record. This functionality is important for downstream workflow steps that need to process multiple related records, such as several contact records. - Populate Recipients with Third-Party Data in Maestro
Recipients in the "Send Document for Signature" step can now be dynamically populated using data retrieved from "Read from…" steps in Maestro. This automation allows for auto-populating agreement recipients using contact data directly from systems of record like Salesforce or HubSpot. - HTTP Web Request Extension
Maestro now includes an HTTP Web Request Extension that allows integration with virtually any external API or service using HTTP requests. This premium feature enables complex agreement workflows to connect with third-party or internal APIs without requiring a pre-built connector. - Custom signing branding in Maestro
Process Builders can now select and apply custom branding directly within a Maestro workflow's "Send Documents for Signature" or "Set Up Invite" steps. This ensures every email and signing session seen by recipients consistently reflects the organization's logo and color scheme. - New ID Verification sub-processors for electronic IDs
Docusign is introducing new sub-processors, IDura and ItsMe, to support the verification of electronic IDs from selected European countries. This update ensures continued and expanded support for ID Verification, with the sub-processors now visible in the ID Evidence files. - Document View, Inline Editing, and Sections for Web Forms
These enhancements make it safer and faster to transform complex PDFs and templates into guided Web Forms. Builders can now reduce configuration errors and speed up review cycles by viewing the original document side-by-side with the form and editing field details inline. - Legacy Authentication Deprecation: End-of-Life Deadline Delayed to September 2026
The deadline for deprecating Legacy Authentication has been delayed from March 31, 2026, to September 30, 2026. This extension provides impacted customers with more time to migrate to more modern, secure authentication methods before enforcement cutoffs resume. - Document Visibility Improvements
Document visibility rules are being updated to be strictly and consistently enforced across all envelope workflows, particularly complex routing and advanced recipient scenarios. These fixes address known bugs involving signing groups, API updates, and senders acting as recipients, ensuring proper access control. - Admin ability to Delete Shared Address Book Contacts from API
Account Administrators now have enhanced deletion capabilities via the API to remove shared contacts created by any user within the account. This update provides greater oversight for admins, helping to keep the account's shared address book accurate and up-to-date. - Update documentation for limits-related error codes and messages
Several API error messages and HTTP status codes related to usage limits have been updated for improved clarity and consistency with industry standards. Developers must review their error handling logic, as rate-limit errors will now consistently return a 429 status code instead of 400.
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 👇Â
Â
Back to Docusign.com

