2026-08-10 Proof Release Notes DEPLOY-1330

Audience: Everyone
Release Notes

Shipping Date: August 10, 2026

Enhancements

PDF Documents Can Now Be Stored in Your Connected eVault

If you have an eVault connected (eOriginal or SmartSafe), you can now choose to store PDF documents from your transactions in your vault — not just eNotes. Click the "Store in eVault" requirement for every document in the transaction you would like to store. There is no process change for eNotes.

Audience: Title and Lender Premium and Enterprise customersRoles: All usersGA

⚠️
Available by default if you have a vault connected. Please reach out to your Customer Success Manager if you are interested in connecting your vault. Applies to future transactions only.

SSO Exemption List Now Available for Command Center Organizations

Organizations with SSO enforcement can now maintain a targeted list of specific users who are exempt from the domain SSO policy, allowing those users to authenticate via password. The exemption list is managed directly in Command Center. MFA is required for any exempted user who signs in with a password.

Audience: Organizations using SSO in Command Center (Lite and Standard)Roles: Owners and Admins with SSO management accessGA

⚠️
Self-serve in Command Center; no Proof staff action required.

Account Recovery via the Proof API Now Generally Available

Account recovery, leveraging Proof's Identify product, is now generally available to initiate via the Proof API. In the Identify transaction create call, add idv_use_case: "ACCOUNT_RECOVERY" to set a special set of parameters for this workflow. See the API reference for details.

Audience: Business, Title, and Lender — API-integrated customersRoles: All usersGA

⚠️
Available by default. Please reach out to your CSM if you're interested in a UI-based Account Recovery transaction initiation workflow. Applies to account recovery transactions leveraging Identify.

Fixes

Agents Can Edit Document Annotations During a Verify + eSign Meeting

During a Verify + eSign meeting, agents can edit document annotations.

Audience: Organizations using Verify + eSign with agent-based sessionsRoles: Verify AgentsGA

⚠️
Applies to future Verify + eSign transactions only.

Verify Transaction Recipients Prompted for SSN/ITIN Only When Required by Transaction Configuration

Verify transaction recipients are asked for their SSN/ITIN during the pre-meeting flow only when the transaction configuration requires it, including transactions created through the API.

Audience: Organizations creating Verify transactions via the APIRoles: Signers and RecipientsGA

⚠️
Applies to future Verify transactions created via the API only.

Transaction Documents Remain Available to Agents When a Signer Completes Signing Ahead of the Meeting

When a signer completes signing ahead of the meeting, the transaction's documents remain available for the agent to complete their designations in-meeting.

Audience: Organizations using Verify + eSignRoles: Verify Agents and SendersGA

⚠️
Applies to future Verify + eSign transactions only.

Verify Agents Can Generate a Signature and Initials During a Verify + eSign Meeting

Verify agents, including non-notary agents, can generate a signature and initials to fulfill their designations during a Verify + eSign meeting.

Audience: Organizations using Verify + eSign with non-notary agentsRoles: Verify AgentsGA

⚠️
Applies to future Verify + eSign transactions only.

Agents Can Fulfill Their Assigned Document Tags During a Verify Meeting

Agents can fulfill their assigned document tags during a Verify meeting.

Audience: Organizations using Verify AgentRoles: Verify AgentsGA

⚠️
Applies to future Verify transactions only.

Updated

Was this article helpful?

0 out of 0 found this helpful