Separate feedback from permission to publish
A comment can identify a problem. A revision can propose a new version. An approval records a decision about the work being reviewed. Treating those actions as interchangeable creates confusion, especially when a client and an internal team are looking at different versions.
MagnutAI’s campaign review flow includes share links, comments, proposed field revisions and approval states. Workspace managers can review proposed changes, while link permissions define what an external reviewer can do.
Choose the access the reviewer actually needs
| Review role | Purpose |
|---|---|
| Viewer | Read the shared campaign and contribute comments. |
| Editor | Propose revisions and request changes. |
| Approver | Make an approval or rejection decision within the review flow. |
| Workspace manager | Manage review settings and accept or reject proposed field changes. |
Review-link roles and workspace roles are different concepts. When creating a share link, inspect its access settings, intended audience and expiry. Use restricted access when the campaign should only be seen by named reviewers.
A clear path through a client revision
Imagine a client reviewing a product launch. They notice that the objective is too broad and one headline emphasizes the wrong benefit. Instead of sending a disconnected replacement document, they can propose the relevant changes in the review flow and explain the reason in a comment.
The manager reviews the proposed fields and accepts or rejects them. The team then checks the complete campaign again, including any creatives affected by the message change. A field-level correction can have consequences beyond that one field.
Keep version and approval states meaningful
The review workflow records campaign versions and activity. Approval saves an approved state and locks the plan until it is reopened through the appropriate manager workflow. This helps distinguish a decision from a draft that is still evolving.
Agree in advance on who is responsible for final approval and what changes require a new review. Do not interpret a missed deadline or a friendly comment as approval. When an approved offer changes, reopen the relevant work and verify the revised asset before scheduling.
Make feedback specific enough to act on
- Identify the exact message or visual detail that needs attention.
- Explain the audience or business reason for the change.
- Supply the corrected fact or approved wording where possible.
- State whether the issue blocks publication.
- Review the updated version rather than assuming a requested change was applied.