Ingestion & Indexing
Check whether the documents that users uploaded are ready to be used in AI search. The search data created here is used for RAG, in which the AI finds related documents and answers from them.
Before you begin
- Required permission: Workspace administrator
- The AI runtime and model that run embedding must be ready.
- To use vector search, complete the connection and the embedding model settings in
Knowledge Storage.
Open Ingestion & Indexing
- Open the administrator page.
- Select
Knowledge Servicesin the left menu. - Select
Ingestion & Indexing.

Knowledge Indexing Overview
Check the current indexing status at a glance.
| Item | Description |
|---|---|
| Pending refresh | Newly created or modified files that are waiting to be reflected in AI search |
| Pending delete | Search data of deleted files that is waiting to be cleaned up |
| Pending vector deletion | The number of old vectors that are waiting to be removed from their original storage location after a file is deleted or the store is switched |
| Pending embed | Documents whose text has been read and that are waiting to be turned into AI search data |
| Vectors in database | The number of vectors actually stored for the current space in the selected vector DB. The local embedding rows value below the card is the number of per-model embedding rows kept in the local knowledge.db for the current document versions, so the two values can differ. |
| SQLite usage | The size of the knowledge indexing record DB. It does not include the size of the vector DB. |
| Indexing mode | The scope of files for which AI search data is created (for example, Full indexing) |
| Embedding provider | The AI embedding model in use (for example, Ollama bge-m3:latest / 1024d) |
| Active included roots | The paths that are indexed |
| Team checkpoint | The time the team folders were last checked |
| Client checkpoint | The time the personal folders were last checked |
| Last refreshed | The time the status was last updated |
You can leave Auto refresh on, or update the status manually with the Refresh button.
While the vector DB status is being checked, or when the check fails, Vectors in database shows -. If the server briefly returns a snapshot from an earlier point in time for the same space, the page keeps the more recent value that it last confirmed and shows a stale snapshot warning. When you switch between the team space and a personal space, the values of the previous space are cleared immediately, and unknown values are shown as - until the query for the new space finishes.
Before you start
Before you start indexing, check the required settings below. Select each button to go to the corresponding setting.
| Required setting | What to check | Go to |
|---|---|---|
| AI runtime | Select the AI runtime to use for indexing, such as Ollama or LM Studio, and check its connection status. | Configure the AI runtime |
| Vision model (VL) | Select the vision model that reads the content of PDFs and images from the AI models. | Configure the vision model |
| AI vector database | Select the vector storage from Local (SQLite), Milvus, Qdrant, and others, and set the connection information. | Configure the AI vector database |
| Embedding model | Select the model that converts documents into vectors for search. (for example, bge-m3) | Configure the embedding model |
Here you only choose the models to use. A vision model and an embedding model can be used for indexing only after you download them in AI model settings.
The AI vector database item checks not only whether the setting exists but also the actual connection status. If the vector DB cannot be reached, Connection error · check settings is shown in the warning color. If the dimension or the distance metric of the collection does not match, Collection mismatch · review needed is shown. If the collection has not been created in Milvus yet, Collection not found · create it first is shown. For a connection error or a collection mismatch, hover over the card to see the detailed error. No separate error detail is shown when a Milvus collection is missing, so select the card to go to the vector DB settings and create the collection by following Connect Milvus. A Qdrant collection that does not exist yet is not an error, so Ready · collection is created on first indexing is shown. For detailed actions, see the vector DB operations guide.
Collection & Processing Rules
Set when search data is created and which folders' documents are used for AI search.
Enable knowledge indexing
Turns the entire knowledge indexing feature on or off.
Indexing Mode Settings
| Item | Description | Default |
|---|---|---|
| Indexing mode | Selects the indexing scope and method | Full indexing |
| Wait time (minutes) | The time to wait from detecting a file change until indexing starts | 20 |
| Max concurrent workers | The number of indexing jobs that can be processed at the same time | 1 |
| Enable worker execution | When turned off, changed files are still detected, but AI search data is not created. | Enabled |
| Auto pause on high load | Pauses indexing when server usage is high and resumes it when the server is stable. | Enabled |
| Boost Mode | Starts indexing 5 seconds after a file change and moves queued jobs up to run now. It does not speed up processing, and it turns off automatically once the backlog is done. | Disabled |
| Allowed time windows | Sets the time windows in which indexing is allowed. If left empty, indexing runs at any time. (for example, 01:00-06:00) | No restriction |
Included roots
Specify the folder paths to index. If left empty, all paths are indexed.
Example:
/@team/docs
/@client/projects
AI Embedding Model Settings
Select the AI model that converts documents into search data.
| Provider | Description |
|---|---|
| Ollama | Uses an Ollama model installed locally. (for example, bge-m3:latest) |
| ONNX Local CPU | Uses an ONNX model that runs locally on the CPU. |
| ONNX Local GPU | Uses a local ONNX model with GPU acceleration. |
| Remote API | Uses an embedding model through an external API. |
A provider that has no installed model is shown as No models available.
| Item | Description |
|---|---|
| Vector dimensions | The size of the search data that the AI model uses. It is set automatically to match the selected model. (for example, 1024) |
| PDF/Image extraction strategy | Select how text is read from PDFs and images. VL first, OCR fallback means that the image understanding AI is used first, and character recognition is used if it fails. |
PDF/image include patterns
Enter the extensions or path rules of the PDF and image files from which text is read.
Example:
*.pdf, *.png, image/**/*
PDF/image exclude patterns
Enter the extensions or path rules of the PDF and image files that are not processed. If left empty, all files included above are processed.
Example:
thumbs.db, *.gif, cache/**
Progress by storage space
Check how much content in each team or personal storage space is waiting to be delivered to the AI.
You can search by space (team/client) and user, and sort by the number of pending refreshes.
| Item | Description |
|---|---|
| Space | Whether the space is the team space (team) or a personal space (client) |
| User | The user of the space, for a personal space |
| Pending refresh | Newly created or modified files that are waiting to be reflected in AI search |
| Pending delete | Search data of deleted files that is waiting to be cleaned up |
| Pending embed | Documents whose text has been read and that are waiting to be turned into AI search data |
| Embeddings | The total number of completed embeddings |
AI learning data overview
Check how much AI search data has been created for each model. This is not a feature that trains a new AI model with the source documents.
| Item | Description |
|---|---|
| Provider | The model provider used for embedding (for example, ollama) |
| Model | The name of the embedding model used (for example, bge-m3:latest) |
| Count | The total number of embeddings created with the model |
You can sort by count to compare the amount of search data for each model.