Reference
The approval gates
What stops, what it protects, and why the first one matters most.
The gates are the mechanism that makes the whole thing safe. Nothing expensive happens without your approval, and nothing publishes without an explicit decision.
| Gate | What you are approving | Why it matters |
|---|---|---|
| Approve script | The written script | Cheapest possible place to change your mind |
| Approve audio | The synthesized voiceover | Rejecting re-synthesizes; it does not re-render video |
| Check credits | The cost of the render | The step that actually spends |
| Approve and publish | The finished piece, and where it goes | Last stop before it is public |
Approving moves the run on. Asking for changes reworks that stage only, so you never start over. Change the script at the script gate and you have spent almost nothing; change it after rendering and you have paid for a render you are throwing away.
A run waits at its gate indefinitely. If a production looks stuck, it is almost always waiting for you, marked blocked in the timeline.
// Signed in? The full screen-by-screen guide lives in the portal ↗