An artwork keeps every file you upload for it as a numbered version: v1, v2, v3. A reviewer asked for changes? Upload the corrected file as the next version of the same artwork, so its history, comments and decisions stay together.
Upload the next version#
- On the Approvals page, open the artwork's ⋯ menu and choose New version.
- Drop the corrected PDF on the dialog, or click to choose it (up to 200 MB). To use a PDF that is already in Files, choose Choose from Files instead (see Proofs and Files).
- Add Notes on what changed, for example "Barcode moved, text corrected". Notes are optional.
- Leave Email the new version to the previous reviewers ticked to have them asked again, or untick it to add the version quietly (see ).
- Choose Upload.
When the current version is approved or out for approval, the dialog says so first, for example "Version 1 is approved. Version 2 replaces it and needs its own approval.", so nobody replaces an approved file without noticing.
The version gets the artwork's next number and the row shows it straight away. Versions are never replaced: v1 stays as it was, with its links, comments and decisions.
When the corrected PDF went into Files first, the row says v6 available (the file's version number) and Send v6 for approval does the same in one step (see Proofs and Files).
What every upload prepares#
For each new version the app:
- keeps the PDF in Files, as the next version of the artwork's file (see Proofs and Files);
- keeps a fingerprint of the file (its SHA-256), which every decision records, so you can always tell which file was approved;
- reads the names of the spot colours in the PDF, and whether it uses overprint;
- makes the version's Simple and Advanced links (see Share links: Simple and Advanced);
- starts preflight (the badge on the dashboard) and the print preview of its separations;
- logs "v2 uploaded" (with its own number) in the history, with the file name and your notes.
The version's note shows in the proof header, next to the version number, so a reviewer can see why it was saved. The history line still names the version and the file.
Share the new version#
A link belongs to one version. After an upload, share the new version: its links are in Share on its row. The links you sent for older versions keep working, so reviewers who open them can still read the proof and its comments.
Email the previous reviewers#
The upload dialog has Email the new version to the previous reviewers, ticked to start with. It shows when the current version has reviewers.
- Ticked: the reviewers you invited to the previous version are emailed a few minutes after the upload. They become approvers of the new version and get their personal link to it in a New version email. A staged approval starts again at its first stage (see Staged approvals). Reviewers you email the new link to yourself in the meantime are not emailed twice.
- Unticked: nobody is emailed and nothing restarts. The new version waits on its row until you share it; choose In stages again for a staged approval.
Team administrators can switch the New version email off for the whole team under Settings → Emails (see Emails and branding). The box is then not offered, and you email each new link yourself, which makes the same reviewers approvers of the new version (see Reviewers: invitations and identity).
What a new version does to an approval#
A new version is a new round: nothing that was decided on the old version carries over, and the old version's decisions stay on record in the history. What happens next depends on where the old version stood.
| The previous version | What happens when you add a version |
|---|---|
| Was never sent to anyone | Nothing is emailed. Share the new version when you are ready. |
| Was sent to reviewers, still pending or rejected | Its links lock. A few minutes later the invited reviewers get the New version email with a personal link to the new version, and are its approvers. |
| Was approved | The same: the approval belongs to the old file. The new version needs its own approval, and the same reviewers are asked again. |
| Is in a staged approval, at any stage | The staged approval starts over on the new version at its first stage, with the same stages and approvers. Only the first stage is emailed. A stage that was just about to be invited for the old version is not invited any more. |
| Finished a staged approval (approved) | The same: every stage approves the new file again, first stage first. |
| Any of the above, and you email the new version yourself within those few minutes | The people you emailed are not emailed a second time. |
| Any of the above, with Email the new version to the previous reviewers unticked, or the New version email switched off | Nothing is emailed and nothing restarts. Share the new version yourself; choose In stages again for a staged approval. |
| The new version was added in Files, not in Approvals | Nothing changes yet: the old version can still be approved. Files asks whether to send the new version, and the row says v2 available (see Proofs and Files). |
| You send a version from Files (Send v2 for approval, in either app) | Its links lock as above, but only the reviewers you chose in that dialog are emailed, straight away. Nobody else is emailed later. |
The few minutes' wait is there so that a version you upload and share straight away sends one email, not two. Reviewers who only commented, or who opened a link without being invited, are never emailed.
In Files, each version of the artwork's file shows its own approval, so you can always tell which file was approved (see Proofs and Files).
See every version and its approval#
On the Approvals page, a row shows the artwork's latest version. Once there is more than one, the version number reads "v2 · 2 versions": choose it to open every version below the row, newest first. Choose it again to close them.
Each version shows:
- its status (Approved, Rejected, Pending, Not sent, or Replaced when a newer version was added before anyone approved it), who decided and when, or the stage a staged approval is at;
- when it was added and by whom, its file name, its notes, and the version of the file in Files it was made from;
- its approvers, each with their decision and the time. On a version that can no longer be approved, an approver who never decided reads No decision;
- how many comments were made on it.
To look at an earlier version exactly as its reviewers saw it, choose its Simple viewer, Advanced viewer or 3D proof button. The proof opens in a new tab on that version, with the comments and decisions made on that link. Comments belong to the link they were made on, so a version that was sent on two links has a button for each, with its number of comments. A version nobody was asked about has one button, for its newest link. A link you revoked, or one that expired, no longer opens and is not listed. PDF downloads the version's file.
The row's Open proof, Share, page details and stages always belong to the latest version.
Switching versions in the proof#
Every link shows all versions of its artwork, older and newer. When there is more than one, the header has previous and next (and the left and right arrow keys) as well as the version menu (in the ⋯ menu on a phone). The version the link asks about is marked for review, approved or changes requested. Compare wipes this version against the one before it. See Artwork inspection.
When a reviewer looks at another version, a strip under the header says so: comments and decisions apply to the version of the link. Comment, Approve and Reject only work on that version, and the 3D proof shows only that version. The button in the strip (Show v1, with the link's own number) goes back to it.
When you let them (see Share links: Simple and Advanced), reviewers can download the version they are looking at from ⋯ → Download this version (PDF). Your team downloads the latest version from the dashboard's Download PDF, from that menu, or any version through the API.
Superseded versions lock#
As soon as a newer version is uploaded, the older versions are superseded: their links can no longer be approved or rejected. A reviewer who opens one sees that a newer version was uploaded, and when, with a button to look at it, and is asked to get a link to the newest version from you. Their comments still work, and every decision made before stays in the history.
This keeps a late approval of an outdated file from reaching production. If a version was uploaded by mistake, there is no way to delete just that version: upload the right file again as the next version (or send the right version from Files). To permanently remove the whole approval and all of its versions, use Delete approval on the dashboard.
Pages and large files#
- A proof drawn from the PDF shows every page. A proof drawn from the separations (Advanced links, and Simple links of files that use overprint) shows the first 100 pages, and a longer file says so when it opens.
- The page a reviewer comments on is recorded with the comment, so comments stay on their page in multi-page files.