Release Note Applicability

This publication applies to the Demo release for June 2026, version 26.2.00.00.

Important: Feature availability timing may vary. Each month, Release Notes include items from different parts of the Docusign product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

Redirect notices when navigating away from Docusign

We've updated how Docusign handles external links so that any time a user clicks a non-Docusign URL from within our product, we now show a brief 'you're leaving Docusign' notice.

This change is to strengthen security by preventing misuse of Docusign URLs as generic redirectors and to make it clearer to users when they are leaving our secure environment. After confirming, they're taken straight to the original destination page.

Availability

This change applies to customers on a free trial, and customers who have purchased plans from docusign.com or app stores.

Rollout schedule

The change will be live in Demo and Production in June.

Introducing Concurrent API Limits

To ensure platform stability and protect our infrastructure from incidents caused by the accumulation of long-running requests, we are introducing concurrent call limits for specific API actions.

Key details

• We are implementing a limit of 50 concurrent calls within a 5-minute window and 100 concurrent calls within a 60-minute window (utilizing an automatic 1-minute rolling window) per account, per action.

Impacted Endpoints

• PostEnvelopes
• PutEnvelope
• PostTemplates
• PutTemplates
• PutTemplate
• PostRecipients
• PutRecipients
• PostRecipientTabs
• PutRecipientTabs
• PutTemplatePart

Important:

This stability measure will not impact 99.99% of normal traffic. If your integration does hit the limit of 50 concurrent calls for a single action, the workaround is simply to wait a few seconds and initiate the call again.

Support for Bulk Send API Customizable Pre-fill Tabs

Bulk Send Lists and Send APIs now support Prefill tabs to be incorporated into the bulk send mailing list and can be used to populate the envelope with customizable prefill tab values.

Currently, we only support text field prefill tabs (radio, list, and other options are not yet supported).

Key details

• The PrefillTabs property is a collection that allows you to send customized pre-populated tab values in a bulk send operation.
• This enables you to set default values for prefill tabs, or document tabs, at the envelope level (unlike regular tabs which are associated at a recipient level).
• Prefill tabs are a top-level array property underneath the bulkCopies (bulkSendingCopy) on the POST bulk_send_list payload.
• Each BulkSendingCopyPrefillTab element contains:

{
  TabLabel : "tabLabelHere"
  InitialValue : "Initial value here"
}

TabLabel (string): The unique label identifier of the tab to prefill

InitialValue (string): The value to set for the tab.

Error codes

• BULK_SEND_ENVELOPE_PREFILL_TAB_NAME_MUST_BE_UNIQUE
  • Prefill tabs must have distinct names. The field {0} appears more than once in a copy.
• BULK_SEND_ENVELOPE_PREFILL_TAB_NAME_REQUIRED
  • All prefill tabs must have names.
• BULK_SEND_ENVELOPE_PREFILL_TAB_VALUE_REQUIRED
  • Prefill tab {0} has no value. A prefill tab can have an empty value, but it cannot have a null value.
• BULK_SEND_ENVELOPE_HAS_NO_ENVELOPE_PREFILL_TABS
  • Bulk sending list contains prefill tabs, but the specified envelope does not.
• BULK_SEND_ENVELOPE_PREFILL_TAB_DOES_NOT_EXIST_IN_ENVELOPE
  • PrefillTab {0} does not exist in the envelope.
• BULK_SEND_ENVELOPE_PREFILL_TAB_NAME_DOES_NOT_MATCH
  • PrefillTab names must match. {0} and {1} do not match.

Recommendations and advice

• Tab Label Matching: Ensure the TabLabel values match exactly with the tab labels defined in your document template.
• Empty Array Initialization: When no prefill tabs are needed, use the default empty array rather than null or don’t add the property at all, if you're not using one.
• Data Validation: Validate that InitialValue data conforms to the tab's expected format (e.g., date format for date tabs). Actual pattern validation happens later in envelope creation and cause the envelope generation to fail during sending.
• Performance: For large bulk sends, consider the memory implications of prefilling many tabs
• Prefilled tabs can typically be modified by recipients unless the tab is marked as read-only on the master/draft envelope used for bulk sending.
• This property is part of the bulk send configuration and applies to each copy sent in the batch: every recipient will see and interact with this, similar to prefill tabs in a regular envelope.

Availability

This update applies to all Docusign accounts, plans, and environments. No additional configuration is required as the updates are applied automatically.

Rollout schedule

• Demo: June 1-3, 2026.
• Production: June 4-15, 2026.

Reduced Friction During Digital Signature Completion Process with New Customization Capabilities

What's changing

Signers can now complete the Advanced (AES) and Qualified (QES) electronic signature-mandated identity verification after reviewing the document, keeping review, verification, and signing in a single, continuous flow.

Why it matters

• Reduces friction by allowing recipients to confirm the agreement contents before completing identity verification.
• Improves completion rates by ensuing only engaged signers complete identity verification
• Aligns the signing experience with other leading AES and QES providers.

How it works

When the account Admin activates the new, respective identity configuration, the Sender will be able to select it while customizing an envelope:

• For AES: ID Verification for EU Advanced at Signing
• For QES: ID Verification for EU Qualified at Signing

The recipient can then preview the agreement, and only once satisfied and willing to sign it will they be prompted to complete the required identity verification process. Once verification is successful, the signer is automatically returned to the document to complete signing.

Availability

This capability is available to all AES and QES customers.

Rollout Schedule

Production: GA end of June 2026.

Improvements to the Docusign ID Verification Participant Flows

In June, we will update the identity selection screens for participants who are completing an ID document verification as part of their agreement. These updates make it easier for participants to access their reusable or electronic IDs from the selection screen.

Participants will see an updated UI when selecting an identity verification method: their physical ID document, their CLEAR account, or another form of electronic ID.

Availability

The new UI will be enabled by default for all customers using Docusign ID verification as part of their agreement process.

Rollout schedule

• Demo: First week of June, 2026.
• Production: Rollout begins June 8, 2026.

Federal UX Optimization for PIV/CAC Signers

This release introduces critical user experience (UX) enhancements specifically for our Federal Market users who sign documents using Personal Identity Verification (PIV) and Common Access Card (CAC) smart cards.

The changes significantly streamline the signing process, reducing friction and improving success rates for smart card authentication.

Key details

The primary goal of this update is to simplify and stabilize the signing process for smart card users.

• Removal of Signing Reason Requirement: The most significant change is the elimination of the mandatory Signing Reason field during the smart card signing process. This removes an unnecessary step and accelerates completion for PIV/CAC signers.
• Optimized Authentication Steps: We have reorganized and streamlined the steps required for PIV/CAC authentication, resulting in a cleaner, more intuitive user flow.
• Reduced Friction: This release eliminates previously unnecessary steps or confusing prompts, allowing signers to move through the process more efficiently.
• Enhanced Compatibility: Updates were made to improve compatibility with various smart card readers and federal environments.

Impact

These updates are designed to:

Target Audience | Impact
Federal PIV/CAC Signers | High: Expect a much faster and more reliable signing experience due to the removal of the Signing Reason field and general flow optimizations.

Availability

This feature is rolling out to all Federal Market accounts.

Rollout schedule

The rollout for this feature started in April 2026.

Spanish and Portuguese Support for AI Summary and Q&A During Signing

AI-assisted features in signing now support Spanish and Portuguese signing experiences, in addition to English. This update allows signers to view AI summaries and interact with Q&A while using the Docusign signing interface in Spanish or Portuguese.

These improvements are available on desktop and mobile devices.

Key details about this feature

1. AI-Assisted Agreement Summary:

• Signers can view a concise summary and key points extracted from the agreement. Summaries are always generated in the language of the signing interface

For example:

• If the signing interface is English, the summary appears in English.
• If the signing interface is Spanish, the summary appears in Spanish.
• If the signing interface is Portuguese, the summary appears in Portuguese.
• The language of the signing interface is determined based on sender's settings for the interface language, the signer's browser language, or the signer's own account preferences.
• Signers can also change the interface language using the language selector in the signing experience.

1. AI-Assisted Q&A:

• Signers can ask natural-language questions about the agreement and receive grounded, document-based answers. Answers are generated in the language used in the question.

For example:

• If a signer asks a question in Spanish, the answer will be returned in Spanish.
• If a signer asks a question in English, the answer will be returned in English.
• This allows signers to interact with AI-assisted features in the language they prefer while reviewing agreements.

Frequently asked questions

• Is agreement language relevant?
  The behavior of AI Summary and Q&A depends on the interface language and the question language, not the agreement language itself.
• Are Admin settings respected?
  If a sender's account has opted out of the setting for AI features in signing, this expansion does not change that setting. AI Summary and Q&A will remain unavailable for agreements sent from that account.
  If AI-assisted features in signing are enabled, the summary and Q&A tools will appear automatically — no additional setup is required.
  Agreement senders on plans purchased digitally do not have access to control this setting and it remains enabled by default.

Availability

Customers who fall under the following criteria have access to this feature:

• Agreements sent from AU, CA, EU, JP1, and NA site accounts.
• Signing interface set to Spanish or Portuguese.
• Single- or multi-document envelopes meeting existing eligibility requirements.
• Supplemental documents are excluded from AI Summary and Q&A processing.
• Available on desktop and mobile devices.

This feature is not available in embedded signing flows, CFR Part 11 agreements, or FedRAMP and GovRAMP agreements.

Rollout schedule

• Demo: May 20, 2026.
• Production: May 30, 2026.

What's next?

We plan to support French, German, and Japanese signing experiences by June 2026.

German, French and Japanese Support for AI Summary and Q&A During Signing

AI-assisted features in signing will soon support German, French, and Japanese signing experiences, in addition to English, Spanish, and Portuguese. This update allows signers to view AI summaries and interact with Q&A while using the Docusign signing interface in these languages.

These improvements are available on desktop and mobile devices.

Key details about this feature

1. AI-Assisted Agreement Summary:

• Signers can view a concise summary and key points extracted from the agreement. Summaries are always generated in the language of the signing interface

For example:

• If the signing interface is French, the summary appears in French.
• If the signing interface is German, the summary appears in German.
• If the signing interface is Japanese, the summary appears in Japanese.
• The language of the signing interface is determined based on sender's settings for the interface language, the signer's browser language, or the signer's own account preferences.
• Signers can also change the interface language using the language selector in the signing experience.

1. AI-Assisted Q&A:

• Signers can ask natural-language questions about the agreement and receive grounded, document-based answers. Answers are generated in the language used in the question.

For example:

• If a signer asks a question in German, the answer will be returned in German.
• If a signer asks a question in English, the answer will be returned in English.
• This allows signers to interact with AI-assisted features in the language they prefer while reviewing agreements.

Frequently asked questions

• Is agreement language relevant?
  The behavior of AI Summary and Q&A depends on the interface language and the question language, not the agreement language itself.
• Are Admin settings respected?
  If a sender's account has opted out of the setting for AI features in signing, this expansion does not change that setting. AI Summary and Q&A will remain unavailable for agreements sent from that account.
  If AI-assisted features in signing are enabled, the summary and Q&A tools will appear automatically — no additional setup is required.
  Agreement senders on plans purchased digitally do not have access to control this setting and it remains enabled by default.

Availability

Customers who fall under the following criteria have access to this feature:

• Agreements sent from AU, CA, EU, JP1, and NA site accounts.
• Signing interface set to French, German, or Japanese.
• Single- or multi-document envelopes meeting existing eligibility requirements.
• Supplemental documents are excluded from AI Summary and Q&A processing.
• Available on desktop and mobile devices.

This feature is not available in embedded signing flows, CFR Part 11 agreements, or FedRAMP and GovRAMP agreements.

Rollout schedule

• Demo: June 16, 2026
• Production: June 30, 2026

Support for Improved Document Formatting in Agreement Template Builder (ATB)

Word documents uploaded into the Agreement Template Builder (ATB) now retain more complex formatting, such as lists, styling, and structure, delivering higher fidelity and reducing manual cleanup.

With improved formatting support and faster performance, users can move from Word to template creation more seamlessly and focus on building templates that matter most.

Availability

This feature is available by default for all ATB customers:

• IAM (all plans)
• eSignature: customers with the Doc Gen add-on only

Rollout schedule

This functionality is available in both Demo and Production environments as of May 1, 2026.

Support for Collapse and Expansion of Left hand Panel in Agreement Template Builder

Users can now collapse and expand the left panel, making it easier to work on smaller screens. This provides a way to hide the panel and give more space to focus on building templates with fewer distractions.

Availability

This feature is available by default for all ATB customers:

• IAM (all plans)
• eSignature: customers with the Doc Gen add-on only

Rollout schedule

This functionality is available in both Demo and Production environments as of May 1, 2026.

Custom ID Verification Configurations Now Enforce Accepted ID Restrictions for Simple and Advanced Signatures

To improve the accuracy of ID Verification for Simple and Advanced Signatures, Docusign now enforces stricter rules for accepted IDs in customized identity configurations.

When administrators select a customized list of accepted IDs in the Advanced settings > Accepted IDs > Manage section of a simple or advanced ID Verification configuration, recipients cannot submit an ID document outside of this list.

Key details

Previously, when a simple or advanced ID Verification configuration included a customized list of accepted ID documents, recipients could submit an ID outside that list if the ID verification partner accepted it.

Now, ID Verification only accepts the ID documents that administrators have selected in the list of accepted IDs of the ID Verification configuration. If a recipient submits an ID document outside that list, ID Verification declines it.

Note: This change applies to any new or existing simple or advanced ID Verification configurations that customers have created. It does not affect any system-owned configurations, which accept all ID types by default.

