Store durable knowledge
Use the Knowledge Base for facts and guidance that should remain useful across sessions, not temporary chat text.
Use a clear entry type
Separate definitions, policies, references, decisions, client preferences, and technical notes where possible.
Add sources and dates
Record where the information came from and when it was last confirmed.
Avoid private secrets
Do not store passwords, private keys, full payment credentials, or unnecessary personal data in a project knowledge entry.
Retire outdated entries
Update or archive information when the project changes so future context remains trustworthy.
NEED A GUIDED ANSWER?
Ask LobeWork about this guide.
The support assistant uses the same published guide library and will link you back to the most relevant article.
WAS THIS GUIDE HELPFUL?Help us improve the documentation.