This article explains how to resolve an issue that may happen if a contact opens another user’s review link or different users share one device to review a proof.
Why did this happen?
When review links are opened by your reviewers and commenters, we save the contact’s information in a cookie on the browser. This improves your approver’s user experience as they do not need to identify themselves again on subsequent opens of proofs.
This occurs when a user has accessed a proof using a contact’s unique review link (included in a workflow). The contact’s credentials are then saved in the user’s cache/cookies. When another contact’s information is saved in the user’s browser’s cache/cookies, that contact’s information will be applied to the proof(s) the user opens.
What do I do now?
First, we recommend all users clear their cache and cookies to eliminate this issue entirely. Please note: If using Firefox, select “Offline Website Data” when clearing your cache and cookies. Second, to avoid this in the future, it is important that all internal users only access proofs via the “View Proof” button on a proof’s timeline and not through forwarded emails or review links.
Can a user be a Commenter or Approver on a proof?
If a user does want to see the proof from an Approver or Commenter’s perspective, we recommend they add themselves to a workflow or use a review link from the timeline in an incognito window.
How do I fix this?
You can remove the accidental contact by editing the workflow (via the proof timeline) and removing them from the Approver or Commenter line in the appropriate stage.