Availability

This feature will be enabled by default for all Docusign Identity Verification customers who are using custom ID Verification configurations for simple and advanced signatures.

Rollout schedule

• Demo: first week of June
• Production: mid-June

Original source

Release Note Applicability

This publication applies to the Demo release for May 2026, version 26.1.02.00.

Important: Feature availability timing may vary. Each month, Release Notes include items from different parts of the Docusign product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

Expiration date setting now matches Advanced Options setting

A mismatch between the expiration date shown in Advanced Options and the actual envelope expiration time for senders has been fixed.

Key details

• What changed: The Advanced Options (Prepare) panel now uses the same logic as the Envelope Details view when displaying the envelope expiration date.
• Behavior and API impact: This is a UI-only change. Underlying expiration behavior and APIs are unchanged.

Rollout schedule

• Demo: Early May 2026
• Production: Mid-May 2026

Limit Reminder Count for Envelope Recipients

We're introducing a setting to limit the number of reminder emails sent to recipients for an envelope. This helps reduce over-notification and gives administrators and senders finer control over reminder behavior. By default, this setting is off, ensuring your existing reminder behavior remains unchanged.

Key details

• New account-level setting to cap the total number of reminder emails for recipients on an envelope. Once the maximum is reached, reminders stop, or earlier if the envelope completes or expires.

• Valid range for the maximum reminder count is 1–999.

• When enabled, reminders follow your configured delay and frequency until the maximum is reached, or the envelope completes/expires (whichever comes first).

• Administrators can configure this in the Admin experience (Reminders and Expiration). New configuration options:

  • Checkbox: Limit number of reminders
  • Input value: Maximum reminders

  If the checkbox is off, the input option is disabled.

• If your reminder settings allow for senders to override account defaults, senders can adjust the limit using the Advanced Options settings that are available when preparing and envelope or template. If overrides are not allowed, these settings are shown as read-only.

API support

A new maximumReminderCount field is available in the reminders payload:

"notification": { "useAccountDefaults": "false", "reminders": { "reminderEnabled": "true", "reminderDelay": "3", "reminderFrequency": "2", "maximumReminderCount": "10" } }

Availability

This enhancement will be available for all Docusign eSignature and IAM plans

Rollout schedule

• Demo: Late April 2026
• Production: Mid- to late May 2026

Branding resource files API access for senders

We are expanding brand access in the eSignature REST API so that authenticated senders can now retrieve brand resource files (email) for the brands they already use, in addition to the existing logo and color metadata. Note: Account administrators already had access these files with full CRUD rights.

Key details

• What's new: Senders who can already access a brand by the API now have credentials to GET that brand's resource files, not just its logo and colors.
• Permissions: Sender access to the brand resource files is read-only (GET). They cannot create, update, or delete brands or resource files (no POST, PUT, or DELETE calls). Those actions remain restricted to admins.

Rollout schedule

• Demo: Late April 2026
• Production: Late May 2026

Concatenate Text Fields in Maestro Write Steps

Process Builders can now concatenate up to three string variables along with custom text when configuring Writeback to… steps such as Writeback to Coupa.

Why it matters to you

For example: with dynamically generated text values, you can combine a Requisition ID, Line Item ID, and Supplier Name into a single unique contract name field, like REQ12345-LINE001-AcmeSuppliers, and write it back to the system of record.

How to use it

When configuring a Writeback to… step, use the multi-variable selector to choose the string variables you want to combine. You can insert hard-coded text (like hyphens or prefixes) between variables to format the output string.

Availability

This feature is available to all Docusign IAM plans.

Rollout schedule

All Demo and Production environments: April 1, 2026

String Field Concatenation in Maestro Read and Writeback Steps

Maestro Read from… and Writeback to… steps now support concatenating multiple text variables and hard-coded text into a single field value.

Key details

Process Builders can combine up to three string variables along with hardcoded text (such as dashes or spaces) when mapping fields in Write to… steps like Writeback to Salesforce, Writeback to Coupa, and other writeback steps. They can do the same when setting up rules in Read from... and Writeback… steps.

Why it matters to you

This feature helps Process Builders to dynamically generated string values to be written to connected third-party systems, for example, combining a requisition ID, line item ID, and supplier name into a single contract name field.

How to use it

When configuring a Write to… step in Maestro, select a string field and use the rich text input to combine up to three string workflow variables with optional hard-coded text.

Concatenation is available for string fields only and is not supported for Boolean, array, or other field types. When creating rules for records to read or write, use concatenation to dynamically create string values to match.

Availability

This feature is available to all Docusign IAM plans.

Rollout schedule

Demo and all Production environments: April 2, 2026.

Currency fields in Read and Writeback Maestro steps

You can now read currency values from your systems of record and write them back in Maestro.

Key details

Maestro natively handles currency data from third-party systems like Salesforce and SAP Ariba.

Why it matters

Handling currency fields from third-party systems is simple now. Maestro properly manages both numeric and currency code field components when reading and writing your data.

How to use it

When configuring reading or writing data from third-party systems, you'll see Currency fields alongside other supported data types including string, double, and datetime.

Availability

This feature is available on all Docusign IAM plans.

Rollout schedule

All Demo and Production environments: May 19, 2026.

New Option to Retrieve Multiple Records in Maestro Read Steps

You can now configure Maestro Read from… steps to retrieve up to five records.

Key details

When defining rules in steps like Read from Salesforce, you now have two choices: read a single record (the default) or read up to five matching records.

Why it matters

You can return more than one record (for example, multiple contact records) when downstream Maestro steps need them.

How to use it

When setting rules to specify which records to read from, select Multiple Records when prompted with How many records should this step return?.

Note: Some Read from… steps for third-party apps already fetch multiple records. These steps will continue to be set to Multiple Records.

Availability

This feature is available for all Docusign IAM plans.

Rollout schedule

All Demo and Production environments: April 10, 2026.

Populate Recipients with Third-Party Data in Maestro

You can now populate recipients in the Send Document for Signature step with data from Read from… steps in Maestro.

Why it matters

Auto-populate agreement recipients with data from your system of record, like Salesforce, HubSpot, MS Dynamics, and others.

How to use it

1. In a Read from… step, select a Related List (for example, a list of Contacts related to your Account record in Salesforce)
2. Map Participant fields (for example, First Name, Email Address) to the corresponding fields from the selected list.
3. In the Send Document for Signature step, select a recipient by choosing Add participant > Add dynamic list of recipients > Dynamic recipients.

Availability

Available on all Docusign IAM plans.

Rollout schedule

All Demo and Production environments: May 19, 2026.

HTTP Web Request Extension

Maestro now includes an HTTP Web Request Extension, giving you the ability to integrate your agreement workflows with virtually any external API or service, without needing a pre-built connector.

HTTP Web Request Module

The Web Request module lets you send HTTP requests (GET, POST, and PUT) to any external endpoint as a step in your Maestro workflow. You can pass data from earlier steps into the request and use the response to drive what happens next, including branching logic based on the result or get data from the endpoint to bring into your Maestro workflow.

Key capabilities

• Connect to any third-party or internal API without waiting for a dedicated integration
• Authenticate using Basic Auth.
• Map workflow variables into request headers and body, and capture API responses as new variables for downstream steps

Availability

The HTTP Web Request Extension is a premium feature and is available to customers on a Docusign IAM Professional Plan and above.

Rollout schedule

• Demo: May 5, 2026
• Production: May 13, 2026

Custom signing branding in Maestro

You can now select custom branding directly within a Maestro workflow, so every email and signing session your recipients see reflects your organization's logo and colors.

What's new

In the Send Documents for Signature and Set Up Invite steps, choose a signing brand to apply. A visual preview shows the logo and color theme before you publish.

Note: If a template owner or administrator has turned off Allow senders to edit the logo and brand colors in the template's Advanced Options, the branding defined on that template can't be changed in the workflow.

Getting started

Ask your admin to configure custom signing brands under Admin > Brands > Signing. For more details, see: Docusign Account Administration: Add a Signing Brand for Recipients.

Plan availability

Available on all Docusign IAM plans.

Release dates

• Demo: Currently available
• Production: April 15, 2026

New ID Verification sub-processors for electronic IDs

In May, we will introduce two new sub-processors, IDura and ItsMe, to provide support in verifying electronic IDs from selected European countries.

Customers who use Docusign ID Verification for Simple and Advanced Signatures will see the sub-processors used to verify the ID when they view the ID Evidence files associated with an identity verification. ID Evidence files can be accessed by the envelope or the ID Evidence API.

Customers can continue to send envelopes and IAM processes involving Docusign Identify without interruption.

Availability

This is available to all plans that include Identify, except for customers using Docusign ID Verification in Japan.

Rollout schedule

• Demo: ramp begins May 4, 2026.
• Production: gradual rollout starting on May 11, 2026 and continuing to the end of the month.

Region applicability

This change applies to all regions, except Japan.

Document View, Inline Editing, and Sections for Web Forms

The Document View, Inline Editing, and Sections enhancements make it faster and safer to turn complex PDFs and templates into guided Web Forms. Builders can see the original document and the generated form side by side, then update field labels and descriptions directly in the builder, reducing manual rework and configuration errors before forms go live.

Key details

Document View (viewing document and form side by side)

• Shows the Web Form and the underlying PDF or eSignature template next to each other inside the Web Forms builder, so builders always see exactly where a field displays on the original document.
• Highlights the matching field on the document when a form field is selected (and vice versa), making it easy to understand and adjust mappings between document fields and form components.
• Can be toggled on or off from the builder, so builders can focus on the form outline when they don't need the document view.

Inline Editing (edit directly in the builder)

• Lets builders edit field labels and descriptions directly on the form canvas without opening separate dialogues or switching tools.
• Supports editing for the most common field types used in Web Forms today, including text, checkbox, radio button, and dropdown fields.
• Designed to reduce common configuration errors and speed up review cycles, with success metrics focused on lowering Web Form error rates after launch.

Sections (multilevel form structure)

• Introduces a three-level outline of Pages, Sections, and Fields, so long forms can be broken into smaller, logical chunks that match the structure of the original PDF.
• Lets builders add sections directly from the component menu and configure section titles, subtitles, and rules to guide signers step by step through the form.

Availability

Document View and Inline Editing are available on eligible eSignature and IAM plans that include Web Forms. These features will be automatically enabled for all accounts with Web Forms.

Rollout schedule

• Demo: April 17, 2026 (for demo accounts where Web Forms have been enabled).
• Production: GA scheduled for May 2026.

Region availability

This enhancement applies to all geographical regions.

Original source

Docusign eSignature 26.1.01.00 Release Notes: April 2026

Also in Docusign eSignature 26.1.01.00 Release Notes: April 2026

Last updated: Mar 18, 2026

Tags
Docusign eSignature
eSignature
Release Note

Release Note Applicability

Important: Feature availability timing may vary. Each month, Release Notes include items from different parts of the
Docusign
product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

Advance Notice: Deprecation of Weak TLS 1.2 Ciphers (April 2026)

As part of our commitment to maintaining the highest security standards, we are entering the final phase of our TLS 1.2 weak cipher deprecation. Following the initial removal of weak ciphers in February 2023, Docusign will discontinue support for the remaining two weak AES CBC ciphers in April 2026.

Impacted Ciphers

Effective April 2026, the following cipher suites will no longer be supported by Docusign APIs and endpoints:

• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
  • OpenSSL name: ECDHE-RSA-AES256-SHA384
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
  • OpenSSL name: ECDHE-RSA-AES256-SHA

Action Required

Customers must ensure that their integrations, client applications, and third-party connectors are updated to support modern, secure cipher suites before April 2026.

1. Review Custom Integrations: If you maintain a custom-built integration, ensure your server or client configuration is not hardcoded to exclusively use the impacted ciphers.
2. Check Third-Party Vendors: If you use a third-party connector to connect to Docusign, please verify with your vendor that their solution supports modern TLS 1.2 or TLS 1.3 ciphers.

Streamlined Envelopes List Experience

Streamlined Envelopes List Experience

We have updated the Envelopes list to make your agreement management more efficient. While the interface maintains the familiar patterns you know, we have introduced key functional improvements to search, filtering, and list customization to help you work faster.

Key Improvements

• Intuitive Search: Find what you need with less effort. New quick-click filters help narrow results instantly, and the system now remembers your previous searches so you can pick up right where you left off.
• Enhanced Filter Feedback: Gain total clarity on your current view. We've improved the filter controls to provide better visual feedback, making it easier to see which criteria are active and toggle them on or off.
• Personalized Columns: You now have the control to hide or show specific columns, allowing you to customize the list view to show only the information most relevant to your workflow.
• Predictable Navigation: We've optimized the list's performance for more reliable loading. You can now also control the number of rows per page, giving you more flexibility in how you browse your agreements. Additionally, we've implemented search parameter sanitization to ensure your browser URL always contains clean, valid values that accurately reflect your current view.

Availability

This is available for all eSignature plans through an automated update. No manual changes are needed to your account settings.

Rollout Schedule

Demo:

• March 16, 2026: 25%
• March 18, 2026: 50%
• March 19, 2026: 100%

The rollout schedule for production will be shared at the end of the demo phase.

Enhanced Signing Group Collaboration

Enhanced Signing Group Collaboration

We are evolving the Signing Group experience to eliminate envelope locking and streamline how teams review and sign agreements. Previously, if one member started signing, the envelope was locked to others, potentially causing delays.

With this update, we're introducing concurrent viewing and immediate takeover to ensure recipients stay moving.

Key enhancements

