Several knowledge bases, and each chatbot only reads the ones you give it

Your widget's knowledge used to be one undivided pile: every published article was readable by every bot on every widget. Now you can keep as many separate knowledge bases as you like - product docs, pricing and policies, reseller-only material, a support playbook - and grant each bot the ones it may answer from. Pick one, pick several, or leave it unset to read everything. That means two widgets on the same site can run genuinely different bots: a public support bot that only knows the help centre, and a partner bot that also knows the reseller terms. A base can also be marked bot-only, so it feeds answers without ever appearing in the widget's browsable Help tab - useful for internal guidance you want the bot to follow but not publish. Website crawls and Notion syncs now target a base, so importing your docs site doesn't dump pages into the same bucket as everything else. Nothing changed for existing setups: your current articles were moved into a base called "General", and every existing bot keeps reading everything until you narrow it - a bot with no selection is never a bot with no knowledge. Deleting a base never deletes what's in it either; its articles return to Unfiled and stay answerable, the same rule already used by media and template folders. The Knowledge tab has a rail down the left to move between bases, and each article can be filed or moved from its editor.