Everything that happens to an artwork is kept in its history: uploads, links, emails, page views, comments, decisions and resets, with who did it and when. Entries can't be edited or removed. The one exception is a comment: when its author edits or deletes it, its entry changes with it.
The timeline#
Open it from the Approvals page with ⋯ → History on the artwork's row, or on the proof page from the History tab (also ⋯ → History and reviewers). The newest entry is on top, and it covers every version and every link of the artwork. Long histories scroll inside the dialog while its title and Close button stay visible. You can also focus the activity list and use the keyboard to scroll.
| In the timeline | API label | API kind | What it records |
|---|---|---|---|
| v2 uploaded | Version uploaded | uploaded | A version was uploaded or sent from Files: its number, file name and notes, and the version number of its file in Files. |
| Simple link created for v2 (or Advanced link, 3D proof link) | Share link created | link_created | A link was made: Simple, Advanced or 3D, and its reviewers. Every upload makes the version's Simple and Advanced links. |
| Simple link for v2 expires on 1 May 2027 (or never expires) | Share link expiry changed | link_expiry | A team member changed when a link stops opening: the new date, or never. |
| Simple link revoked for v2 | Share link revoked | link_revoked | A team member revoked a link: its address stopped working at once. |
| Simple link emailed for v2 | Link sent to reviewers | sent | A link was emailed: to whom, and the message. |
| Approved v2, or Rejected v2 | Decision | decision | A reviewer approved or rejected a page or the whole PDF: the comment, progress, status, and whether the address was verified by an invitation link. |
| Reset to pending (was approved) | Reset to pending | reset | A team member reset a link to pending: the reason, the status before and the decisions it cleared. |
| Comment on v2 | Comment | comment | A comment: the start of its text, and its page, the 3D proof, or general. |
| Viewed page 2 · v2 | Page viewed | viewed | A PDF page was displayed in Flat or Booklet view: page, version, time and known reviewer or anonymous visitor.Team-only activity; viewing does not mean approval. |
| Email sent: Approval request · v2 (or Email not delivered) | Email sent | An email went out, to a reviewer or to your team: which email, its subject, each recipient, and whether your own mail account or AutomatePrint sent it. A failed delivery shows the mail server's reason. Team-only. | |
| Stage 1 of 2 approved: Prepress check | Stage completed | stage | A stage of a staged approval passed: its number and name, how many stages there are, and the stage that started next. |
Each entry shows when it happened and who did it: the team member's name, or the reviewer's name or email. On the proof page, the reload button at the top of the list fetches entries made since you opened it.
The History tab also lists the link's Reviewers, with their role, their decision and when they made it, and the link's status. Team members find Reset to pending there (see Decisions, locking and reset).
The decision record#
Every approval and rejection keeps what you need to show later what was approved, by whom:
- the reviewer's email address and name, the decision, whether it covers the entire PDF or one numbered page, and their comment;
- whether the address was verified by the personal link of an invitation email;
- the fingerprint (SHA-256) of the exact file that was approved;
- the link it was made on (Simple or Advanced, and whether it offered 3D), the views that link offered and the views the reviewer actually opened;
- the confirmation text the reviewer ticked when approving;
- the reviewer's IP address and browser;
- the link's status after the decision.
The History dialog shows the decision, the comment, the status after it and a note when the address wasn't verified. The whole record, with the fingerprint, views, IP address and browser, is in the artwork's history in the API (see Approvals API).
What reviewers see#
Reviewers get a shorter timeline on the History tab:
- every version upload of the artwork, with its number and file name;
- the creation of their link, its decisions, resets and comments, and when it was emailed (without the addresses or the message);
- their own comments on other links of the artwork.
It leaves out your team's names, version notes, reset reasons, who was emailed and email messages. Other reviewers' addresses are masked. Signed-in team members see the whole timeline on the proof page too. Page-view activity is visible only to your team.
A connected customer portal can show this same reviewer timeline and masked reviewer list through the Approvals API endpoint. It never needs to expose the team's audit history to an approver.
Page-view activity#
Your team's timeline records Viewed page 2 · v2 when that PDF page finishes displaying in a visible browser window. Booklet spreads record both visible pages. The entry includes the time, Flat or Booklet view, and the reviewer's identity when known. Visitors without an identity are labelled Anonymous visitor; opening a shared link alone does not verify who they are.
Prefetched pages, pages still loading, failed previews and background tabs are not counted. Repeat views of the same page are grouped during a visit, with a further 30-minute duplicate guard for that viewer and proof link. This is display activity, not evidence that someone read the page or approved it. There are no emails for page views.
Choose Open page and feedback on a page-specific history entry to open that exact version and page. Comment entries also select the saved comment. Your team can follow these links from the artwork history or proof portal.
Emails in the timeline#
Every email a review sends is an entry of its own, Email sent, so you can see when a notification went out and to whom:
- which email it was (Approval request, New version, New comments, Reviewer approved…) and its subject;
- each recipient;
- who sent it: from your mail account, or sent by AutomatePrint. When your own mail account refused the email and AutomatePrint sent it instead, the entry gives the mail server's reason;
- Email not delivered with the reason when no mail server accepted it. Such an email is tried again later, and each attempt is its own entry.
An email you switched off leaves no entry. Email entries are for your team only; reviewers never see them. The emails themselves, and how to change them, are on Emails and branding.
Decision emails, comments and completion#
Your team receives an email when a reviewer approves, rejects or adds a comment:
- To: the team member who last emailed that proof link. For a link nobody emailed: the version's uploader, then the artwork creator, then the link creator, then team administrators. Nobody is emailed about their own comment.
- Subject: the reviewer, PDF version and action, naming the page when applicable, such as "Sam approved page 2 of Spring brochure v1".
- Progress: approved pages, pages with changes requested, remaining pages and total PDF pages for that proof link. A page is approved only when every approver on that link approves it; any rejection puts it in changes requested. Remaining pages are those with neither a complete approval nor a rejection. A rejected page can still await another approver, so the message separately says whether everyone has finished.
- Feedback: the saved comment, the link's status after a decision, and whether the reviewer's address was verified.
- Open proof and feedback: opens the exact PDF version and page, selecting the comment when there is one.
Counts describe the moment the action was saved. Each new action has its own update, so a delayed email cannot silently change to show a later review state. A note submitted together with a decision is included in that decision email, rather than generating a second comment email.
For a multi-page PDF, a separate Review complete email follows when every approver on that link has decided on every page, including whole-file decisions. It either confirms approval of the PDF or says changes requested; a completed review with rejected pages does not approve the PDF for production. Correcting the final rejection to approval produces a new approval completion email. A new version or reset starts a fresh review.
Reviewers are kept up to date as well: the invited reviewers of a link are emailed about new comments by anyone else, and about a new version of the artwork. See Emails and branding.
Updates are queued after the action is saved; delivery can take longer when email services are busy. Successful progress and completion deliveries are tracked separately so a retried completion email does not repeat the already-delivered progress update. Editing, moving or deleting an existing comment, resets and page views do not send these emails. Team administrators choose which emails are sent, and their wording, under Approvals → Settings.