• Concurrent Access & View-Only Mode: No more Access Denied errors. All members of a signing group can now enter an agreement simultaneously. While one person is actively signing, others can view the document in a read-only mode.
• Collaborative Review Tools: Even in read-only mode, group members can use signing as a tool. You can use AI Summary and Q&A, add comments, download, or review the document history, without interrupting the active signer.
• Immediate "Takeover" Capability: We've eliminated the need to wait for a session to time out for the envelope to unlock to other members. If the active signer leaves the session or closes the tab, any other group member can immediately take over the session to complete the signing process.
• Real-time Status Indicators: Changes in the user interface will let recipients know exactly who is currently signing and when the document is available to take control.

Rollout Schedule

• Demo: Early April
• Production: Late April (for select early adopters)

Connect Auto-Retry Changes

Connect Auto-Retry Changes

Connect listeners can become unavailable for a variety of reasons, including transient network issues, storage capacity limits, and other external factors. To improve reliability, we are enforcing auto-retries for all Connect traffic.

With auto-retries, customers gain an automated path to recover from temporary disruptions without needing to manually republish events. In addition, Connect dashboards will more accurately reflect true successes and failures, providing clearer visibility into delivery outcomes.

When will this be enforced?

Auto-retries will be enforced for all accounts by the end of May through a rolling release.

Can I enable this now?

Yes. You can enable auto-retries today by turning on the Require Acknowledgement setting in your Connect configuration.

What if my listener is overloaded from Auto-Retries?

Customers can pause a Connect configuration to reduce load on their listener while they investigate and resolve the underlying issue.

What is the Auto-Retry Schedule?

If message delivery for a given envelope fails, retries will be attempted using exponential back-off. The retry attempts will be made in the following sequence:

• Five minutes later
• 10 minutes later
• 20 minutes later
• 40 minutes later
• One hour later
• Two hours later
• One day later
• Once per day for a 15-day span

User authentication tracking captured in Envelope History

User authentication tracking captured in Envelope History

To support stricter security and audit requirements, envelope history now records when signer authentication is completed as part of accessing an envelope.

Key details

With this enhancement:

• Envelope History now includes a dedicated event when signer authentication is performed by password as part of signing. This creates a clearer, per-envelope audit trail showing that a recipient successfully completed authentication before viewing or signing an agreement.
• Authentication events are logged when recipients log in to Docusign when accessing the envelope.
• Security and compliance teams gain stronger evidence for access reviews and investigations, helping demonstrate that appropriate authentication took place for sensitive envelopes.

Availability

This enhancement will be available to all customers in April.

New Record Count Field for Maestro Steps

New Record Count Field for Maestro Steps

Maestro Read from... steps for retrieving data from connected third-party accounts now return checkbox and dropdown variables.

Key details

• Read from Salesforce, Read from Microsoft Dynamics 365, and other Read from... steps now return Checkbox variables as boolean, and Dropdown variables as string.

To use it on new Read steps, no additional setup is needed. For existing steps, open the step and save it again to access the new Record Count variable. Then use the Record Count Integer variable in downstream Maestro steps.

Availability

This feature is available to all Docusign IAM plans.

Rollout schedule

All Demo and Production environments: March 25, 2026.

New Checkbox and Dropdown Variables for Maestro Steps

New Checkbox and Dropdown Variables for Maestro Steps

Maestro Read from... steps for getting data from connected third-party accounts now return checkbox and dropdown variables.

Key details

• Read from Salesforce, Read from Microsoft Dynamics 365, and other Read from... steps now return Boolean and string values for checkbox and dropdown fields, respectively.

Why it matters to you

Use these values from third-party systems to populate checkbox and dropdown fields in Maestro steps downstream from a Read step, for example, in a Collect Data with Forms step.

Availability

This feature is available to all Docusign IAM plans.

Rollout schedule

All Demo and Production environments: March 25, 2026.

AI Summary and Q&A now support embedded signing experiences

AI Summary and Q&A now support embedded signing experiences

We're expanding AI-assisted features in signing to support embedded signing experiences, allowing signers to access AI Summary and Q&A when signing agreements within applications that integrate DocuSign through embedded signing.

This enhancement helps more signers understand agreements quickly and confidently, even when signing occurs directly within third-party applications.

This capability continues to support single-document and multi-document envelopes (up to 150 total pages) and is available across global sites — AU, CA, EU, JP1, and NA.

These improvements are available on desktop and mobile devices.

How do AI features work in Embedded Signing?

When embedded signing is used:

• AI Summary and Q&A will appear within the signing interface if the envelope meets eligibility criteria.
• The features function the same as in standard signing experiences.
• There is currently no API parameter available to disable AI-assisted features for embedded signing sessions. Feature availability is controlled exclusively through the sender account's admin settings.

For more information about embedded signing, see:
Developer Center: Embedded signing.

Note:
AI-assisted signing tools are not displayed in Focused View.

The focused view intentionally removes the signing toolbar and supporting tools from the user interface. Because AI Summary and Q&A are accessed through signing tools, they are not available in this view.

How Embedded Signing works with the sender's admin settings

• Admin settings configured on the sender's account continue to determine whether AI-assisted features appear during signing.
• If a sender's account has already opted out of AI-assisted features in signing, AI Summary and Q&A will remain unavailable in all signing experiences, including embedded signing.
• If AI-assisted features are enabled, AI Summary and Q&A will appear automatically during signing when eligibility criteria are met.
• No additional configuration is required to enable these features in embedded signing.
• Agreement senders on Digital plans (purchased online) do not have access to control this setting.

For details on managing AI-assisted signing features, review this article:
Turn Off the AI Tools for Signing Setting in Account Administration.

Note:
Content from supplemental documents included in the envelope is not used to generate the AI summary. Only primary agreement documents are used.

Availability

This feature is available to customers who fulfill the following criteria:

• Sends agreements from AU, CA, EU, JP1, and NA site accounts.
• Agreements opened with Signing Interface language set to English.
• Single- or multi-document envelopes with up to 150 pages total.
• Envelope size under 23 MB.
• Supplemental documents are excluded from AI Summary and Q&A processing
• Available in embedded signing experiences
• Not available for CFR Part 11 agreements, CFR Part 11 agreements, or FedRAMP/GovRAMP agreements
• Not available in embedded signing experiences

Rollout schedule

• Demo: March 19, 2026
• Production: April 6, 2026

Dates may vary slightly depending on deployment schedules.

AI Summary and Q&A are available for Spanish and Portuguese signing

AI Summary and Q&A are available for Spanish and Portuguese signing

AI-assisted features in signing now support Spanish and Portuguese signing experiences, in addition to English. This update allows signers to view AI summaries and interact with Q&A while using the Docusign signing interface in Spanish or Portuguese.

These improvements are available on desktop and mobile devices.

AI-Assisted Agreement Summary

Signers can view a concise summary and key points extracted from the agreement.

Note:
Summaries are always generated in the language of the signing interface.

For example:

• If the signing interface is English, the summary appears in English.
• If the signing interface is Spanish, the summary appears in Spanish.
• If the signing interface is Portuguese, the summary appears in Portuguese.

The language of the signing interface is determined based on sender's settings for the interface language, the signer's browser language, or the signer's own account preferences. Signers can also change the interface language using the language selector in the signing experience.

AI-Assisted Q&A

Signers can ask natural-language questions about the agreement and receive grounded, document-based answers.

Note:
Answers are generated in the language used in the question.

For example:

• If a signer asks a question in Spanish, the answer will be returned in Spanish.
• If a signer asks a question in English, the answer will be returned in English.

This allows signers to interact with AI-assisted features in the language they prefer while reviewing agreements.

Attention:
The behavior of AI Summary and Q&A depends on the interface language and the question language, not the agreement language itself.

How this feature works with Admin Settings

• If a sender's account has opted out of the setting for AI features in signing, this expansion does not change that setting. AI Summary and Q&A will remain unavailable for agreements sent from that account.
• If AI-assisted features in signing are enabled, the summary and Q&A tools will appear automatically. No additional setup is required.
• Agreement senders on plans purchased digitally do not have access to control this setting and it remains enabled by default.

Availability

This feature is available to customers who fulfill the following criteria:

• Agreements sent from AU, CA, EU, JP1, and NA site accounts
• Signing interface set to Spanish or Portuguese
• Single- or multi-document envelopes meeting existing eligibility requirements
• Supplemental documents are excluded from AI Summary and Q&A processing
• Not available in embedded signing flows, CFR Part 11 agreements, or FedRAMP/GovRAMP agreements
• Available on desktop and mobile devices

Rollout schedule

The following dates are subject to changes:

• Demo: April 16, 2026
• Production: April 30, 2026

We expect to offer support for additional signing languages, such as French, German, and Japanese, are expected by June 2026.

App Center Release Notes

App Center Release Notes

Note that some of the following items are updates on previous months' Release Notes publication.

Configure Agreement Actions Connected Apps in App Center

Docusign has streamlined how you connect and manage applications, such as Google Drive, OneDrive, Sharepoint, Box, and Dropbox. The Connected Apps functionality for Agreement Actions has moved from the Admin Connections page to the unified App Center. This transition is part of a migration to Microsoft Azure.

This includes all existing Agreement Actions apps, as well as new eSignature. Send, and CLM.DS apps.

See the Use the Docusign App Center to Manage App Connections article for detailed information.

Availability

This feature is currently available in Demo and Production.

Agreement Action Connections have migrated to the App Center

The migration of Agreement Actions Connections to App Center is now complete for all regions.

You can now manage app connections in the App Center. Continue managing Agreement rules in the Admin Agreement Actions section.

These apps work with Agreement Actions, and are managed in App Center:

• Box
• Dropbox
• Google Drive
• OneDrive
• Sharepoint

Rollout schedule

This is currently available in the Demo and Production environments.

Extension App Approval

Admins can now approve and remove individual apps in the App Center. Docusign-built file archive extension apps are approved for all accounts that already have access to them.

Availability

This feature is currently available in Demo and Production.

Original source

Release Note Applicability

This publication applies to the Demo release for March 2026, version 26.1.00.00.
Important: Feature availability timing may vary. Each month, Release Notes include items from different parts of the Docusign product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

Docusign Workspaces availability for FedRAMP and GovRAMP Customers

Workspaces will be available for U.S. FedRAMP and GovRAMP customers in March for the following plans:

• IAM Enterprise for State and Local Government
• IAM Enterprise with FedRAMP
• IAM for CX for State and Local Government
• IAM for CX with FedRAMP

Additional Information

For more details, see the support documentation here.

Rollout schedule

• Demo: Mid-March 2026
• Production: End of March 2026

Redesigned eSignature Home Page

With this new homepage design, we offer:

• A new button bar in the header area that displays the three most recently used actions that the user had selected from the Start button menu.
• The overview counters have been repositioned to the right-hand side of the page. For users with access to Agreement Desk and Navigator, the overview will include Open Requests and Navigator Upcoming Renewals. Additionally, the counters look at the last 30 days instead of last six months.
• Tasks assigned to users are surfaced directly on the Home page; the five most recently assigned tasks from eSignature and CLM are displayed.
• The profile photo and signature image have been removed from the Home page; they can be accessed and updated through the profile menu by clicking Manage Profile.

Release dates

Phase 1: A toggle will appear on the Home page for users to optionally see the new page design.

• Target Demo ramp start: mid-February
• Target Prod ramp start: early March

Phase 2: The new homepage will show the default experience, but users will have the ability to toggle it off.

• Target Demo ramp start: mid-March
• Target Prod ramp start: early April

Phase 3: The new homepage will be the only experience, and the toggle will disappear.

• Target Demo ramp up: mid-April
• Target Prod ramp up: early May

This is an image of the toggle experience for eSignature customers.

AI Summary and Q&A Now Support Multi-Document Agreements

We’re expanding AI-assisted features in signing to support multi-document envelopes with a combined total of up to 150 pages, in addition to single-document agreements. This enhancement applies to agreements sent in English across all global sites (AU, CA, EU, JP1, and NA) helping more signers understand what they are signing with greater clarity and confidence.
These improvements are available on both desktop and mobile devices.

AI-Assisted Agreement Summary

Signers can view a concise summary and key points extracted from the full agreement (or multiple documents within the same envelope) making it easier to review complex agreements with confidence.
Note: Content from supplemental documents included in the envelope is not used to generate the AI Summary. Only main documents are used.

AI-Assisted Q&A

Signers can ask natural-language questions about the agreement and receive grounded, document-based answers. Q&A now works across multi-document envelopes, supporting agreements up to 150 total pages.
Note: Q&A responses are generated only from primary agreement documents. Information contained in supplemental documents is not included in answers.

Sender controls are respected

• If a sender’s account has already opted out of AI-assisted features in signing, this expansion does not change that setting. AI Summary and Q&A will remain unavailable for both single-document and multi-document envelopes sent from that account.
• If AI-assisted features in signing are enabled, the summary and Q&A tools will appear automatically — no additional setup is required.
• Agreement senders on plans purchased digitally do not have access to control this setting.

Availability

• Agreements sent from AU, CA, EU, JP1, and NA site accounts.
• Agreements written in English.
• Single- or multi-document envelopes with up to 150 total pages and under 23 MB in size.
• Supplemental documents are excluded from AI Summary and Q&A processing.
• Not available in embedded signing flows, CFR Part 11 agreements, or FedRAMP / GovRAMP agreements.

Rollout schedule

The features are expected to release on the following dates (dates may slightly vary):

• Demo: March 16, 2026.
• Production: March 30, 2026.

Manage eSignature and Digital Signatures Together in a Single Account

