2026-10-13 Proof Release Notes DEPLOY-1348

Audience: Everyone
Release Notes

Shipping Date: October 13, 2026

Enhancements

Option to Match Last Instance of Anchor Text Now Available for Document Templates

Anchor text helps place document fields correctly when template matching or template selection doesn't land them in the right spot. Organizations can now enable an option to match the last instance of the target text on a page instead of the first. This option is controlled by an org flag and affects only new anchor text added after it is enabled; existing anchor tags are unaffected.

Audience: Business (including NST), Title, and LenderRoles: All users with access to document templatesGA

⚠️
Opt-in; contact your CSM or account team to enable the "Enable Last Document Anchor" org flag. Applies to future transactions only; existing anchor tags are unaffected.

OpenID Connect API external_user_id Now Mapped to the External ID Field on Transactions

The external_user_id value from OpenID Connect API workflows is now mapped to the external ID field on transactions.

Audience: All organizations using OpenID Connect API workflowsRoles: N/AGA

⚠️
Default for all OpenID Connect API integrations. Applies to future transactions only.

Transaction, Org Member, and Company Directory Exports Now Run as Background Jobs

Transaction, org member, and company directory exports now run as background jobs, allowing users to navigate away or refresh while the export processes. A notification appears when the export is ready to download, and in-progress exports can be cancelled at any time.

Audience: All portals with transaction export accessRoles: Owners and Admins with export accessGA


API Transactions Now Require a Cost Center ID for Command Center Organizations with Cost Centers Enabled

For Command Center organizations with cost centers enabled, API requests to create transactions now require a cost_center_id field. A new list endpoint is available to retrieve valid cost center IDs. Transactions submitted without a cost center ID return a validation error with guidance on locating the correct ID.

Audience: Command Center organizations with cost centers enabled, using the Proof APIRoles: API integrators and developersGA

⚠️
Enabled via feature flag by Product/Engineering. Applies to future transactions only.

Signer Name Field Is Now Read-Only in All Trusted Referee Meetings

The signer name field is now read-only in all Trusted Referee meetings. A signer whose name needs to be corrected resolves it outside the meeting — either by re-entering the flow where the name is editable, or by having the sending organization correct the recipient and reissue the transaction.

Audience: All portals and transaction types that route to a Trusted RefereeRoles: Trusted Referees and SignersGA

⚠️
Applies to all organizations by default. Applies to future transactions only.

Virginia Notaries Can Now Accept Meetings from Customers Using Proof Digital IDs

Notaries in Virginia can now accept meetings from customers using Proof Digital IDs. These customers will go through identity verification, including the use of a digital certificate that will be used to sign the PDF.

Audience: Virginia Notaries and SignersRoles: NotariesGA

⚠️
Available to all Digital ID-compliant signers and Virginia notaries by default. Applies to RON transactions that meet the criteria for Digital ID enrollment and reuse.

API Customers Can Now Control Whether the Proof Landing Page Is Shown or Skipped Per Transaction

Business customers using the API can now indicate on a per-transaction basis whether to show or skip the Proof landing page, sending users directly into the Proof signing or identity verification workflow.

Audience: Business and Real EstateRoles: AdminsGA

⚠️
Opt-in. Applies to future transactions only.

Updated

Was this article helpful?

0 out of 0 found this helpful