Bring the useful facts into the request.
Keep event details, product facts or writing guidance in the workspace, then select the relevant source before drafting.
Start creating in Chat ↗Choose facts for this request
Use Knowledge for reusable guidance and Content for a specific structured record. Neither source automatically verifies the generated draft.
Reusable guidance
A project can keep a versioned Knowledge collection with approved voice or background facts. Review which guidance applies to the next writing request.
One content record
Select the exact event record when the draft needs its date, venue or other fields. The record is visible as context; it is not silently rewritten by the model.
Check the draft against the source
For a food-night announcement, compare names, dates and claims in the saved writing with the selected record or guidance.
If generation suggests a change to a content record, review that proposal before saving it. A saved writing output and an updated source record are different results.
For workspace or project-wide voice guidance, see Brand guidance. For record management, see Content collections.
See an example workflow
An illustrative example. Review current inputs, settings and the quote in your workspace.
- StartSelect an exact event record or Knowledge revision.
- Request or actionChoose Writing and ask for a draft from those facts.
- ReviewConfirm selected context and compare claims with source fields.
- Saved resultA saved document, separate from its source record.
- ContinueReview any proposed record update as its own action.
Example AskGL request
Draft a short event announcement using the selected record’s date, venue and time. Do not add facts missing from the record.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Related ways to continue
Good to know.
Creation notes
Prepare your starting point
Separate factual details such as names and dates from tone, audience and visual direction. Select current guidance that applies to the deliverable and inspect the request preview. Content records can hold repeatable named facts, while a Taste Profile holds reviewed visual qualities. Avoid unrelated background that obscures the request.
Use Knowledge in ChatReview what you keep
Read the generated writing against the selected guidance. Revise the output and update the factual source through their own supported flows. Earlier saved requests retain recorded context, so changing Knowledge should not be described as silently updating every past result. Keep accepted facts current for future preparation.
Structure content recordsCommon questions
Is every catalog capability enabled?
No. Catalog candidates, registered integrations and currently enabled workspace choices are different. Check support stage and the actual preparation controls.
How should I choose the next tool?
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.