
Some of what you'd like the AI to know shouldn't be repeated to a customer: internal policy, the wording you use about a known issue, escalation thresholds. Tags and knowledge scopes let both be true. Your team's agents read it. Kai Support, talking to customers, doesn't.
Tags sit on the content itself. You can set them on:
Help articles, in the Tags field of the editor.
Snippets, in the Tags field when you create or edit one. In a CSV import, set the Internal column to true.
Websites, in the Tags field of the crawl. Every page from that crawl carries the tag.
Notion does this for you if you choose Respect Notion permissions when you import: private pages arrive as internal-only snippets.
internal, and only add more when you have a real second case. A careful tag system applied unevenly is worse than one tag applied every time.Each knowledge scope has three options:
All knowledge. Everything, including content tagged internal.
Only these tags. Nothing but the tags you name. Use it for a specialist that should stay in its lane, such as a billing agent limited to billing material.
All except these tags. Everything apart from what you name. The usual choice for anything customer-facing.
You set a scope in three places, from broad to narrow:
Kai Support → Settings → Answers & media → Content it answers from. The default for Kai Support and for every Let Kai Support answer workflow step that doesn't set its own.
The Let Kai Support answer step in a workflow, when one flow should see something different from the rest.
A custom agent's Knowledge search tool, so each agent has its own view.
The narrower setting wins where there is one. That's what lets an internal agent read everything while Kai Support, on the same content, stays restricted.

Out of the box, Kai Support's scope and a new Knowledge search tool are both set to All except these tags with internal. So tagging something internal is enough to keep it out of customer answers.
A tag only changes what the AI reads. A help article tagged internal is still visible to everyone in your help center. To limit who can read an article, use its Audience filter on the collection's article list, or protect the whole help center.
Tag one article internal.
Ask about it in your own messenger. Kai Support shouldn't use it in the answer.
Ask the same thing of an internal agent whose Knowledge search tool is set to All knowledge. It should.
Repeat the check after you add a new source. A crawl or an import brings in material nobody has reviewed, and it arrives untagged unless you tag the source.