Veeva 26R2: the MLR review screen changed – and nobody clicked enable

Three weeks ago, the screen where pharma teams approve marketing content changed. Nobody at those companies clicked “enable.”

Veeva Vault 26R2 went to general release on July 31 and August 7. For PromoMats – the system where promotional material passes medical-legal-regulatory (MLR) review – the notable part is not one feature. It is how many changes arrive already switched on.

What shipped, exactly

• A rebuilt document viewer, auto-on in every Vault. Familiar toolbar actions (Bring Forward Annotations, Suggest Links, View Links) now live in the All Actions menu; Bookmarks, Destinations, Glossary, Thumbnails and Annotations moved to the Doc Info pane toolbar.
• eCTD redline annotations, enabled in all PromoMats Vaults – compliance packages now render redlines instead of the legacy blue links.
• The “Auto-Link on Initial Upload” admin checkbox is fully removed. Auto-linking now follows the lifecycle-state settings introduced in 26R1.
• Claim links change color with the claim’s lifecycle state – approved, withdrawn, or in between, visible at a glance.
• One rename on top: what the interface called “Veeva AI” is now “Vault AI.”

The Monday after the release weekend

Picture a global brand team: one PromoMats Vault, twelve markets, about 900 promotional assets through MLR review each quarter.

1. Reviewers open the new viewer – and familiar toolbar icons have moved into the All Actions menu.
2. The auto-linking behavior the admin once tuned with a checkbox now runs on state-based rules someone has to re-document.
3. The next eCTD compliance package renders redline annotations the regulator has never received from this company before.
4. None of this was on the team’s release calendar. It shipped on Veeva’s date, not theirs.

The architecture behind it

MLR review is the gate every channel depends on: approved emails, CLM decks for field teams, websites, congress materials. When the gate’s controls change on the vendor’s schedule, release notes stop being reading material and become change requests. Concretely: the removed auto-link checkbox is replaced by the Text Asset Auto-Linking Settings page from 26R1, where you define the lifecycle states in which auto-linking runs – if nobody migrated your settings, you need to verify current behavior now. Claim-link styling follows the Claim record’s lifecycle state (light blue approved, medium blue not-approved, gray withdrawn), with a green/red/orange circle indicator. And the release timing itself runs in POD waves – prerelease July 13, general release July 31 and August 7 – with session-timeout changes following separately in the week of September 23.

The teams that treat release notes as change requests – retrain reviewers, re-document auto-linking rules, re-generate a test eCTD package – keep channels moving. The Head of Commercial Content who does not will learn about 26R2 one support ticket at a time. In regulated pharma and medical organizations, that difference is measured in stalled campaigns.

The fine print

• Not everything is switched on. The AI pieces – chat, version-compare summaries, the new AI tab – need a signed agreement (a zero-dollar order form) plus admin enablement and agent activation.
• The AI tab is early adopters only in 26R2; agent improvements are planned bi-weekly between 26R2 and 26R3.
• Claim-variation suggestions (the magnifying-glass icon) appear only in Vaults using Claims Agent.
• The authoritative list of what turns itself on is not the release notes – it is Veeva’s Release Impact Assessment (RIA) spreadsheet. Check it before any internal comms.

Questions to settle before your next MLR cycle

1. Which lifecycle states does auto-linking run in now – and does that match the old checkbox behavior?
2. Has anyone re-generated a test eCTD package to see the redline output before a regulator does?
3. Who owns reviewer retraining for the new viewer – content ops or IT?
4. Is the AI order form signed, and if so, which agents are actually activated?
5. Does your validation and change-control process treat vendor auto-on changes as change requests?

The feature list is Veeva’s. The change management is yours.

Also from the 26R2 release: PromoMats content now flows into Vault CRM automatically.

Frequently asked questions

What changed in the PromoMats MLR review screen with Veeva 26R2?

A rebuilt document viewer, switched on automatically in every Vault. Familiar toolbar actions such as Bring Forward Annotations, Suggest Links and View Links now live in the All Actions menu, while Bookmarks, Destinations, Glossary, Thumbnails and Annotations moved to the Doc Info pane toolbar. General release ran on 31 July and 7 August 2026.

Which 26R2 changes arrive switched on, and which need enabling?

The viewer, the eCTD redline annotations and the claim-link colour coding arrive on. The AI pieces – chat, version-compare summaries and the new AI tab – need a signed zero-dollar order form plus admin enablement and agent activation. The authoritative list of what turns itself on is not the release notes but Veeva’s Release Impact Assessment spreadsheet.

What happened to the Auto-Link on Initial Upload setting?

The admin checkbox is fully removed. Auto-linking now follows the lifecycle-state settings introduced in 26R1, configured on the Text Asset Auto-Linking Settings page, where you define the states in which auto-linking runs. If nobody migrated those settings, current behaviour has to be verified rather than assumed.

Sources: Veeva Vault – What’s New in 26R2 · Veeva Vault – Latest Announcements (both fetched Aug 27, 2026). Veeva, Veeva Vault and PromoMats are trademarks of Veeva Systems Inc. This is an independent analysis; no partnership with or endorsement by Veeva. First published as part of my LinkedIn series, August 2026.