We are pleased to announce an important enhancement to the management of digital signatures and electronic signatures (e-signatures) in Docusign.
Previously, organizations were required to maintain separate sub-accounts to avoid losing access to features such as markup or payments when using digital signatures. With this update, both signature types can now be managed seamlessly within a single account.

Key Improvements

• Envelope-Level Configuration: Digital signature support is now determined at the individual envelope level, rather than being an account-wide setting. This provides greater flexibility for managing mixed signature workflows.
• Automated Compatibility: When an envelope is designated for digital signatures or includes an Identity Verification (IDV) workflow that requires them, Docusign will automatically adjust the envelope’s settings to ensure compatibility.
• Unified Account Management: Organizations can now support both standard eSignature and digital signature use cases within a single account, eliminating the need for sub-accounts and reducing administrative overhead.

Note: Customers adopting digital signatures for the first time should be aware that the user experience differs from standard e-signatures (for example, post-signing actions may be more limited).
For additional information, please refer to our FAQ: How digital signatures work.

Availability

This enhancement applies to existing accounts using digital signature, and any eSignature account that enables digital signatures add-ons.

Rollout schedule

The enhancement will be rolled out as follows:

• Demo: fully available now.
• Production: the feature will ramp up gradually throughout February, reaching global availability on March 16, 2026.

Modifications to Account Email Sender and Domain

To improve overall email deliverability, Docusign is migrating account-related emails such as, login, account recovery & security, and signup purposes, to a new sending domain, updated the “From” address, and sending using new IP addresses. These changes reduce the likelihood of false positives in spam filters and improve placement in inboxes.

Key details

Today we send account emails from the following domains:

• From name: Docusign via Docusign
• Email addresses:
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]
  • [email protected]

We are updating the From name, address and domain for all account communications:

• Demo:
  • From name: Docusign Demo Account
  • Email address: [email protected]
• Production:
  • From name: Docusign Account
  • Email address: [email protected]

We are also making routing updates: account communications will be sent from new IP addresses as part of the migration to third‑party providers, alongside existing IPs during the transition. See the complete list of email IP addresses in our Trust Center.

Previous Email Info vs New Email Info
This is an example of an email you might receive before this update:

• Sender Name: Docusign via Docusign
• Sender info: [email protected]

Here is an example of an email with the new address you might receive after this update is deployed:
Demo:

• Sender Name: Docusign Demo Account
• Sender info: [email protected]
  Production:
• Sender name: Docusign Account
• Sender info: [email protected]

Rollout schedule

The new email infrastructure rollout with a gradual ramp under the following schedule:

• Demo: Begins on February 18th.
• Production: Ramp is scheduled to commence on March 3rd.

This migration affects all regions and sites.

Important:

• Do not remove any previously allowlisted IP addresses while this migration is in progress.
• Accounts linked to a Custom Email Domain are not affected by this change as all account emails are sent from the customized domain.

WhatsApp Delivery: Enhanced Recipient Safety and Reporting

We’re improving WhatsApp Delivery to reduce fraud-related activity. This update introduces a clear way for recipients to report suspicious messages to Docusign.

Key details

• New “I don’t know this sender” interactive button in the Envelope Activation template lets recipients report suspicious messages directly from the thread; reports are routed to Docusign for investigation and abuse mitigation.

Rollout schedule

• Demo: Late February
• Production: Mid March

Customer impact and actions

• No action required. Recipients continue to see HELP/STOP guidance and may use the in-thread report option when unsure of the sender.

Bulk Send Now Supports Excel (.xlsx) Recipient Lists

With this update, you can upload Microsoft Excel (.xlsx) files directly to a bulk send envelope, eliminating the need to convert recipient lists to CSV.
This update streamlines preparation and helps reduce formatting errors caused by file conversion.

Key details

• You can upload a native .xlsx recipient list directly to a bulk send envelope instead of converting it first to CSV.
• Upload Excel (.xlsx) files during the Bulk Send process. Ensure column headers are in the first row, and for best results, use only single-sheet .xlsx files.
• Map your Excel columns to template roles just as you would with a CSV.

Rollout schedule

• Demo: Available in the second week of March.
• Production: Available in the fourth week of March.

TLS 1.3 support for Connect

To enhance the security and performance of Connect, we're enabling TLS 1.3 for all Connect traffic across Demo and Production environments by the end of April.

Key details

TLS 1.3 will be enabled in addition to existing TLS 1.2 support for all Connect traffic in Demo and Production environments.

Impact

No customer action is required. Existing integrations using TLS 1.2 will continue to work as usual.

Rollout schedule

We're enabling TLS 1.3 for all Connect traffic across Demo and Production environments by April 30, 2026.

Organization Bulk User Export Update

Some SCIM-enabled accounts with Organization Management may encounter failures when attempting to use the bulk action to export a list of users. The fix for this issue will deploy on March 9, 2026.

SCIM, or system for cross-domain identity management, is an industry-wide standard that enables organizations to manage users and groups through their identity providers. For more information, see SCIM for Docusign.

Key details

With this fix:

• All Organization bulk export users will see an additional column in their CSV export titled SCIMManaged.
• If the account is not on an IAM plan that includes user licenses, the column will be added as the last column (furthest to the right) in the report.
• If the IAM plan includes user licenses, SCIMManaged will be the second to the last column. If your organization does not use SCIM, the values in this column will be set to FALSE.

Availability

This update is available for Docusign accounts with Organization Management.

Rollout schedule

March 9, 2026.

Senders no longer need to set signing order for IDnow EU Qualified signatures

Senders can now add recipients who use the IDnow – EU Qualified signature type without configuring a signing order, simplifying envelope setup.

Key details

• Senders no longer need to set a signing order for envelopes that have recipients who sign using the IDnow – EU Qualified signature type.
• This change reduces setup steps and makes it faster to prepare envelopes that require a qualified electronic signature.
• For more information on how to add IDnow – EU Qualified recipients to an envelope, see Sending a Document Using a Qualified Electronic Signature.

Availability

This enhancement is available to all customers who use IDnow EU Qualified signatures.

Rollout schedule

The enhancement was rolled out in January 2026 for Demo and Production environments.

Docusign App Center Release Notes

Approved Apps Enhancements

Account admins can now approve any third-party application for their Docusign accounts, and any account user.
Key details

• This enhancement provides:
  • Admin Control: Account administrators can now approve and un-approve specific third-party applications for their Docusign accounts and individual account users.
  • Automatic Approval: Data Verification applications are automatically approved for accounts with access.
• For detailed information, see the Use Approved Apps article.

Availability

This feature is enabled by default.

Rollout schedule

• Demo environment: Enabled now
• Prod environment: February 12, 2026

Known Issues for Agreement Actions

The migration of Agreement Actions management from the Docusign Admin Connections page to the Docusign App Center was not completed as planned for the CA, EU, and NA regions.
Key details

• For customers in CA, EU, and NA sites: Continue to manage your connections through the Agreement Actions connections page until you are notified of a new migration window. When migration resumes, you will be temporarily unable to manage connections or rules during your active migration window.
• For customers in AU and JP sites: The production migration is complete, and your connections are now managed in the App Center.

Rollout Schedule

