Summary: Enforced required fields are visually differentiated from required fields, single ID IAL2 verification available, new signer signature option, custom message per transaction type, and white-text tagging support for representative signing
DEPLOY-1200 shipping the week of October 13, 2025
Enhancements
Enforce required fields
When required fields are enforced, notaries need to be aware that the field cannot be deleted. In addition to existing guidance, we’re updating the field to reflect this change in behavior. Read more about required, enforced required, and optional fields in Required and optional document fields (NX-5403).
- Audience: All notaries
- User roles: Notary
- Availability: Clients who opt-in for enforce required fields
- Release stage: General availability
Allow signers to upload image of signature
A new option for signer uploaded signatures allows signers to upload an image as their signature. Set signature options for signers will be updated on release day with instructions for how to enable this (RX-1843).
- Audience: All customers
- User roles: All
- Availability: Setting is available but not checked by default
- Release stage: General availability
- Transaction types: Future transactions
Custom message for each transaction type — available 10/16
Customize your recipients' experience with a welcome message for each of your transaction type workflows (ETX-3284).
- Audience: All portals
- User roles: Owner and admins
- Availability: New settings available by default, no changes to existing settings
- Release stage: General availability
- Transaction types: n/a
Fixes
We now support the ability to add representative signing capacities via white-text-tagging (developer docs) (BIZ-8516).
- Audience: Premium
- User roles: All
- Availability: Opt-in
- Transaction types: Future transactions
Updated