Collections

Overview

A Collection is a named grouping of knowledge sources within a project. Collections allow teams to partition knowledge—for example, separating public marketing FAQs from internal employee procedures or developer API specs.

What is a Knowledge Collection?

Instead of dumping all documents into one massive pool, collections create distinct vector namespaces:

• Public Help Collection: Contains website pages and public support FAQs.

• Developer Docs Collection: Contains API references and GitHub repositories.

• Internal Knowledge Collection: Contains internal pricing sheets and sales collateral.

Creating & Managing Collections

1. In the dashboard, go to Knowledge > Collections.

1. Click + New Collection and provide a title (e.g. Developer API Hub).

1. Select which sources belong to this collection.

1. Save collection settings.

Assigning Collections to Assistants

You can bind one or more collections to specific assistants:

• A sales assistant on /pricing can be assigned only the *Public Sales & Pricing Collection*.

• A technical onboarding assistant on /dashboard can be assigned the *Developer Docs Collection*.

Multi-Language & Tier Segmentation

Use collections to create language-specific knowledge stores (e.g., Docs - Spanish, Docs - Japanese) or tier-gated knowledge (e.g., Enterprise SLA Only).