Migrations will be scheduled during low-traffic windows (weekends or week nights to minimize customer disruption.
When migration begins again, here's the expected timing:

• CA: Approximately 2 hours.
• EU:
  • Approximately 6 to 8 hours.
  • Three-five days after the CA migration.
• NA:
  • Three to four days, due to larger scope.
  • The team will share additional details once timelines are finalized.

Authentication bug

We are currently resolving an authentication bug that may occur when navigating from Docusign Admin to App Center and back to Docusign Admin.
This issue may cause error messages to display when Admin pages load. Until this is resolved, you can work around the issue by logging out of Docusign Admin and signing back in.
See the Use Docusign App Center to Manage App Connections article for more information.

Persistent SMS Re-authentication for QES Agreement Access

Docusign has improved agreement security by requiring SMS authentication every time a recipient accesses an already signed agreement. This option only applies to agreements signed with European Qualified Electronic Signatures (QES). It ensures only the intended recipient can view agreements, even after the signing process is complete.

Account administrators enable SMS re-authentication by activating the Recipient always verify option in the ID Verification QES configuration of their choice.

SMS re-authentication triggers after recipients have successfully verified their identity to access an envelope. From that moment on, they will have to authenticate via SMS each time they attempt to access the envelope, including after signing the document. For more information on this enhancement, review Verification of Government-Issued IDs for European Qualified Signatures.

Starter Workspaces for Faster Workspace Setup

Starter Workspaces is a new feature that helps you begin using Workspaces with preconfigured content.

Key details

If you have not yet created a workspace, you can select a preconfigured workspace for common use cases such as Account Opening, New Patient Intake, and Hiring.
Each Starter Workspace includes draft envelopes and upload requests tailored to that use case, which you can review, edit, and customize.

Availability

This feature will be available to all customers who have access to Workspaces in Docusign.

Rollout schedule

• Demo: Mid-February 2026
• Production: End of March 2026

Support for Additional Formatting Functionalities in Agreement Template Builder

Users will now be able to apply additional formatting functionality when creating and editing their document templates.

Key details

The following functions are being added:

• Strike-through: allows users to strike-through text within the document
• Text highlighting: lets users highlight text within the document
• Clear formatting: clears any existing formatting applied to text

Availability

This functionality will be available by default to users with access to Agreement Template Builder.

Rollout schedule

This enhancement will be available in both Demo and Production environment from the end of February 2026.

Account Level Connect Dashboard Improvements

We've increased the maximum number of downloadable logs in the Connect Dashboard from 500 to 10,000. We've also added a new Republish filter so you can directly track the successes and failures of manually republished envelopes.
These changes will be fully rolled out by early March.

Connect Failures Page Deprecated

We've deprecated the legacy Failures page in Docusign Connect and replaced it with the modern Connect Dashboard.
Key details

• The Failures page only showed a limited subset of logs for the original 11 Connect events. The new Connect Dashboard provides:
  • Expanded log details.
  • Complete success and failure coverage for all your Connect events.
  • Deep-linking so you can bookmark specific views and filters (after signing in, you'll return to the same view).
• We recommend that all customers use the Connect dashboard going forward.
• You can access the dashboard in Demo and Production accounts through Docusign Admin.
• Learn more: Connect Dashboard overview.

This change will be fully rolled out by early March.

Retrieve IDnow Evidence Directly Using Docusign APIs

Docusign is introducing a new process to retrieve IDnow partner evidence directly through Docusign APIs. Customers no longer need to build or maintain separate integrations to fetch evidence from IDnow.

Key details

With this enhancement, customers can:

• Access IDnow evidence directly from Docusign
• Simplify compliance workflows by centralizing evidence retrieval
• Reduce onboarding time and accelerate time to value

Rollout schedule

This capability is planned for release by the end of February.

Original source

Release Note Applicability

This publication applies to the Demo release for January 2026, version 25.4.01.00.

Important:
Feature availability timing may vary. Each month, Release Notes include items from different parts of the
Docusign
product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

eSignature Email Notification Update

A new design for our product communications

We are pleased to announce an upcoming update to our email communications. To enhance consistency and align with our updated brand identity, we have refined the design of these emails. This change will provide a more cohesive and professional experience for both Docusign customers sending envelopes and their recipients.

What's new?

Our eSignature notification emails are getting a modern refresh with a focus on clarity and consistency. This includes an updated color palette, a streamlined footer with quick links, improved layouts with new icons and refined designs, and consistent branding across all eSignature communications.

Some examples of our new email designs:

• Signature request
• Signature completion
• Account activation
• Account verification code
• Branded email

Below, you can see an example of how a branded email will appear, showcasing the application of customized colors and logo.

Who is impacted?

All eSignature users and recipients will see the new email designs. Except for customers who currently utilize customized email resource files. See important notes about resource files below.

For customers currently utilizing our basic branding features, we are pleased to confirm that your customized colors and logos will be seamlessly integrated and honored within the redesigned email templates, for both signing and sending brands. This ensures a consistent and familiar brand experience for your internal users and your recipients.

No action is required on your part. These modifications are purely cosmetic and will not impact the content or functionality of our emails. You and your signers will continue to receive the same essential information, presented in a refined and branded format.

Important note

For customers who currently utilize a brand with customized email resource files, it's important to note that the new email designs will not be automatically applied. Instead, the most recently uploaded customized version of these files will remain active and continue to be displayed, so account users and recipients won't notice any changes. This ensures that any existing custom content is preserved until a deliberate update is made. To benefit from the updated email designs, customers will need to update their brand by uploading the newest version of the email resource files, that will be available after the launch of the new designs, if desired.

Availability

The new design will be released in the Demo environment in December 2025 and in Production in January 2026. There will be a follow up notice when the change is deployed.

Region availability

This enhancement applies to all geographical regions.

Lucida Console support restored for sending & signing

We’ve re-enabled full support for the Lucida Console font family for document uploads and field formatting. Supported fonts are rendered as is, with no font substitution. Unsupported fonts are replaced with the default font.

Uploaded files using Lucida Console will now render in Lucida Console, with no font substitution. Lucida Console is again selectable for fields in the product UI and API. Existing templates with fields using Lucida Console will render in Lucida Console.

Key details

• Default font: Arial remains the default font for fields in the product UI.
• No Override: If you have changed your field fonts to another supported font, your selection will remain unchanged.

Documentation

• Supported Fonts for Document Upload
• Supported Fonts for Docusign Fields
• createEnvelope | REST API | Docusign

Release timeline Component Demo Production Fields (API) Dec. 3, 2025 Dec. 22, 2025 Fields (UI) Dec. 9, 2025 Jan. 6, 2026 Document Upload (API + UI) Available now Available now Region availability

• This enhancement applies to all geographical regions.

Clickable Links in Signing Now Supported for Standard-Based Signature (SBS)

Description
Docusign now supports clickable mailto, http, and https links in documents for SBS-enabled direct accounts. Previously, clickable links were available only for direct accounts without SBS (Standard-Based Signature) enabled. Direct accounts are those who purchased their Docusign plan through a Sales representative.

With this release, the feature is extended to include SBS-enabled direct accounts as well. All new envelopes created from existing templates or newly uploaded documents in these accounts will automatically support clickable links—no additional configuration is required.

Note:
Envelopes sent from SBS-enabled direct accounts before this update will not be retroactively updated to include clickable links.

Default settings

This enhancement will be enabled by default for all direct accounts.

Release dates

• Demo: Available now.
• Production: 100% by February 5, 2025.

Limitations

Clickable links are not available for FedRAMP accounts.

Region availability

• This enhancement applies to all geographical regions.

Docusign Workspaces: Global release

Docusign Workspaces is now being released globally across all datacenters, including North America (NA), Australia (AU), Japan (JP), and Europe (EU). Workspaces is currently available in all NA datacenters. This release extends availability to all markets.

Key Details

• The release is global and covers all major data regions: NA, AU, JP, and EU.
• Existing and new Workspaces add-on for eSignature customers in supported regions will have access to Docusign Workspaces.
• IAM for CX and IAM for Sales customers with Enterprise plans will also have access to Docusign Workspaces.

Additional Information

For more details, see the support documentation:
Docusign Workspaces.

Availability

Production: Available on January 16, 2026.

Auto-Fill for Docusign Workspaces

We are introducing the Workspace Auto-Fill feature to streamline multi-envelope transactions in Docusign Workspaces. This enhancement eliminates repetitive data entry for participants, resulting in a faster and smoother signing experience for complex transactions.

Key Details:

• Participants only need to enter their information once when completing their first envelope in a workspace.
• The following fields are auto-filled for all subsequent envelopes in the same workspace:
  • Phone Number
  • Title
  • Company Name
  • Address
• Saved data is limited to the current workspace and does not persist to other transactions or workspaces.
• The feature is automatically enabled for all customers with Docusign Workspaces; there are no settings or controls to manage it.
• Auto-Fill is not available for envelopes originating outside of Workspaces.

Rollout Schedule:

• Demo: Mid-January 2026
• Production: Mid-February 2026

AI-assisted agreement type detection for Agreement Template Builder

AI-assisted agreement type detection for Agreement Template Builder

We are introducing AI-assisted field suggestions, an enhancement to the Agreement Template Builder, designed to take the manual work out of document tagging. This feature uses AI to identify and place fields within your document, ensuring they are accurate and ready for use in less time. By streamlining the placement of both sender and signer fields, you can build professional, consistent templates with ease.

Key details

• Smart Field Placement: AI automatically finds and places the sender and signer fields, specifically Signature and Date Signed, directly onto your document.
• Intelligent Recommendations: The system recognizes existing fields in your account and suggests where they should go. It can even recognize similar terms, such as “Effective Date” and “Start Date”, to keep your data consistent.
• Easy Review and Approval: You have full control over every suggestion. You can review each field placement and accept or remove them one by one or all at once.
• Simple Setup: To use these tools, an administrator must enable the feature in Docusign Admin under Sending Settings.

Availability

• Document types: This feature currently supports .DOCX files written in English.
• Regions: This feature is available for accounts in NA, CA, AU, EU, and JP1.
• Supported Plans: All plans that have Agreement Template Builder available (most plans, excluding personal and trial plans)

Release dates

• Demo: late January 2026
• Production: February 2026

Certificate of Completion is now Supported in the Mobile App

Certificate of Completion is now Supported in the Mobile App

Users can now view and download the Certificate of Completion (CoC) directly within the
Docusign
mobile app. This feature allows users to download the CoC as a standalone file or combined with other envelope documents. This allows users to manage their business efficiently from their mobile devices.

Release dates

This will be available in our mobile apps as follows:

• iOS: October
• Android: January

Region availability

• This enhancement applies to all geographical regions.

ID verification with DVS check for Australian customers

ID verification with DVS check for Australian customers

In early January, we will add the ability for customers in Australia to request a Document Verification Service (DVS) check on their users as part of the identity verification (IDV) process. A DVS check is a program by the Australian Government that verifies the information on an identity document against the original issuing agency.

Identify customers will be able to use this feature by selecting Docusign ID Verification with DVS when they add IDV as part of an eSignature envelope, or as part of a larger workflow in Docusign IAM.

Availability

• Customers whose accounts are located in the Australian datacenter
• ID Verification with DVS is available to customers who have purchased IDV Premier

Design improvements to the ID Verification and ID Verification with Liveness participant flows

Design improvements to the ID Verification and ID Verification with Liveness participant flows

In mid-January, we will update the identity selection screens for participants who are completing ID Verification or ID Verification with Liveness process as part of their agreement. Our aim here is to make it easier for participants to access their reusable or electronic IDs from the selection screen.

Participants will see an updated UI when selecting an identity verification method: their physical ID document, their CLEAR account, or another form of electronic ID.

Here are a few examples of the experience:

• ID Verification with Liveness example
• ID document verification example
• Another ID document verification example

Release Dates

This will be available in Demo and Production in mid-January 2026.

Envelope Identity Verification Report is updated to Application Identity Verification Report

Envelope Identity Verification Report is updated to Application Identity Verification Report

The Envelope Identity Verification Report has been renamed to Application Identity Verification Report to reflect a broader scope across Docusign applications.

• We've renamed the report to reflect that identity verification tracking happens across all Docusign applications, not just eSignature.
• The report includes a new Application column that shows which Docusign application, e.g., eSign or Maestro, initiated the identity verification for each event.
• A new Application Transaction ID column captures the unique transaction identifier (for example, Envelope ID for eSign, Workflow Instance ID for Maestro), enabling easier traceability of individual verification events.
• Enhanced filtering lets you view activity by application, streamlining analysis and enabling you to assess identity verification usage by product.

Availability

The report is available to all customers who have access to Identity Verification reports. No additional action is required.
This update is already live and rolled out to all Docusign customers using Identity Verification.

Disclaimer

In-product reports should not be used to track billing numbers. Always rely on the Billing Reports provided by Docusign Sales.

See the support article Application Identity Verification Report for more details.

Streamlined Design and Usability Updates for Envelope & Template Details

Streamlined Design and Usability Updates for Envelope & Template Details

This update is a continuation of the previous release as we continue our ramp to production through the month of January 2026.

What’s new and improved?

Based on user feedback, we delivered a major usability enhancement to the Envelope and Template Details pages. This update resolves issues identified after the August release and introduces our updated design system, resulting in a more consistent, efficient, and user-centric experience.

Key improvements

These enhancements include a more focused header with clearer primary actions, improved visibility and control over recipient details, as well as a new centralized Details tab that consolidates all envelope and template information in one place. Easier access to comments, restored ID visibility and copy functionality, and streamlined document preview access further reduce friction and improve workflow efficiency.
See the Docusign eSignature 25.4.00.00 Release Notes for full details.

Availability

These enhancements are targeted to be complete by the end of January. The current ramp timeline is as follows:

• Production
  • 5% of accounts on December 8, 2025
  • 15% of accounts on December 10, 2025
  • 25% of accounts on December 17, 2025
  • 35% of accounts on January 5, 2026
  • 50% of accounts on January 12, 2026
  • 70% of accounts on January 20, 2026
  • 90% of accounts on January 26, 2026
  • 100% of accounts on January 28, 2026

Increased Upload Limit in the Docusign Mobile App

Increased Upload Limit in the Docusign Mobile App

To support your larger documents, the maximum file size for individual uploads in the Docusign mobile app (iOS and Android) will increase from 25 MB to 50 MB per file, regardless of file type.

Key Details:

• Applies to all users of the Docusign mobile app for iOS and Android.
• This change does not affect uploads through the Docusign Web app or the API endpoint, which already support 50MB files (see API documentation).

Note:
Customers can already upload up to 50MB files using the Web app and the API endpoint, ChunkedUploads Rest API.

Release Dates:

• iOS: January 2026
• Android: January 2026

Consistent Branding for SMS Signing Opt-In

Consistent Branding for SMS Signing Opt-In

We’re enhancing your recipients’ signing experience Now, when a signer accesses the signing opt-in page through an SMS text message, your custom brand logo will be displayed in the top-left corner instead of the default Docusign logo. This ensures that your brand is visible and consistent throughout the entire signing process, including the opt-in step for SMS notifications.

Screenshot of an SMS opt-in modal with a custom logo placeholder.

Administrators can add a custom signing brand for senders to select when they send an envelope. For more information, see Add a Signing Brand for Recipients.

Availability

This update is available to all customers who use signing brands with logos on envelopes and send envelopes with the SMS delivery method.

• Demo rollout: Mid-January 2026
• Production rollout: Late January 2026

Reporting Data Feed API Migration to Azure Infrastructure

Reporting Data Feed API Migration to Azure Infrastructure

We are migrating the Reporting Data Feed API for Docusign eSignature enterprise customers to a new Azure infrastructure. This update may temporarily affect data processing times for some customers. The purpose of this notice is to provide an advance update to the affected accounts.

What is changing?

• The Reporting Data Feed API system is migrating to a new Azure infrastructure.
• During a "parallel run" period, the API will return data from both the legacy and new systems to ensure a zero-data-loss transition.

What will customers experience?

• High-frequency users (using createdAfter):
  • Will receive data from both systems during the parallel run.
  • May notice increased processing times.
• Ad hoc users (not using createdAfter):
  • Will receive data only from the new system.
  • If caching previous results, these users may experience increased processing time due to reprocessing.

Why are we making this change?

The change is necessary to migrate to the new Data Feeds system. This migration strategy ensures a seamless transition to the new system while guaranteeing zero data loss. The parallel run mitigates risks related to time zone differences and system-specific data generation timestamps.

Timeline

The phases of this migration are scheduled to complete as follows:

• Backfill Completion (new system): First week of January
• API Switchover: Second or third week of January
• Legacy System Shutdown: Mid-February

Original source

Release Note Applicability

This publication applies to the Demo release for November 2025, version 25.3.02.00.

Important: Feature availability timing may vary. Each month, Release Notes include items from different parts of the Docusign product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

Activity Logs for Maestro Workflows

We’re excited to introduce the new Maestro Activity Log, a feature that provides an audit trail to track and review all workflow activity.

The Activity Log provides full visibility into all actions taken across your workflows, enabling better governance, simplified troubleshooting, and clear accountability for all workflow-related tasks. Activity log are available at the account, workflow, or instance level and can be exported as a CSV. Customers use audit capabilities to check the status of a workflow or confirm that a workflow was executed as expected.

What’s New?

The new Activity Log tracks and displays activity for both workflow definitions and workflow instances, ensuring a complete audit trail for your Maestro operations.

• Administrators can see all Maestro activity, including actions on workflow definitions and details of all instances for every workflow on the account.
• Process Builders can view activity for their workflows, covering both actions on workflow definitions and all instances for these workflows.
• Preparers can view the activity log for the specific workflow instances they initiate.
• Users can download the activity log contents to a CSV file for further processing and analysis.

This example of an activity log for a workflow shows changes to the workflow definition and activity from workflow instances.

Availability

This feature is available now for all IAM accounts.

Region availability

• This enhancement applies to all geographical regions.

New Envelope Reminder Connect Event

We are making it easier for you to stay informed on the progress of your recipients envelope journey.

• envelope-reminder-sent - This event is sent when the Set Account Reminders feature sends out a reminder for a specific envelope. Available only in JSON SIM event model message format.

Note: This event will not include a traditional envelope summary and the payload supports only a maximum of 60 recipients.

Availability

This functionality is fully available in the Demo and Production Environments.

Region availability

• This enhancement applies to all geographical regions.

New Connect Events for Navigator

We’re making it easier for you to track and respond to agreement activity within Navigator by introducing new agreement events.
These events give you visibility into key agreement lifecycle moments, helping you reduce errors, streamline workflows, and lower downstream processing costs. When Navigator agreements are created, updated, or deleted, or when review processes reach completion, having timely structured event data ensures that your systems stay in sync and your teams can take action quickly.

• agreement-created - This event is sent when a new agreement is created in Navigator. Available only in JSON SIM event model message format.
• agreement-updated - This event is sent when a user manually modifies an agreement in Navigator. Available only in JSON SIM event model message format.
• agreement-deleted - This event is sent when an agreement is deleted in Navigator. Available only in JSON SIM event model message format.
• agreement-extractions-reviewed - This event is sent when extraction reviews count is reduced. Available only in JSON SIM event model message format.
• agreement-reviews-complete - This event is sent when the number of pending extraction reviews reaches 0. Available only in JSON SIM event model message format.

How Connect improves accuracy and reduces errors:
New Connect events signal when AI-extracted data has been reviewed and when all information has been validated, providing the clarity needed to confirm your agreement data is ready for downstream processes. These real-time notifications help prevent incomplete or inaccurate information from moving forward in your workflows, avoiding potential delays and errors.

How Connect reduces downstream processing costs:
With agreement lifecycle events delivered in real time, your teams can proactively update related records and automate follow-on actions. This reduces the manual work and expense typically associated with identifying changes or confirming the status of agreements.

Availability

This functionality is fully available in the Demo/ and Production Environments by the end of November.

Region availability

• This enhancement applies to all geographical regions.

New Control to Pause Connect Configurations

We’re excited to announce a new capability: the ability to pause a Connect Configuration. This feature gives you more control over event processing, making it easier to perform updates, maintenance, or troubleshooting without triggering additional activity.
You can pause an active configuration in several ways:

• Select the Pause option from the Actions menu under each active configuration.
• Check the Pause configuration box on the Edit Configuration page.
• Set pausePublish: true in a POST or PUT Connect Configuration API call.

When you pause the Connect queue, all event processing associated with that configuration will be temporarily halted. This allows you to make updates, perform maintenance, or investigate issues without triggering further event activity. Any existing retries scheduled during the pause window are skipped but not lost.

When a configuration is unpaused, processing automatically resumes at the next scheduled retry for the affected events.

You can monitor paused events directly in the Connect dashboard, where they’ll be clearly marked with a message such as: This event was skipped due to the configuration being paused.

Pausing does not affect configuration settings or reset retry schedules. Account-level and organization-level configurations can be paused (envelope-level configurations are managed separately). Events that reach the end of their 15-day retry window while paused will expire and must be manually republished once the queue is active again.

Availability

This functionality is fully available in the Demo and Production Environments.

For more details on how the pause functionality works, please refer to our documentation.

Region availability

• This enhancement applies to all geographical regions.

OAuth per Connect Configuration

Account administrators can now configure OAuth credentials on a per-configuration basis.
Previously, the OAuth Connect solution only allowed a single set of credentials per account. With this new functionality, each Connect configuration can be assigned its own credentials, giving administrators more flexibility, security, and control across different integrations.
There are two ways to set OAuth credentials for a configuration:

• In the UI: Select Include Configuration Level OAuth within the configuration setup or edit page. Once this checkbox is selected, the OAuth settings fields will appear for you to enter the credentials.
• Via API: Set enableOAuthPerConfiguration: true and include the OAuth credentials in a POST or PUT Connect Configuration API call. Syntax is below:
  Note: If configuration-level OAuth is enabled, account-level OAuth and Basic Auth are not supported.

Availability

This functionality is fully available in the Demo and Production Environments.

For more details on how this functionality works, refer to our documentation.

Region availability

• This enhancement applies to all geographical regions.

Streamlined Phone Authentication Selection

To help you leverage our most up-to-date and user-friendly Phone Authentication solution, we are making it even easier to discover and use.
When preparing an envelope, if you select the Phone Call or SMS options, a helpful message will now appear. This message will highlight the benefits of our modern Phone Authentication method and provide a direct link to switch to it instantly.

Our modern Phone Authentication offers several key advantages, including:

• A better recipient experience: Your recipients will enjoy a more modern and flexible process. They can now choose between a Phone Call or an SMS text message to receive their one-time passcode.
• A simplified admin experience: You can now more easily configure specific authentication workflows for your agreements.

This update is part of our ongoing commitment to improving your workflow and ensuring that you have access to the most advanced options available.

Availability

This enhancement will be automatically available in both Demo and Production environments on November 19. This applies to all accounts that have Phone Call, SMS, and Phone Authentication methods available.

Region availability

• This enhancement applies to all geographical regions.

Collapsible Side Panel

The left-side navigation panel of the Agreements and Templates pages in the web application will become collapsible to free up space in the list views. This will reduce truncation of content and overall clutter. The default experience is unchanged with the side panel expanded, and users can choose to keep the side panel expanded.

What’s new?
Additionally, the side navigation is receiving the following updates:

• Remove the accordion panel caret icons from primary section headers.
• The All Agreements list view now includes Quick Views as a filter option.
• A new Find a Folder dialog in the Folders menu.

Availability

This feature rollout to the Demo environment began in October and will continue ramping to the Production environments until completion in the month of November.

Region availability

• This enhancement applies to all geographical regions.

New Field Types Supported in the Docusign Mobile App

The Docusign mobile app now supports Dropdown, Attachment, and Line fields. These fields make it easier to send documents on-the-go without switching devices. Senders can add an Attachment, Dropdown, or Line field when creating envelopes, as well as send templates that use these fields.

Release dates
We've submitted the app to the Apple App Store and Google Play Store and are awaiting final approval. These new field types will be available in our mobile app as follows, pending approval:

• Dropdown
  • iOS: October
  • Android: December
• Attachment
  • iOS: October
  • Android: November
• Line
  • iOS: December
  • Android: November

Region availability

• This enhancement applies to all geographical regions.

Supplemental Documents Now Supported in Mobile App Sending

The Docusign mobile app now supports Supplemental Documents in sending, making it easier to send documents on-the-go without switching devices. Senders can add and edit Supplemental Documents when creating envelopes as well as editing and sending templates.
Supplemental documents are supporting materials, such as disclosures or informational documents, that recipients can view and acknowledge but do not need to sign.

Release dates
This will be available in our mobile apps as follows:

• iOS: December
• Android: November

Region availability

• This enhancement applies to all geographical regions.

Certificate of Completion is now Supported in the Mobile App

Users can now view and download the Certificate of Completion (CoC) directly within the Docusign mobile app. This feature allows users to download the CoC as a standalone file or combined with other envelope documents. This allows users to manage their business efficiently from their mobile devices.

Release dates
This will be available in our mobile apps as follows:

• iOS: October
• Android: January

Region availability

• This enhancement applies to all geographical regions.

Streamlined Design and Usability Updates for Envelope and Template Details

Based on your feedback and to ensure the best possible experience, we have finalized a significant update to the Envelope and Template Details pages.
These revisions address the usability concerns raised following an earlier August update. We've updated our design system and re-evaluated both pages to create a more consistent, streamlined, and user-friendly experience.

What’s New and Improved?
We've applied the following key updates to both the Envelope and Template Details pages:

• Consolidated Header Actions: We've cleaned up the page header. The main action is now a prominent button, with secondary actions grouped in a single new actions menu.
• Enhanced Recipient Visibility: In the Recipients tab, we've introduced a toggle to manage detail.
  • By default, you will now see expanded details like the recipient's signing time, private messages, and authentication codes.
  • You have the option to toggle this off for a simpler view.
  • Even when simplified, the recipient's email and phone number (delivery method) will always be visible.
• Centralized Information: A new Details tab now organizes all envelope and template-specific data in one dedicated location.
• Other Actions and Information:
  • A Comments has been added to the header, near the primary action.
  • The Envelope/Template ID and its copy function have been restored to the header.
  • View documents: Clicking the document thumbnail (which now displays only the first page) will take you directly to the Signing Preview.

Availability

We plan to begin updating the Demo environment starting in early November.
The release to Production environments starting shortly after.
Note: Due to the upcoming holidays, the full rollout may extend into the beginning of next year. We will share a more detailed rollout schedule as soon as it is finalized.

Region availability

• This enhancement applies to all geographical regions.

Reorganized Envelope Lists

We are extending the optional trial period for the new, streamlined organization of the envelope lists on the Agreements page.

What’s Happening in November?
The new envelope organization will continue to be optional throughout November. You can still switch between the new and old experiences using the toggle on the Agreements page.

A Reminder of the Change
The new experience is designed to simplify your workflow by orienting your lists around the stages of an agreement. Instead of the older list structure, the new default views are:
New View | What it Shows
All Agreements | The default view, showing all envelopes with powerful filters (Sent by/to me, Action Required, and so on)
Drafts | Agreements you have started but not yet sent.
In Progress | Agreements that have been sent and are actively waiting for signatures or actions.
Completed | Agreements that have been fully executed.

We encourage you to try out the new organization this month to get familiar with it before it becomes the permanent experience.

Region availability

• This enhancement applies to all geographical regions.

New Name and Location: Docusign EU QES Moved to Signature Type Dropdown

We've updated the user interface for selecting the EU Qualified Electronic Signature (QES) option when preparing an envelope.

What’s new
We've updated the user experience for selecting a QES signature, making the process more intuitive and consistent.

• Setting Name Change: The setting name has been updated from Docusign ID Verification for EU Qualified to the clearer Docusign EU QES.
• Streamlined Selection: The setting has been moved from the Identity Verification dropdown to the Select a Signature Type dropdown when preparing an envelope.

These changes streamline the envelope preparation process by grouping signature-related settings together. This makes it faster and easier for senders to select the appropriate Qualified Electronic Signature type.

Who is impacted?
This change impacts Digital customers with QES-enabled accounts. Digital customers refers to customers who established their accounts by signing up on our website.

Note: These changes do not impact Direct customers that use sales-assisted channels. These customers may continue to use the existing user interface.

Availability

• Demo environment: Available now
• Production environments: Week of October 21

Important Notes

• Sales-Assisted Accounts: Direct customers (those whose accounts were facilitated by our Sales team) will not see this change at this time. We are working to provide a unified experience for all account types in a future release.
• Supporting Documentation: For more details on using Docusign EU QES, refer to the support article, Sending a Document Using a Qualified Electronic Signature.

Region availability

• This enhancement applies to all geographical regions.

Original source

Release Note Applicability

This publication applies to the Demo release for October 2025, version 25.3.01.00.
Important: Feature availability timing may vary. Each month, Release Notes include items from different parts of the Docusign product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

Collapsible Side Panel

The left-side navigation panel of the Agreements and Templates pages in the web application will become collapsible to free up space in the list views. This will reduce truncation of content and overall clutter. The default experience is unchanged with the side panel expanded, and users can choose to keep the side panel expanded.
What's new?
The collapsible panel will function as follows:

• Unlock the side panel by selecting the lock icon next to the New Navigation toggle.
• Expand and collapse the unlocked panel when you hover your cursor over the panel
  Additionally, the side navigation is receiving the following updates:
• Remove the accordion panel caret icons from primary section headers.
• The All Agreements list view now includes Quick Views as a filter option.
• A new Find a Folder dialog in the Folders menu.
  Release dates
  These changes will be live for all users of the web application in the Demo and Production environments in October.

IAL2 Verification for ID Verification Customers

Starting in late October, customers who need to verify their users' identity using the NIST SP 800-63A standard, will be able to do so through the ID Verification platform.
What's new?

• Users will be able to use either their CLEAR or ID.me accounts to quickly and securely verify their identity. Users who do not already have a CLEAR or ID.me accounts will be able to create one to complete the process.
  Who is impacted?
• IAL2 identity verification is available to customers on the ID Verification Premier SKU.

Envelope Access and Sharing for Agreement Desk

Customers that have signed up to the Docusign's beta or limited-availability experience of Agreement Desk will now have enhanced visibility into request and envelope access.
What's new?

• The Activity Feed in Agreement Desk now reflects when a request is shared with a user and user's access is removed from the request.
• The eSignature envelope history will provide a more comprehensive audit trail of sender and recipient activities associated with envelopes linked to Agreement Desk requests. Including:
  • New entry when an envelope is linked/added to a request in Agreement Desk.
  • New entry when a request user takes an action on the linked envelope.
    Release timing:
• Agreement Desk UI changes: September 29
• eSignature changes:
  • Demo environment: October 1
  • Production environments: October 7

ID Claims Enhancement to Work With Email Reminders

Using ID Claims, we’ve improved your recipients' experience with email reminders sent from a Maestro workflow.
What's new?

• When your recipient’s identity verification is valid and they receive an email reminder to sign an agreement, they don’t need to reverify their identity. This removes a significant source of unwelcome friction from their experience.
• With this enhancement, previous workarounds involving additional identity verification attempts or SMS re-authentication are no longer needed.

New Tag Types Supported in the Mobile App

The mobile app now supports Dropdown and Attachment fields, making it easier to send documents on-the-go without switching devices. Senders can add an Attachment or Dropdown tag when creating envelopes, as well as send templates that use these tags.
Release dates
These new tags will be available in our mobile apps as follows:

• iOS: October
• Android: November

UI Upload Limit Increasing from 25MB to 50MB

To better support your larger documents, we are increasing the maximum file size for individual uploads in the eSignature web app. The maximum file size per upload is increasing from 25MB to 50MB, regardless of file type. This upgrade only applies to uploads made in the web application. As shown in the Before and After columns in the following table, there is no change to the other limitations.
For more information, refer to the support article, File Size Limitations for an Envelope.
Note: Customers can already upload up to 50MB files using the API endpoint, ChunkedUploads Rest API.

Multi-Channel Delivery: WhatsApp and Email

Docusign now supports email as an additional delivery method with WhatsApp for envelope notifications.
What's new?

• This enhancement allows you to send an envelope to a single recipient using both WhatsApp and email delivery methods. This is similar to our existing SMS and email delivery options. WhatsApp and email delivery is supported through the Docusign web application and the eSignature API directly.
  Note: If you have Multi-Channel Delivery purchased and enabled, this WhatsApp and email feature will be enabled by default.

Web Application Consistent Messaging Fields: Subject an Message Update

To create a more unified sending experience across all delivery methods, we've updated the terminology for the recipient message fields in the envelope and template prepare flows.
What's new?

• Previously, the message fields for envelopes and templates used the terms Email Subject and Email Message. These field labels have been simplified to Subject and Message.
• This change aligns the terminology used in the prepare flow with other delivery method options (namely SMS and WhatsApp), making the experience more intuitive and consistent for all senders. The functionality remains the same.

Update the Display of Phone Authentication Failures for CC Recipients

We're updating the Agreements summary page to provide clarity to each recipient's verification status when they use the phone authentication process. This update removes guesswork by providing clear indicators for key Phone Authentication events.
What's new?

• Previously, when a recipient who was designated to Receive a Copy (CC) failed the phone authentication process, their status was incorrectly displayed as Completed on the envelope details page (even though the failure was logged). This inconsistency was confusing and did not accurate reflect the result of the authentication.
• Now, the envelope details page more accurately displays a Verification Failed status for CC recipients. This provides a consistent and intuitive experience, standardizing the behavior for all recipient types and giving senders accurate status information directly from within the summary page.
• This update will be automatically available by default to all relevant accounts by the end of October 2025.

AI-Assisted Signers Q&A Available to North America

The AI-assisted Signers Q&A feature is now expanding to agreements sent from all eligible sender accounts across North America. Previously available only for Real Estate plan accounts, this feature helps signers better understand what they’re signing by allowing them to ask natural language questions – and get useful, document-based answers.
What’s new

• The feature is currently available for Real Estate plans. We have now extended the support for agreements sent from all sender accounts in North America.
  Key details (unchanged)
• Sender controls respected
  • If a sender has disabled AI features during signing, Q&A will remain hidden.
  • If enabled, Q&A appears automatically – no extra setup required.
    Note: Agreement senders on digitally purchased plans do not have access to control this setting.
    Availability criteria
• Documents up to 15 pages and <23MB in size
• Not shown in embedded signing flows or FedRAMP/GovRAMP agreements
  This update will be fully rolled out in early October, bringing helpful, trustworthy AI assistance to signers across North America.

Reorganized Envelope Lists

The envelope lists in the Agreements tab of the web application will be reorganized so that they are simpler and oriented around stages of an agreement.
The views will be: All Agreements, Drafts, In Progress, and Completed. The All Agreements will be the default when a user lands in the Agreements tab with a filter for inbound vs. outbound envelopes (Sent by anyone, Sent by me, Sent to me) as well as a filter for the quick views (All, Action Required, Waiting for Others, Expiring Soon, Authentication Failed).
We completed the initial rollout of the optional experience beginning of September, allowing users to try the new navigation by enabling a toggle. In October, users will continue to have the choice to enable or disable the New navigation option.

eSignature Download Report Limit Updated From 50K to 5K

We're rolling out an update to make our reporting and CSV download features more consistent and predictable.
Previously, the number of rows you could see on-screen and the number you could download in a CSV file were different, which could lead to confusion and empty files.
What’s new?

• What You See Is What You Get: The limit for instant CSV downloads is now the same as what you see on your screen (5,000 rows). This ensures the file that you download perfectly matches the data you've filtered in the app.
• Effortless Large Exports: For reports with more than 5,000 rows, simply use our Scheduled Reports feature. It’s designed to handle large datasets (up to 500,000 rows) and deliver them right to your inbox.
  This change removes the guesswork and ensures a smoother, more reliable reporting workflow.

Web Forms Updates

Users logged in to Docusign who have access to Web Forms will be able to select, pre-fill and send forms directly to a recipient's email.
Rollout to Demo and Production environments will be completed by the end of October.

Security Questions and Security Answers (SQSA) Deprecation

Docusign is updating security measures to provide you with a more robust and user-friendly experience. This update includes removing security questions and answers (SQSA) from our system.
If you currently have SQSA set up, you will no longer have access to it starting January 12, 2026. This change simplifies your login and account recovery processes and increases your account security.
Why is this changing?
As we transition towards a more secure passwordless future, we are eliminating older security methods that are less effective and potentially vulnerable. This change aligns with industry best practices and our commitment to your account security.
When will this change happen?
The security questions and answers (SQSA) will be removed on January 12, 2026.
Additional security recommendations
To enhance your account security, we highly recommend that you use the following account security options:

• Two-Step Verification (TSV) Two-step verification adds an extra layer of protection to your account. Even if someone knows your password, they will still need a second verification method to gain access.
• Passkeys Passkeys are a more secure and convenient alternative to passwords for logging in. They are unique digital credentials tied to your device and cannot be easily phished or stolen.
  If you have questions or need assistance setting up TSV or passkeys, visit our Get Support page.

Original source

Docusign Apps Launcher for Salesforce package

These release notes include cumulative new features and fixes for the Docusign Apps Launcher for Salesforce package of apps. Docusign Apps Launcher for Salesforce is a managed package that includes the following applications:

• CLM for Salesforce
• CLM Essentials for Salesforce
• eSignature for Salesforce
• Gen for Salesforce
• Navigator for Salesforce
• Negotiate for Salesforce
• eSignature Apex Toolkit

NEW AND ENHANCED

This section covers the new features and enhancements delivered in the release. The ID numbers reference internal Docusign tracking information.

Docusign CLM for Salesforce

• FINT-1121 Support Caching of Community User Tokens for CLM Files Component: The product now saves one community user token in CLM Files (until the token expires). This one token is for all actions. The product no longer needs to generate a new community user token for each action.
• FINT-1122 Obtain LockStatus from CLM Files Component: The product can now retrieve the LockStatus property from the “Get Documents” response. This property surfaces the current status of all documents. The product no longer needs to retrieve each document status individually.
• FINT-1123 Remove GetLock Restrictions for the CLM Files Component: We have removed the GetLock API calls because the LockStatus is now returned in the “Get Documents” response (see FINT-1122). GetLock API calls are no longer required for documents in CLM Files.

FOR MORE INFORMATION OR ASSISTANCE

We love to hear from our customers. If you'd like to suggest product enhancements, visit our Ideas page. If you have questions or an issue with a product, visit our support center.

Original source

Release Note Applicability

This publication applies to the Demo and Production releases for August 2025, version 25.2.02.00. Feature availability timing may vary due to different release cycles within the Docusign product.

Merging Branches for Advanced Conditionality in Maestro Workflows

• You can now merge different branches from branching and multi-branching rules steps in your workflow to create common steps further down the workflow, eliminating duplication.
• Variables inside merged branches won't be available for merged steps that follow.
• Branching rules inside merged rules auto-merge.
• Unmerging specific branches is partially supported.
• Available for IAM professional plans and above.
• Demo: Aug 13, 2025; Production: Aug 28, 2025.

Add a Terminate Step to End a Maestro Workflow Branch

• Allows terminating different branches at different levels for True/False and Multi Branching rules, providing more control and flexibility.
• Features clear visualization of termination points.
• Demo: Aug 13, 2025; Production: Aug 28, 2025.

Maestro Step Selector UI Enhancement

• The step selector is improved from a dropdown to a spacious panel divided into categories and a Home page listing all steps.
• Includes a Suggested next step section recommending relevant next actions and a search bar for quick step location.
• Demo: Aug 13, 2025; Production: Aug 28, 2025.

AI-assisted Q&A Launch in the Signing Experience for Real Estate Plans

• Introduces AI-powered Ask a Question feature in signing experience, initially for Real Estate plans on North American servers, desktop only, single-document agreements up to 15 pages in English.
• Signers can ask questions and get answers with citations from the agreement.
• Feature rollout extends through Aug-Oct 2025.
• Not supported for embedded signing, notary/eWitness recipients, or certain regulated accounts.
• Customers can enable/disable AI features in Signing Settings.

Envelope and Templates Details Pages Moved to New Design System

• Visual refresh of envelope and template details pages with tabs to organize information, consolidated actions menu, recipient details toggle, and document thumbnails.
• Rollout delayed; Demo environment in July, Production in early August.

Signing Group Member Information Removed for Recipients on Different Account

• Names and emails of signing group members hidden on envelope details page if user is on a different account to protect internal information.
• Rollout delayed; Demo in July, Production in early August.

Reorganized Envelope Lists

• Envelope lists in Agreements tab reorganized around agreement stages: All Agreements (default), Drafts, In Progress, Completed, with filters for inbound/outbound and quick views like Action Required, Waiting for Others, Expiring Soon, Authentication Failed.
• New navigation optional in August, later default with toggle to old experience.

Agreement Preparation

• New Document Templates feature for DocuSign Agreement Preparation to streamline workflows with centrally managed standard agreements, reusable content, and placeholders.
• Key benefits include efficient agreement generation, dynamic content insertion, robust version management, seamless envelope integration, centralized consistency, and streamlined workflows.
• Agreement Fields allow reusable data fields across account.
• Enhanced document generation with easier access, Agreement Desk, and Maestro automation.
• Availability: IAM plans Demo Aug 5, 2025; Production Aug 26, 2025.
• Document Templates with Word Template Assistant available from Aug 30, 2025.
• For eSignature plans, updated template building process with agreement types and fields.
• Agreement Template Builder available Demo Jul 23, 2025; Production Aug 6, 2025.

Original source

Optimized Default View for Responsive Signing

To improve Responsive Signing, account administrators can use a new Optimize View for User’s Device setting that dynamically decides whether to open agreements on mobile devices in the mobile-friendly or desktop (PDF) view, based on the quality of the mobile-friendly experience. This ensures mobile recipients directly open their agreements in mobile-friendly view, only when the document structure supports it.

Account administrators now have three default view options for responsive signing on mobile devices:

• Optimize View for User’s Device - This is the new default setting for most accounts. When a document is predicted to render well in the mobile-friendly view, it will open with the mobile-friendly toggle set to ON. If not, it will open with the toggle set to OFF (PDF view).

• Open Only in Mobile-Friendly View - All documents will open with the mobile-friendly toggle set to ON, regardless of predicted quality.

  • Note: Accounts that previously had the Enable mobile-friendly as the default view setting enabled will not have any change in behavior. These accounts will be automatically updated to the Open Only in Mobile-Friendly View setting.

• Open Only in Desktop View - All documents will open with the mobile-friendly toggle set to OFF (PDF view), regardless of predicted quality.

To view these settings, open the Admin tab to access the account administration settings, and select Signing Settings. For product documentation, see Signing Settings.

The following screenshots compare the settings before and after these updates.

Original source

Release Note Applicability

This publication applies to the Demo release for September 2025, version 25.3.00.00. Feature availability timing may vary due to different release cycles in parts of the Docusign product.

Release Note Corrections

Changes since initial release include removal of Collapsible Side Panel entry, update to New Access Rules for Docusign eSignature Reports, and addition of Connect x.509 Annual Renewal entry.

IK Classification in Apps and Keys Page

Developers no longer need to perform 20 API transactions to promote Integration Keys (IK) to Production, even for non-eSignature APIs. The Admin IK page now includes a new option to select IK classification before going live. Release schedule: Demo Environment Aug 15-31, 2025; Production Environments Sept 11, 2025.

Optimized Default View for Responsive Signing

Responsive signing on mobile devices now automatically chooses the clearest mode: Mobile-friendly view or Desktop (PDF) view. Controlled by a new administrator setting 'Optimize View for User's Device'. Accounts previously defaulting to Mobile-friendly view will see no change.

New Access Rules for Docusign eSignature Reports

Access to scheduled and sent eSignature Reports is now restricted to authorized users only. Scheduled and sent reports can be accessed only by users with rights to the report, either the creator or designated recipient. Applies to all Docusign IAM and eSignature accounts. Release dates: Demo Aug 18, Production Aug 28.

Change to Validation on Empty Dropdown Fields in Envelope Templates

Users can now save envelope templates with empty dropdown fields starting September. Validation error for empty dropdown options is removed for saving templates but envelopes with empty dropdown selections will still be validated.

User Experience Updates for Template and Envelope Creation

Footer controls merged into a consolidated header for easier navigation. 'Next' button renamed to 'Next: Add Fields'. Toolbar on Add Fields page refreshed with Line tool and Smart Sections more visible. Demo rollout late September, Production mid-October.

Improved Clarity for Hidden Text Fields

Senders can mask sensitive info with 'Hide text with asterisks' property. An eye icon is added for authorized recipients to reveal masked field contents for their own view only. This enhancement rolls out automatically and cannot be disabled.

AI Agreement Summary Now Available on Mobile Web

AI-powered Agreement Summary expands to mobile web signers, showing key extracted info to help understanding. Sender controls respected; summary appears automatically if enabled. Applies to NA site accounts, single-document agreements under 100 pages and <23MB, not in embedded or FedRAMP/GovRAMP flows. Full rollout by end of September.

Signers Q&A Coming to Mobile Web

AI-powered Q&A feature expands to mobile web signers, allowing natural language questions about agreements. Sender controls respected; Q&A appears automatically if enabled. Applies to Real Estate plan accounts, documents up to 15 pages and <23MB, not in embedded or FedRAMP/GovRAMP flows. Full rollout by end of September.

Updated Home Page

Home page updated to support broader Docusign features. Profile photo and signature removed (still editable via Manage Profile). Header shows up to three recommended actions replaced as others clicked. Overview counters moved to right side, showing last 7 days counts instead of 6 months. New 'Tasks' section lists up to five recent tasks. Rollout in Demo and Production in September.

Reorganized Envelope Lists

Envelope lists in Agreements page reorganized around agreement stages: All Agreements (default), Drafts, In Progress, Completed. All Agreements view includes filters for inbound/outbound envelopes and quick views (All, Action Required, Waiting for Others, Expiring Soon, Authentication Failed). Rollout started in August as optional toggle, becoming default in September with toggle available temporarily.

Original source

Docusign Apps Launcher for Salesforce package of apps

• CLM for Salesforce
• CLM Essentials for Salesforce
• eSignature for Salesforce
• Gen for Salesforce
• Navigator for Salesforce
• Negotiate for Salesforce
• eSignature Apex Toolkit

NEW AND ENHANCED

This section covers the new features and enhancements delivered in the release. The ID numbers reference internal Docusign tracking information.

Docusign CLM for Salesforce

Note: The following enhancements improve document load times and prevent component failure when trying to display more than 50 documents:

• FINT-1121: Support Caching of Community User Tokens for CLM Files Component — The product now saves one community user token in CLM Files (until the token expires). This one token is for all actions. The product no longer needs to generate a new community user token for each action.
• FINT-1122: Obtain LockStatus from CLM Files Component — The product can now retrieve the LockStatus property from the “Get Documents” response. This property surfaces the current status of all documents. The product no longer needs to retrieve each document status individually.
• FINT-1123: Remove GetLock Restrictions for the CLM Files Component — We have removed the GetLock API calls because the LockStatus is now returned in the “Get Documents” response (see FINT-1122). GetLock API calls are no longer required for documents in CLM Files.

FOR MORE INFORMATION OR ASSISTANCE

We love to hear from our customers. If you'd like to suggest product enhancements, visit our Ideas page. If you have questions or an issue with a product, visit our support center.

Original source

Docusign Apps Launcher for Salesforce

These release notes include cumulative new features and fixes for the Docusign Apps Launcher for Salesforce package of apps. Docusign Apps Launcher for Salesforce is a managed package that includes the following applications: CLM for Salesforce, CLM Essentials for Salesforce, eSignature for Salesforce, Gen for Salesforce, Navigator for Salesforce, Negotiate for Salesforce, eSignature Apex Toolkit.

NEW AND ENHANCED

• Docusign Navigator for Salesforce

  • FINT-232 Users Can Access Docusign Navigator in Salesforce With the New Docusign Agreements Component. We added the ability for users to access Docusign Navigator in Salesforce. Docusign Navigator is a smart repository for your Docusign agreements. You can use Navigator to store, manage, and analyze all of your agreements. Important: This feature is still transitioning between limited availability and general availability. As we continue optimizing this functionality, you might experience issues when attempting to load Docusign agreements. Navigator is powered by Docusign Iris, an AI tool that identifies and stores key attributes of your agreements. Navigator makes it easy for users to find agreements, access vital information quickly, and gain valuable insights, all without leaving Salesforce. Administrators can configure Navigator to limit user access to agreements, ensuring that users can only access the agreements they need. To use Navigator in Salesforce, add the Docusign Agreements component to your layouts. The Docusign Agreements component displays your Docusign agreements and the controls to filter, search, and act on them:
    • You can use the Docusign Agreements component to perform the following actions in Salesforce:
      • Search: Use natural language, attributes, or keywords to find agreements in your connected Docusign account.
      • Filter: Use data points from your agreements like parties and expiration dates to narrow your search.
      • Customize Column View: Select the columns displayed for Navigator, like Parties, Agreement Type, Effective Date, and so on.
    • Note: Navigator only displays agreements sent from Salesforce. It does not display agreements sent from your Docusign web or CLM account. Existing customers must disconnect and reconnect Docusign and Salesforce to use this feature. Navigator displays a maximum of 100 Docusign envelope IDs per record, including parent and child objects. Not all Navigator functions are available in Salesforce yet.

• Docusign Gen for Salesforce

  • DFS-15250 Salesforce Flow Support for Gen and eSignature. We added the ability for administrators to use Salesforce flows to trigger Gen and Send. Gen and Send allows administrators to link Docusign Gen templates and envelope templates. When conditions trigger a Salesforce flow, Docusign generates an agreement from a record and sends it for signature. To add Gen to a flow, add a new action and choose Generate agreement with Docusign. Configure the step with a Gen template ID and a Salesforce record ID.
  • Important: Current API limitation is 100 generations per 10 minutes and cannot be increased. We recommend running scheduled flows no more than once every 10 minutes to avoid hitting rate limits.

FIXES

• Docusign CLM for Salesforce
  • FINT-912 Record User Data When Experience Cloud Users Upload Documents to the CLM Files Lightning Component. We fixed an issue with Experience Cloud users uploading documents. Previously, Docusign displayed the integration user's details instead of the uploading user's. Now, Docusign records the Experience Cloud user's details as the uploading user in the CLM Files Lightning component.

FOR MORE INFORMATION OR ASSISTANCE

We love to hear from our customers. If you'd like to suggest product enhancements, visit our Ideas page. If you have questions or an issue with a product, visit our support center.

Original source

Release Note Applicability

This publication applies to the Demo and Production releases for March 2025, version 25.1.00.00. All datacenters have been deployed for this Production release. Feature availability timing may vary due to different release cycles in product areas.

Removing Direct Signing Feature in Maestro Workflows for CFR Part 11 Accounts

• Direct signing option is removed for 21 CFR accounts to enhance compliance with 21 CFR Part 11 regulations.
• 21 CFR Part 11 customers will no longer see the 'Allow participants to go directly to signing' toggle in a Get Signatures step.
• This affects existing workflows which may need updates.
• Change rollout: week of February 17 in Demo, week of March 10 in Production.

Web Form Enhancements

• Continued rollout of multi-recipient forms completing in March.
• Each signer on the same envelope can fill fields via dedicated web form experience (requires Advanced Web Forms add-on).
• Support for SMS and phone authentication using new phone number field enabled for web forms linked to eSignature templates.
• Existing web form URLs will automatically redirect to new URLs with updated domain and base path starting March 3 in Demo and March 10 in Production.

Introducing Sounds While Sending and Signing Agreements in Docusign

• Sounds and animation introduced for sending and signing envelopes for all web customers who purchased a Docusign plan online.
• Users hear sounds and see animated confirmation on sending/signing.
• Users can turn off sounds independently for signing and sending from Settings in My Preferences.
• Rollout at end of March across web and mobile applications.

New Custom Folder Navigation

• Improved navigation experience for custom envelope and template folders.
• Instead of a list, users enter a modal showing more folders at once with search for easier navigation.
• Live for all web app users in Demo and Production in March.

Agreement Activity Log

• Agreement-level activity log available in Navigator for users with Can Manage access.
• Logs agreement-level events like uploads and access updates.
• Demo release target March 4; Production ramp-up March 17-24.

Navigator Moving to Completed View

• Navigator accessed by selecting 'Completed' instead of 'Navigator' option.
• Default view is Navigator with menu to switch to completed envelopes.
• 'Envelopes' section renamed to 'Agreements' containing documents and envelopes.
• Partial rollout early March, full rollout end of March.

Ability to Customize Columns for Envelope Templates

• Users can customize columns in envelope templates lists by showing/hiding and ordering columns.
• Live for all users by end of March.

Custom Data Verification

• Organizations can build custom extension apps to verify signer data against internal databases or any web service.
• Enables verifying against trusted internal sources, new verification use cases, enforcing data rules, improving signer experience with custom messages and autofill, reducing errors.
• Deployment steps include identifying use cases, creating extension app, evaluating API proxy need, defining data models, integrating app, publishing and testing.
• Rollout to Demo complete by end February 2025; Production available end March 2025.

Basic Data Verification in Standard Fields

• Basic Data Verification fields moved to Standard Fields section in envelope preparation.
• Includes phone and postal address verification (excludes email).
• Available for digital accounts only, not via eSignature REST API.
• Rollout to Demo continues until March; Production rollout from end February to April.

Maestro Workflow Templates

• Library of pre-built workflows tailored to industries and use cases for quick setup, customization, and publishing.
• Templates can be used as-is or customized.
• Initially available for US only; other languages and regions to follow later in 2025.

New In-Product Support Case Creation

• Users and admins can create support cases directly from Docusign accounts via Contact Support in Help menu.
• Users can describe issues and attach files; support team receives info for faster response.
• Available in Demo from March 11, 2025, and Production from March 14, 2025.
• Not available for free/trial plans or CLM accounts.

Original source

Release Note Applicability

This publication applies to the Demo and Production releases for April 2025, version 25.1.01.00. Important: Feature availability timing may vary. Each month, Release Notes include items from different parts of the Docusign product. Some of these areas have different release cycles, which means availability of the feature may vary. Items are available by the end of the month for which the notes are written, but may appear slightly before or after the release notes are published.

Introducing New Field Colors in eSignature

• Refreshed color scheme for fields used in the eSignature agreement creation and signing experiences, aligning with branding and usability improvements.
• No changes to field functionality.
• New colors displayed for sender and signer experiences.
• Update rolled out on the web app in April for all eSignature users; no user action required.
• Updates automatically appear in sending and signing interfaces.
• Mobile app users will receive the update in June.

Removing Support for position CSS property in HTML Uploads for Advanced Responsive Signing and Elastic Templates

• Position CSS property is no longer supported for customers uploading HTML for Advanced Responsive Signing and Elastic Templates.
• Uploads will fail if the HTML code contains the position CSS property.
• Customers using this property should update their HTML to prevent upload errors.

New Maestro Start Method: From Event Triggers

• Maestro workflows can be triggered based on events inside your Docusign account.
• Workflows start automatically when events and conditions are matched, without manual triggering.
• Start method allows specifying events related to eSignature envelopes, recipients, or other Maestro workflows.
• Conditions on events enable listening for specific scenarios (e.g., envelope completed using a specific template; recipient declined to sign; Maestro step failed).
• For more information, see Workflow Start Methods.
• Rolled out in Demo environment on February 21, 2025, and in Production on March 17, 2025.

Maestro Branching Rule Enhancements

• Add a branching rule between two steps in a workflow.
• Define which path each step should take after the branching rule.
• Delete a branching rule between two steps without disrupting the workflow.
• When removing a branching rule, choose the path for remaining steps to follow, ensuring a smooth transition.
• For more information about branching rules, see Configure a Branching Rule.

Export/Import Maestro Workflows Between Environments and Accounts

• Introduces Export and Import for workflows to copy workflows between accounts and environments.
• Enables deployment efficiency: transfer workflows from demo to production or between accounts within the same environment (or within the same account) without rebuilding.
• Read more about Export/Import workflows in the help topic.
• Fully rolled out in all regions and available on April 15.

Configure Visibility of Supplemental Documents for Envelope Recipients

• Senders can configure visibility of supplemental documents per recipient (currently, all recipients see all supplemental documents).
• Enhances control over document visibility during sending.
• Senders can continue using the existing document visibility feature.
• Available to all eSignature customers in April.

Support of the 'Geldwäschegesetz' (GwG) Obligations for German Customers

• Enhanced partnership with IDnow to deliver new electronic ID (eID) functionality.
• Supports GwG obligations for German customers.
• Benefits include fast, secure, automated service; eID usage of national identity card; familiar user experience.
• Trust Service Provider updated to IDnow Trust Service AB, replacing Docusign France.

Replace ERSD Browser Matrix Information for Default Customers

• Default Electronic Records and Signature Disclosure (ERSD) updated with the latest browser compatibility information.
• Operating systems, browsers, screen resolution, and security settings not listed will not be supported after rollout.
• Requirements will no longer be in table format; linked to a support page with the latest system/browser requirements.
• Unsupported hardware/software will show an error screen directing users to the support page for updates.
• Custom ERSDs are not impacted.

Web Forms Enhancements

• Web Forms updates rolling out throughout April.
• Data access sharing: allows web form creators to share submission data with other account users.
• Data is accessible from Download Results in Web Forms Builder and via Reports > Document Data > Web Forms.
• Additional data processing time: new form submission data may take up to 1 hour to appear in all reports.
• Changes to checkbox group values in CSV reports: selected checkbox group values will display under a single column (previously multiple columns).

ID Verification with Japanese IDs

• Japanese users can incorporate digital identity verification into contracting processes (e.g., MyNumber Card).
• Benefits include embedded secure remote contract signature, seamless digital identity verification, and detailed proof of verification for auditing.
• Enhances ease of signer identity in eKYC-compliant digital contracting.
• Enabled by default for new and existing Docusign ID Verification customers provisioned in the JP1 datacenter.

Joint Agreements - Exempt Members

• Exemption from authentication requirements for certain members/recipients of a partner’s sending account.
• Steps to enable:
  • Step 1: Network creator enables "Exclude members of the sending account from Authentication Requirements" in Joint Agreements Network Configuration.
  • Step 2: Network partners specify a login requirement for their sending account (Admin > Security Settings > Login Requirements; choose one of three options).
• Available in all Demo and Production environments.
• Note: A network partner's sending experience depends on the authentication requirements set by the network creator.

New Custom Folder Navigation

• Improved navigation for custom envelope folders and envelope template folders.
• Replaces side navigation list with a dialog box that shows more folders at once.
• Users can search to simplify navigation for many custom folders.
• Live for all web app users in Demo and Production environments in April.

Customize Columns for Envelope Templates

• All users can customize which columns are shown/hidden and their order for envelope templates lists.
• Live for all users by April 3, 2025.

Navigator Access Moved Under Completed Agreements

• Navigator access now occurs via the Completed view instead of Navigator.
• Default view is Navigator documents; can switch to the completed envelopes view with the view selector.
• Envelopes section in Agreements renamed to Agreements to reflect both documents and envelopes.
• Live for all Navigator customers by April 3.

Quick Action Module on Home for IAM Users

• Users who can create Maestro workflows will see blocks to start creating workflows, templates, and other actions next to the "Send for signatures" drop zone on the Home page.
• Rolling out in the Demo environment in late March and in Production in mid-April.

Introducing Agreement Summary for Signers

• Agreement Summary helps signers gather highlights before reviewing the full agreement.
• Rollout across April and May 2025.
• Availability conditions:
  • Signers located in North America.
  • Device with a larger screen (desktop or laptop).
  • Receiving envelopes with a single document of up to 15 pages (expands to up to 100 pages in May).
  • Documents in English only.
• Not supported at launch in certain scenarios:
  • Embedded signing.
  • Notary or eWitness involvement.
  • CFR-Part 11, FedRamp, or StateRamp accounts.

Original source