Back to all guidesAproova features · 9 min read · Updated 26 July 2026

What Aproova does, from the first version to final approval

See how Aproova handles visual feedback, versions, review stages, client access, decisions, and integrations.

Written by the Aproova product team from the review flows we build and test in the application.

What Aproova does, from the first version to final approval

Upload is only the beginning of a review. Feedback, corrections, a new version, and a decision still need to follow.

Aproova keeps those steps in one review, so the team sees the full history while an occasional client sees only the material and action meant for them.

Comment on the actual work

Image comments stay with the marked area, PDF comments with the page, and video comments with the playback position. Replies, attachments, filters, and required changes remain in the same thread.

The person making the correction receives the request with its context instead of translating a vague message from chat.

Keep versions and campaign packages together

A correction becomes a new version of the existing review. Earlier comments remain available and two versions can be compared before approval.

In a package, each file keeps its own version and status. A story can return for changes while the post and PDF remain approved.

Control who reviews and who decides

Commenters and decision makers can have different permissions. Stages define who acts now and whether one or every required person must approve.

Internal versions and private comments stay restricted until the team releases work to the client. The final decision remains attached to the version that was reviewed.

Connect the review to the rest of the operation

Trello can keep the work item while Aproova keeps the proof. Webhooks send review events to n8n or another HTTP service for notifications and custom routines.

The integration carries the update. The asset, feedback, and approval history stay in Aproova.

A small campaign example

A team uploads a social post, a PDF, and a short video. Marketing comments on the headline, legal marks a required PDF change, and the client approves the video.

Only the affected files receive a new version. The package stays together and the final record shows which file was approved and which one returned for changes.

Questions people ask before setting up the workflow

Which files can Aproova review?

Images, PDFs, and videos can be reviewed in the browser. Source files can accompany the proof for download while a compatible preview is used for visual review.

Do clients need to join the workspace?

No. A controlled link can open only the review released to that client and show the actions allowed for their role.

Does Aproova replace Trello or n8n?

No. Aproova manages the content review and decision. Trello can manage the work item, and n8n can receive events for custom automation.