Name the effort
Add a short project description and instructions that belong with this work. Project access follows workspace and project permissions.
← All features
Give the work a place to grow.
A project connects the conversations, source material and outputs for one effort, so your next request starts with the right context.
Start creating in Chat ↗Keep one effort together
A project gives the food-night brief, conversations and saved work a shared place to return to.
Keep related requests close
Open conversations in the project, select relevant context and save their writing or visual outputs. Each generation still needs its own reviewed request.
Continue from a result
Use the project overview to find a conversation or asset, inspect its exact version and decide what to revise or hand off.
Organization is not automation
The project holds the work; it does not create or publish a campaign on its own.
To inspect and reuse a saved asset, continue to the Library. For repeatable, reviewed tasks with new inputs, see Generators.
See an example workflow
An illustrative example. Review current inputs, settings and the quote in your workspace.
- StartCreate or open the project for one campaign.
- Request or actionKeep its brief and related conversations together.
- ReviewCheck project scope and the versions chosen from each chat.
- Saved resultA reopenable workspace for the effort.
- ContinueContinue from the right conversation or exact output.
Related ways to continue
Use Knowledge in chat
Bring relevant guidance into a reviewed request.
Explore ↗Reuse an exact source
Bring a saved output or Library item back into the composer.
Explore ↗Collect a delivery set
Package selected versions for a clear handoff.
Explore ↗Creative chat
Create and continue conversations inside a project.
Explore ↗THE USEFUL DETAILS
Good to know.
Creation notes
Prepare your starting point
Describe the audience, intended deliverables and approved facts. Keep project scope understandable to people with permitted access. Open the relevant conversation and choose only the current sources and guidance needed for that brief. Existing workspace and project permissions remain the boundary for private material.
Inspect Library assetsReview what you keep
Return to the intended conversation and inspect the exact output version. Use Library for asset inspection, Studio for supported native development and content sets for a chosen handoff. A project can contain several directions while a specific request and delivery set use only selected material.
Reuse KnowledgeCommon 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.