Skip to main content
Sharing is how you move work out of a private creation flow and into review, approval, or execution. Use it when someone needs to inspect an output, give feedback, approve a claim, or reuse an asset.

What to share

Finished creatives

Share final static ads, video ads, resized exports, and campaign-ready assets when the reviewer only needs the output.

Projects and chats

Share the project when the reviewer needs the reasoning, prompt history, context, variants, or iteration trail.

Asset collections

Share approved assets, reference examples, UGC clips, logos, and product shots when another person needs to build from the same source material.

Reports and research

Share competitor research, performance monitoring summaries, and scheduled-run outputs when the team needs the decision record.

Choose the right sharing level

Review workflow

1

Share the final candidate

Send the smallest thing that contains the decision: asset, project, research summary, or report.
2

Ask for specific feedback

Separate approval questions from strategy questions. For example: “Is this claim approved?” is different from “Do we like this angle?”
3

Apply edits in Superscale

Bring feedback back into the project so the final output and reasoning stay together.
4

Move approved assets into the right home

Store reusable assets in the Asset Drive, high-performing examples in brand context, and product-specific examples at product level.

Share modes

Review links are useful when the decision is about a specific asset. Project sharing is useful when the decision depends on why the agent made something.
Share only the material needed for the decision. Use project sharing when the reviewer needs context; use asset or review links when they only need the output.

Common questions

Export the asset when the recipient only needs the final creative. Share the project when they need to understand the brief, context, prompt, variants, or reasoning.
Share a curated review set: final candidates, short rationale, and the decision needed. Keep internal rejected drafts, experimental prompts, and unrelated client context out of client-facing shares.
Last modified on June 5, 2026