Feature referenceKnowledge bases · 02 of 06

Knowledge bases

Document knowledge sources

Document sources extract text and structure from an uploaded PDF, Word, Markdown, or plain-text file and index that material privately for Stand-in retrieval. Stand accounts for the extracted indexed text rather than the original upload size.

Availability
Pro and Business
Configured in
Dashboard → AI Stand-ins → Knowledge bases → expand a knowledge base → Document sources → Upload document
Category
Knowledge bases
Reference status
Current
01

Supported document types

TypeIndexed material
PDFExtractable text and recoverable structure from supported PDF documents.
WordText and supported document structure from Word files.
MarkdownHeadings, lists, code, links, and text structure expressed in Markdown.
Plain textText content separated into searchable and retrievable sections.
02

Upload and ingestion lifecycle

  • Choose Add document in an owned knowledge base and select a supported file.
  • Stand creates an ingestion task and exposes its current status rather than treating upload completion as indexing completion.
  • Successful extraction is divided into indexed sections that can be inspected and searched from the source details.
  • The source becomes useful to a Stand-in only after ingestion succeeds, the knowledge base is attached, and the Stand-in changes are saved.
03

Content accounting

Pro and Business indexed-content allowances measure the extracted text that Stand stores for retrieval. The raw file’s byte size and internal retrieval representations are not presented as plan usage.

A file can therefore have a large original size but comparatively little indexed text, or fail to provide useful text despite uploading successfully. The source status and extracted-text inspection are the authoritative customer-visible result.

04

Replace or remove a document

  • Replacing a document creates new extraction and indexing work while the prior successful version remains active.
  • The successful replacement becomes current atomically; a failed replacement leaves the earlier content available.
  • Temporary replacement work is not intended to appear as permanently doubled plan usage.
  • Deleting the owned document removes its indexed material from future retrieval after the deletion lifecycle completes.
05

Availability and boundaries

  • Document sources are unavailable on Base.
  • Other organization members can see shared knowledge bases, but only the owning rep can upload, replace, or delete their sources.
  • Stand does not expose the uploaded file or extracted private source as a visitor-visible system message.
  • Downgrading preserves the resource in grace or read-only state rather than deleting it, but new ingestion and refresh pause while the organization is above the current entitlement.
06

Example

The screen below shows the feature in its normal Stand context. Labels and surrounding controls may vary with account state and plan.

Document knowledge sources in the Stand dashboard
Document knowledge sources in Stand. The image is illustrative; the reference text defines the supported behavior.