Snapshots reduce ambiguity
Portal review is cleaner when the conversation is anchored to a known revision. Reviewers are responding to a fixed package, not a moving target.
Guide 2
Publishing snapshots for stakeholder review
A snapshot gives reviewers a stable revision to comment on, approve, or reject. That keeps feedback tied to something concrete instead of a constantly changing desktop state.
Approvals become easier to explain
Because each review event is tied to a specific published state, it becomes easier to explain what was approved, what changed later, and why.
Desktop can keep the full context
When review events sync back from the portal, the desktop record remains richer and more auditable than a separate browser-only approval thread.