Skip to main content

Managing RAG Storage Spaces

A storage space (RagSpace) defines where documents are physically kept — it's the common building block used both by knowledge bases and by job document storage. The two uses are distinguished by their "purpose":

  • "RAG" purpose — knowledge base documents; an organization can have several spaces of this type.
  • "Documents" purpose — incoming/outgoing analysis documents; only one space of this type can be active at a time.

Space types​

  • Local — platform-managed disk (or managed MinIO, depending on infrastructure configuration).
  • S3 — bucket, region and credentials provided by your organization.
  • SharePoint — site URL, target folder, authentication via the Azure SSO app or dedicated credentials.

Management​

From Admin → RAG & Storage:

  • Create/edit a space — the name serves as a physical prefix/folder and cannot be changed after creation.
  • Secrets already saved (S3 secret key, SharePoint client secret) are never shown again; leaving the field blank when editing keeps the existing value.
  • A "Test configuration" button checks real access (S3 bucket reachable, SharePoint write permissions, or accessibility of the managed disk/bucket) before saving.
  • Deletion is refused if the space is used by a knowledge base, by jobs, or if it is the currently active "documents" space.

Each knowledge base references the space where its documents are stored, independently of the embedding model used to vectorize them (see Embedding Models).