Check the claims
Read the draft against the approved name, origin and price. Correct invented or outdated details before use.
Save the useful parts of a brand brief once, assign the Knowledge collection to a workspace or project, and check which guidance a writing or visual request actually uses.
Start creating in Chat ↗A brand brief can guide supported requests. It does not lock the appearance or truth of the output.
Put the coffee name, origin, price, voice and visual direction in a versioned Knowledge collection. Assign it to the workspace or project when related conversations should find it. A product record in Content remains a separate source with its own fields.
Before writing a launch introduction, inspect the resolved guidance and prompt. A separate image request can use visual guidance and an eligible exact source image. The request records which context was applied or only recorded.
The saved output still needs a human review.
Read the draft against the approved name, origin and price. Correct invented or outdated details before use.
Inspect the result for shape, label, logo and colors. Guidance can influence the request; it cannot guarantee fidelity.
Revise Knowledge for future work. Earlier requests keep their recorded context, so compare saved versions before choosing again.
For speech, exact spoken text is not rewritten by the brand default. For a single structured source, see Content context.
An illustrative example. Review current inputs, settings and the quote in your workspace.
Write a short introduction for this coffee blend using only the approved name and origin in the selected guidance. Use a clear, friendly voice; omit unsupported claims.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Use named content fields for recurring product facts and Knowledge for longer guidance. Keep supporting inspiration separate from the exact product image being edited. A Taste Profile can make selected qualities reusable; it should describe the direction rather than claim an automatic style lock.
Choose reference purposesRead every claim and inspect shape, label, logo and colors across the whole visual. Different models can respond differently to the same guidance. Keep exact accepted versions, develop native text and layout separately in Studio and prepare the final handoff only after reviewing each piece.
Save visual Taste ProfilesNo. 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.