Changelog + Docs: Import CSV rows into indexed collections with per-row metadata (OCS #4601)

docs/changelog.md

@@ -15,6 +15,7 @@ hide:
 * **NEW** [OAuth applications](api/getting_started_with_oauth.md#openid-connect-oidc) can now request a `teams` scope, shown on the consent screen as **List your teams**. Once granted, `/o/userinfo/` and the ID token include a `teams` claim listing the slug and name of every team the user belongs to, so a client that connects one team per token can show which teams are already connected and offer to connect the rest. The token is still scoped to a single team. Only global applications can request the scope, and it is not available to client-credentials tokens, which have no user.
 
 ## Oct 2, 2026
+* **NEW** An [indexed collection](concepts/collections/indexed.md#importing-csvtsv-rows) on a local index can take a `.csv` or `.tsv` through the new **Import CSV/TSV rows** entry under **Add Files**, indexing each row as its own searchable record. Regular file upload doesn't accept CSV or TSV files, so this is how to add them. Choosing a file shows a preview with the row count and the first five rows as they will be indexed, and you tick up to 16 columns to store as metadata on each row. The chunks page shows each row's number and metadata, and a chatbot's collection search returns them with each matching row. An import can hold up to 10,000 rows, each at most 2,000 tokens once rendered, and both limits are checked at preview. Remote (OpenAI) indexes don't offer row import. See [Import CSV/TSV Rows into a Collection](how-to/import_csv_tsv_rows.md).
 * **NEW** **Generate Chat Export** on a chatbot's **Sessions** tab now opens a dialog where you choose which columns go into the CSV. Every column is selected to begin with, and **Select all** and **Clear all** change them all at once. Message ID and Message Type are always included. The file keeps the export's usual column order whatever order you tick the columns in.
 * **NEW** The **Migration** card in the **Data** section of [Team Settings](concepts/team/index.md) now lets Team Admins choose what a [team migration](tech-hub/migrate_team.md) exports: the whole team, or selected chatbots. Selecting a chatbot includes all of its versions, and team members, tags, pricing rules and notifications are always exported for the whole team. When a selection is active, the migration banner says how many chatbots are being migrated, and migration mode stops triggers and scheduled messages only for those chatbots — the rest of the team keeps running. The card warns you when a change would leave a chatbot firing on both servers.
 * **CHANGE** `sync_team` now names the chatbots it migrated and states what it did not migrate, and a partial sync no longer requires the team's files bundle — it fetches any missing files from the source server as it goes. `sync_team --force-delete` still deletes the whole local team before re-importing, whether the sync is partial or not.

docs/concepts/collections/indexed.md

@@ -79,12 +79,31 @@ Local indexes are hosted and managed by OCS. When you create a local index, you
 - **Supported file types**: pdf, txt, csv, docx
 - **Supported embedding models**: You can see the list of embedding models for the LLM provider you have selected.
 
+`.csv` and `.tsv` files are not accepted through regular file upload. Add them through [Importing CSV/TSV rows](#importing-csvtsv-rows) instead.
+
 ### Chunking and Optimization
 
 When you upload a document to a local index, OCS breaks it into smaller parts called **chunks** and stores them in the index. The default chunking settings work well for most use cases.
 
 For advanced configuration — including chunk size, chunk overlap, and embedding model selection — see [Local Index Optimization](../../tech-hub/local-index-optimization.md).
 
+### Importing CSV/TSV rows
+
+You can import a `.csv` or `.tsv` file so each row becomes its own searchable record.
+Use **Add Files → Import CSV/TSV rows** on a local-index collection.
+This is the only way to add a CSV or TSV file to an indexed collection, because regular file upload doesn't accept them.
+
+Each row is indexed as one chunk.
+The chunk text is the file name followed by one `column: value` line for every column in the row.
+The columns you tick are also stored as metadata on the row's chunk.
+When a chatbot searches the collection, each matching row comes back with its row number and its metadata.
+
+!!! note "Local indexes only"
+    Row import works for local indexes only.
+    Remote (OpenAI) indexes don't offer the **Import CSV/TSV rows** option.
+
+See [Import CSV/TSV Rows into a Collection](../../how-to/import_csv_tsv_rows.md) for step-by-step instructions.
+
 ## Document Sources for Indexed Collections
 
 Instead of uploading files manually, you can connect OCS to an external document source — such as a Confluence space or GitHub repository — and have it fetch and index content automatically on a schedule. This keeps your OCS indexed collection (for both remote and local indexes) current without manual uploads.

docs/how-to/import_csv_tsv_rows.md

@@ -0,0 +1,80 @@
+---
+title: Import CSV/TSV Rows into a Collection
+---
+
+# Import CSV/TSV Rows into a Collection
+
+This guide shows you how to import a `.csv` or `.tsv` file into an indexed collection.
+Each row becomes its own searchable record.
+Regular file upload doesn't accept CSV or TSV files, so row import is how you add them.
+Use this when your chatbot needs to look up individual rows, such as matching a participant's input against a product list or reference table.
+
+For a conceptual overview, see [Importing CSV/TSV rows](../concepts/collections/indexed.md#importing-csvtsv-rows).
+
+## Prerequisites
+
+- An [indexed collection](../concepts/collections/indexed.md) using a **[Local Index](../concepts/collections/indexed.md#local-index)**. Remote (OpenAI) indexes don't offer row import.
+- A `.csv` or `.tsv` file, within the standard file upload size limit.
+
+## Import a file
+
+1. Open your indexed collection and click **Add Files**.
+2. Select **Import CSV/TSV rows**.
+3. Choose your `.csv` or `.tsv` file. A preview loads as soon as you choose it.
+4. Check the preview. It shows the number of rows found and the first five rows as they will be indexed. If a row is too long, the preview names it and **Import** is disabled.
+5. Under **Store as metadata**, tick the columns you want stored with each row. You can tick up to 16.
+6. Click **Import** to upload the file and start indexing.
+
+Each row is indexed as one chunk.
+The chunk text is the file name followed by one `column: value` line for every column, whether or not you ticked it.
+
+!!! note "Row numbers count from the first data row"
+    Row numbers in the preview, the chunks page, and search results count data rows starting at 1.
+    "Row 4" is the fifth line of the file once the header row is counted.
+    Blank rows are skipped but keep their place in the count, so the numbers can have gaps.
+
+## Viewing imported rows
+
+On the file's chunks page, each imported row appears as its own chunk, showing its row number and the metadata you chose to keep.
+
+When your chatbot searches the collection, each matching row comes back with its row number and the metadata you chose.
+The collection's **Index Inspector** page (the search icon) doesn't show the row number or metadata.
+
+## File requirements
+
+- Headers must be unique and non-blank.
+- Every row must have the same number of cells as the header row. A row with a different number of cells (a ragged row) is rejected, and its row number is reported.
+- The file must have at least one data row.
+- UTF-8 is tried first, with or without a byte-order mark. If the file isn't UTF-8, OCS tries to detect its encoding and rejects the file only if detection fails.
+- The delimiter for `.csv` files is detected automatically from comma, semicolon, tab and pipe. `.tsv` files must be tab-separated.
+
+## Limits
+
+- A single import can hold up to 10,000 rows.
+- Each row can be at most 2,000 tokens once rendered as `column: value` lines.
+
+Both limits are checked when you preview the file, so an oversized row is reported before indexing starts.
+Self-hosted operators who need different limits can override the application settings — see [Local Index Optimization](../tech-hub/local-index-optimization.md#csvtsv-row-import-limits).
+
+## Common issues
+
+### Some rows did not import
+
+If some rows in the file fail to embed, the rest of the sheet still indexes.
+The failed rows are listed on the file's status tooltip in the collection's file list. A long list is cut short.
+
+The file is still marked **completed** if at least one row indexed, so **Retry Failed Uploads** does not pick it up.
+To recover the missing rows, delete the file and import it again.
+
+If every row in a batch fails, the whole file fails and stays retryable, so **Retry Failed Uploads** picks it up as usual.
+
+### The file was rejected before importing
+
+Check the [file requirements](#file-requirements) above.
+Common causes are a ragged row, a duplicate or blank header, or an encoding OCS couldn't detect.
+For a ragged row, the error message reports its row number.
+
+## See also
+
+- [Indexed Collection for RAG](../concepts/collections/indexed.md) — how indexed collections and local indexes work
+- [Local Index Optimization](../tech-hub/local-index-optimization.md) — chunking configuration and row import limits

docs/tech-hub/local-index-optimization.md

@@ -40,3 +40,19 @@ In most cases the default chunking strategy works well. You can customise it per
 - **Structured data (tables, forms)**: Experiment with overlap settings — tables often lose meaning when split mid-row.
 
 !!! warning "Changing the chunking strategy after upload requires re-indexing your files."
+
+## CSV/TSV row import limits
+
+Importing a `.csv` or `.tsv` file as individual rows is an alternative to chunking.
+It's available for local indexes only.
+See [Importing CSV/TSV rows](../concepts/collections/indexed.md#importing-csvtsv-rows) for the concept, and [Import CSV/TSV Rows into a Collection](../how-to/import_csv_tsv_rows.md) for the steps.
+
+Three limits apply to a row import:
+
+| Limit | Default | What it controls |
+|---|---|---|
+| `COLLECTION_ROW_IMPORT_MAX_ROWS` | 10,000 | Maximum number of rows a single import can hold |
+| `COLLECTION_ROW_IMPORT_MAX_ROW_TOKENS` | 2,000 | Maximum tokens allowed per rendered row before it's rejected |
+| `COLLECTION_FILE_MAX_METADATA_COLUMNS` | 16 | Maximum number of columns that can be kept as metadata per row |
+
+These are constants in the application settings, not environment variables, so self-hosted operators who need different limits must override the settings values in their deployment.

mkdocs.yml

@@ -105,6 +105,7 @@ nav:
       - Add a Custom LLM Model: how-to/add_custom_llm_model.md
       - how-to/workflow_cookbook.md
       - how-to/add_a_knowledge_base.md
+      - Import CSV/TSV Rows into a Collection: how-to/import_csv_tsv_rows.md
       - Router Nodes:
         - how-to/routers/index.md
         - Configure LLM Router: how-to/routers/llm_router.md