- Canvas
- Video
- Tips
Review a Short with a Small Team: Creator, Reviewer, and Release Owner
To review a Short with a small team in Popcraft Canvas, assign someone to edit, someone to review, and someone to decide which exact file is ready to publish. Keep the board private for invited reviewers and record the release decision against the final export.
This suggested workflow uses a hypothetical 30-second desk-tip video: move unnecessary objects aside, place a blank card in the cleared space, write one next task and begin.

Cover: AI-generated illustration, not a product screenshot or a completed video frame.
1. Separate the job from the access level
Popcraft describes owner, editor and viewer access for shared boards. These are application access levels; Creator, Reviewer and Release Owner are responsibilities your team assigns. See Popcraft's collaboration overview.
Creator: prepares the script, references, shots and edit, then responds to requested revisions.
Reviewer: checks the agreed version and supplies specific corrections. Confirm how they can access the intended material in your workspace.
Release Owner: checks that the requested fixes are resolved and chooses the final file for publication. Board ownership alone is not a recorded release decision.
One person may hold two responsibilities. Record the assignments before reviewing.
2. Invite privately and identify the review version
On a Canvas board, open Share → Share & invite. Enter the intended person's email in Invite by email and use Invite. For a private review, keep General access set to Restricted: only invited people can open the board. The separate Publish to Canvas action is not the invitation path. Check the access options in your workspace; do not assume that sharing a link grants the intended role.

Canvas General access set to Restricted: only invited people can open the board.
The panel states that invitees use their own credits when generating on the board. Agree who makes revisions, then identify the current review version.
For the desk-tip Short, the review package needs:
The approved narration and takeaway: “Write one next task and begin.”
A numbered shot list, using stable labels such as S01 through S10 if the five story beats have become ten shots.
The current preview or export, with its filename and version.
Two decisions: Is the action clear? Are there defects that prevent release?
Before changing an important Canvas node, use the available version controls to preserve useful work. The Canvas update guide explains Save version and Node history. Recorded history helps recover a creative state; it does not record a teammate's approval automatically.
3. Review the instruction before the styling
First, watch for meaning. Does the blank card appear before the narration asks the viewer to write? Is the final action legible? Does the video stay with one tip?
Next, inspect execution. Check desk continuity, changing object shapes, text accuracy, narration, music level and the ending on a phone. Separate a necessary fix from a preference so the Creator knows which decisions block release.
Use a compact feedback record:
Version: desk-tip-review-v02. Location: S09, approximately 00:24. Type: required fix. Observation: the card wording is too small to read on a phone. Requested change: increase the text size and keep the final card visible longer. Preserve: approved narration and desk colors. Status: awaiting revision.
This is an example request, not an observed defect. Avoid “make it better”: specify the location, the problem and the intended change. Keep the record in a shared document or your team's usual review channel if the workspace lacks the feedback controls you need.
4. Return a change response with the new version
The Creator answers each required fix with “changed,” “needs a decision,” or “not changed,” plus a short reason. Link the revised preview and use a new version identifier.
For the card example, the response might say: “Card text enlarged in S09; final hold extended; narration unchanged. Please recheck the card and the ending in v03.” Recheck adjacent shots too: a timing change can affect the voiceover or cut off the final line.
Approve script changes before generating more media. After replacing an individual shot, review it within the complete sequence.
5. Approve the exact export
The Release Owner opens the downloaded file, checks that required fixes are resolved, and records the decision against that file. A useful release record contains:
Project; export filename and link; version; reviewer; unresolved items; release decision; Release Owner; decision date; intended channel.
Leave the decision pending until someone explicitly approves it. A new material edit needs an updated file reference and another release check. Do not treat a saved board, restored node, invitation or successful export as automatic approval.
For projects involving event facts and sponsor assets, use the more detailed small-agency event sign-off guide.
Questions teams often ask
Does a reviewer need editor access?
For review alone, they need access to the intended material. If they will also edit, confirm the permission options actually shown in your workspace before assigning that work.
Can we approve a board instead of an export?
You can approve a creative direction on a board. Release approval should identify the actual file being published, because its timing, sound or content can differ from a preview.
Does restoring a version restore its approval?
No automatic approval behavior is assumed here. Recheck the restored content and record a human decision for the resulting export.
Open Popcraft Canvas and keep the review record with your project files.