This tab lists processed documents. Select a document to review its Content, Tags, Raw extraction, and Summary.
See Document processing.
Build queryable knowledge from your documents, then attach it to agents and apps.
Knowledge turns source documents into queryable content for agents. Qore creates a table of contents, tags, and embeddings that agents retrieve during conversations.
Select Knowledge in the Console sidebar. Create knowledge at the top of the page and manage project knowledge bases below it. Select All Datasets to manage source files. For every task in one place, see Create a knowledge base.

Build knowledge from a description
The Create New Knowledge prompt
A configured knowledge base
Group source files
All Datasets
A named dataset that tracks ingestion
Bring changed files into the knowledge
A knowledge base → Datasets → Sync
A new knowledge version that agents answer from
Inspect what was extracted
A knowledge base → Content
The table of contents, tags, raw extraction and summary per document
Use what you built
Try Knowledge, or attach it
Grounded answers, in the playground or in an agent
Two concepts work together:
A named grouping of source files. It tracks ingestion but does not interpret content.
See Datasets.
A knowledge base only changes when you sync it. Updating a file in a dataset does nothing to the knowledge base until that file is synced, and each file that syncs creates a new knowledge version. See Sync & versions.
Describe what the knowledge should hold. Qore sets up the knowledge base from your description.
Ready-to-use templates provide starting descriptions for common knowledge types. Select a template, then edit its description before you send it.
Choose a source while you create the knowledge:
Use + to attach files from your computer, a cloud drive, or a website. When you give several website URLs, Qore creates a dataset for each.
Use Datasets to select existing datasets. The selector includes Search datasets… and + Create Dataset.
You do not have to have a dataset first. Describing the knowledge and attaching files in one step is the normal path; datasets matter when you want to reuse the same source files across several knowledge bases, or when you are crawling a website.
You can also build knowledge from the Agent Builder chat. The agent that builds your agent follows the same process as the Knowledge Builder: it can create a knowledge base, add the files you attach to a dataset, sync it, and attach the result to the agent you're building. See Build knowledge from the Agent Builder chat.
MY KNOWLEDGE lists the project's knowledge bases. Each card shows its name, description, and last update time. Select a card to open it.
Search knowledge…
Filters by name and description. It does not search document contents. Query a knowledge base in Try Knowledge.
List and grid icons
Switch between row and card views.
▷
Opens Try Knowledge for that knowledge base.
⋮
Opens item actions, including delete.
Deleting a knowledge base cannot be undone here. It removes the generated structure — the table of contents, tags, and embeddings. The source files stay in their datasets, so you can build a new knowledge base from them, but the deleted one does not come back.
Knowledge created from a website crawl is named after its source.
All Datasets in the top right opens Datasets.
Share a knowledge base. Each knowledge base has its own URL. Anyone opening it needs access to the same project.
Open a knowledge base to refine its scope, manage source files, and inspect processing.
Select the knowledge base name to switch knowledge bases.
Use chat to add sources or change the knowledge scope. Each reply shows its credit usage.
This tab lists the datasets and files that the knowledge base uses. It shows each file's version and status. Sync files, upload new versions, and resolve items needing attention here.
See Sync & versions.
This tab lists processed documents. Select a document to review its Content, Tags, Raw extraction, and Summary.
See Document processing.
Select vN ▾ to view each knowledge version and what created it.
Select + Attach to add files from your computer, a cloud drive, or a website. See Add files.
Select ▷ Try Knowledge to query the knowledge base and inspect the chunks behind each answer. See Try Knowledge.
Detach is different from delete. Detach dataset and Detach from knowledge remove sources from this knowledge base. The source files remain in the dataset. Delete from dataset removes the file from the dataset.
Processing runs through ingestion, table-of-contents generation, tagging, and embeddings. Failures identify the stage that stopped.
Provider throttling commonly stops table-of-contents generation:
The provider rate limited the request. Failed stage: TOC_GENERATION
Failed files show Sync failed in Datasets and a warning in Content → Documents. Select the file to view its error and failed stage.
Select Retry to process the file again. Qore also retries automatically within two hours. Retries are limited. After all retries are exhausted, Retry is unavailable. Correct the source file, then provide a new version. Common issues include scanned PDFs without text and password-protected files.
Wait before retrying. An immediate retry usually meets the same rate limit, and every attempt consumes provider quota. Repeated failures across knowledge bases usually mean a tenant-wide throttle rather than a problem with your files — check with your administrator before continuing.
A file contributes only after it shows Synced. To retry several failed files, select the dataset's ⋮ → Retry failed files only. See Sync & versions.
Legacy Dataset and Legacy Knowledge no longer appear in Knowledge. Use datasets and knowledge bases instead.
Maintained by Abhishek Paul
AI-assisted, human-approved

Last updated
Was this helpful?
Was this helpful?

