​
Workspace

The top-level tenant. A workspace owns billing, members and roles, audit logs, usage metering, SSO connections, bot integrations, and helpdesk integrations. Workspace owners manage everything; members get access based on project permissions.

​
Project

A knowledge base — typically one product’s docs, a repo, or an internal wiki. Projects own sources, client keys, agents, actions, analytics, and per-project LLM settings (persona, tone, custom instructions, provider/model overrides).

​
Source

A connected content origin inside a project. Supported types include website, github, gitlab, notion, confluence, gdrive, sharepoint, shopify, tickets, files, slack, zendesk, jira, linear, salesforce, openapi, discourse, stackoverflow, and youtube. Each source can be re-synced on demand, on a schedule, or via webhook (git push). See Knowledge Sources.

​
Source Group

A named collection of sources within a project — use groups to model docs versions (v1, v2, latest), separate products, or internal-only content. Client keys can be restricted to specific groups (allowed_groups), and chat/search requests can pass group_ids to narrow retrieval further. See Source Groups & Sync.

​
Crawl / Sync

An ingestion run. A crawl fetches content from a source, normalizes it, and (re)indexes changed pages using content-hash change detection. Trigger manually, on a daily/weekly schedule, or by inbound webhook.

​
Document

A normalized markdown page with metadata (URL, title, headings, crawl timestamp). Documents have a visibility flag: public documents are retrievable by widget/SDK/bot traffic; restricted documents are only available to authenticated dashboard and internal-ask users.

​
Chunk

The retrieval unit: a heading-aware segment of a document stored with both a vector embedding (for semantic search) and a full-text index (for keyword search). Answers are built from the top-ranked chunks after Reciprocal Rank Fusion.

​
Conversation, Message, Citation, Feedback

Each chat exchange is persisted as a conversation of messages. Assistant messages carry citations — numbered [n] markers mapped to source documents — and can receive feedback ratings that feed the knowledge-gap analytics and retrieval boosting.

​
Client Keys

Per-project integration credentials: Public keys support origin allowlists and optional reCAPTCHA enforcement; secrets are hashed at rest and shown once. See Authentication.