Role-based folders

Everyone is answered from the folders they may see.

Split your knowledge base into folders and decide which role may see which folder. Panel chat enforces that boundary in code: content in a closed folder is never used in an answer for someone in that role.

Why it is needed

A company's internal knowledge is not one flat pile. HR files, contract templates and salary bands are not for everyone. Without folder scope a single internal assistant can read the most confidential document to the least privileged user.

How it is enforced

Scope is per role and works in the retrieval layer — before an answer is produced. The model never sees the contents of a closed folder; this is not a solution that relies on instructing it to keep quiet.

The customer widget is unaffected

A visitor has no role; the widget always answers from customer-facing folders only. Folder scope concerns panel chat and internal search.

Technical documentation for this →

Let your site say what it knows.

Give your URL and your assistant starts answering from your knowledge base.

Start free
7-day free trial · card required · cancel any time