Learn how Wonderful's review and approval system works — leaving comments on assets, managing versions, tracking feedback, and signaling approval.
Wonderful keeps reviews fast by attaching feedback directly to assets, preserving full version history, and making approval status visible to everyone on the team. No more feedback buried in email threads or Slack messages.
Feedback in Wonderful is anchored to specific assets and versions. When someone leaves a comment, it's linked to the exact version of the file they're reviewing — so when revisions are made and a new version is uploaded, old comments don't disappear; they're attached to the version history.
The review cycle looks like this:
Comments support:
By default, comments are shown for the current version. Toggle the All Versions filter to see the complete comment history across every version of the asset.
This matters for revision rounds: you can see what was said in round one, confirm it was addressed in round two, and keep a clean record for the client.
When a creative is revised:
What stays the same: Asset name, all previous comments, all links from tasks or boards to this asset.
What changes: The preview updates to the new file.
Use the version selector in the asset detail view to jump between any version. You can:
Wonderful doesn't have a single "approve" button — instead, approval is expressed through a combination of signals:
| Signal | What it means |
|---|---|
| Asset marked Ready | This file is approved for use in ads |
| Comment threads resolved | All feedback has been addressed |
| Task moved to Final phase | Work on this task is done |
| Task moved to Approved phase | Formal sign-off from an approver |
Teams typically define their own approval convention in their workflow setup. Common patterns:
Most agencies run a two-stage approval process:
This separation keeps internal feedback private and presents only polished work to the client.
You can share a task or asset with external stakeholders (clients, legal, partners) without giving them a full Wonderful account.
External reviewers can:
External reviewers cannot:
Set privacy to Public View for stakeholders who only need to see the work, not comment on it. No sign-in required — anyone with the link can view.
For campaigns requiring multiple sign-offs (e.g., creative team, legal, client), use phases to manage the sequence:
Each phase transition can trigger a Slack notification or email to the next approver, keeping the process moving without manual follow-up.
→ See Automation to set up phase-based notifications.
Documents (briefs, copy docs) follow the same review process:
Not as a hard gate — Wonderful doesn't block phase transitions. Instead, teams use naming conventions (e.g., a "Needs Approval" phase) and Slack notifications to coordinate. Hard gate approvals are on the roadmap.
No. Every comment stays in the version history. When you upload a new version, existing comments are associated with the previous version. You can filter to see all comments across all versions or just the current version's comments.
Yes. Any team member can resolve comment threads. This is intentional — the creator resolving a thread signals "I've addressed this," not just the reviewer.
Assets can be archived but not permanently deleted in normal use. Archived assets retain their comment history.
When you share a task with a Public Review link, clients see all comments on the shared assets. If you want to keep internal discussion private, have internal conversations on a separate task version or use @mentions with internal team members.
Wonderful records when a shared asset or task is accessed via a public link. You can see view activity in the task's activity log.
Yes. You're notified by email when:
You can configure notification preferences in your account settings.