| Topic | Details |
|---|---|
| Best for | Saving facts that should keep helping across future chats, campaigns, and image work. |
| Start here | Use this when the answer depends on business context, approved facts, or operational rules, not just visual style. |
| Outcome | Less repeated typing, fewer missing details, and stronger context retrieval in later tools. |

The Knowledge Base is where durable facts live once the style guide itself is already underway.
| Scope | Use it for |
|---|---|
| Chat + Image | Facts that should influence both writing and visuals. |
| Chat only | Business context that should shape answers or planning but not image direction. |
| Image only | Visual constraints or cues that should affect the look of output more than the wording. |

Knowledge Base Studio gives you multiple ways to add information, depending on whether the source lives in someone’s head, a note, a PDF, or a website.

Use the interview when the knowledge still lives in someone’s head and needs follow-up questions.
A launch has strict rules: free shipping ends Friday, bundles cannot be mixed, and one claim is legally approved while another is not.
Those details belong in the Knowledge Base because they should shape future answers and campaign work long after one chat ends.

Use the header actions to confirm where you are before you start adding durable business knowledge.

The roadmap helps you spot which kinds of knowledge are still missing from the brand system.