Several deliverables from one brief
Keep background in a project, review separate copy and visual requests, then package selected work. Plan campaign assets →
A FEW WAYS TO BEGIN
Give a product a setting, develop a visual direction, write a social series or bring an approved script to life. Start with a concrete brief and keep the pieces that work.
Start with a brief or an eligible source, explore a scene and inspect the details before choosing the product image you want to keep.
Explore ↗Bring references, select useful qualities and compare your directions. Take the chosen pieces into a supported native design or save them for the next request.
Explore ↗Give each post a purpose and collect selected versions.
Explore ↗A campaign needs a selected package, a social team needs a reviewed series, and a reviewer needs one exact version to comment on.
Keep background in a project, review separate copy and visual requests, then package selected work. Plan campaign assets →
Make an announcement, origin note and useful tip with individually reviewed visuals. Prepare social content →
Invite bounded review on an exact version, then branch privately from the useful feedback. Review creative work →
Choose what the work should communicate and where it will be used before selecting a model. Bring the sources relevant to that artifact and inspect the actual input contract. One shared campaign brief can require different operations, settings and review criteria for its copy, visuals and speech.
Product-image storyDevelop one inspected handoff from exact chosen revisions. Use native Studio text and image slots where supported and arrange eligible files with captions. Public boards illustrate a story rather than proving media generation; actual output verification belongs to the saved result. Scheduling and performance measurement remain separate.
Visual-direction storyNo. Catalog candidates, registered integrations and currently enabled workspace choices are different. Check support stage and the actual preparation controls.
Use the contextual links for the source, artifact or decision you have now. A feature explains a tool, a workflow explains its steps and an output guide explains the saved result.