Creating a knowledge base
Creating a knowledge base takes two fields. Getting content into it is the real work, so this page goes straight on to connecting its first source — a connector that keeps pulling documents in for you.
- The Knowledge Base module visible in your left-hand navigation.
- To connect a source, an IntELIEKonnect import connector that is already Active and Connected. Nothing needs to exist to create the knowledge base itself.
If Knowledge Base isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.
Steps
In the left rail, select Knowledge Base. Overview above it is the page people ask questions from; knowledge bases are created on this card grid.
Select Create KB. The Add Knowledge Base panel opens on the right. Enter a Name (2–100 characters) and a Description (up to 250), then select Save. Retrieval, generation and safety settings start from defaults you can tune later on Settings.
Select Details on the new card. Every knowledge base opens on Documents and carries its own section list — Documents, Q&A, Sources, Ingest status and the rest.
Select Sources, then Manage connectors on the IntELIEKonnect tile. It is the only selectable tile — the others do nothing yet.
Select Connect on the connector you want. In the panel, set Access metadata — this is the access stamped on every document it pulls in. Leave Chunking template on Auto-detect (default) unless the source is all one document type, add Custom tags if you want them on every document, then select Save.
Select Fetch now on the row. Documents appear on Documents badged IntELIEKonnect as they arrive, and their indexing shows on Ingest status.
What success looks like
- Knowledge base created successfully! appears, the panel closes and the card is in the grid.
- The connected row reads Connected with the Enabled switch on.
- Fetch started — new documents will appear in Documents shortly. appears, then rows land on Documents.
What the card's status pill means
The pill on each card is worked out from the knowledge base itself, not from its documents. No documents reads Empty; one or more reads Indexed — even if every one of them failed to process. Indexed is not a promise that anything is answerable, so check Ingest status after a first load.
If something goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Save stays greyed out on Add Knowledge Base. | Name or Description is empty or invalid — messages only appear once you have left the field. | Select into each field and out again to reveal the message, then fix it. |
A red message reads knowledge_base with name '…' already exists. | The name is already used in your organisation. | Choose another Name. There is no inline check, so this only appears on Save. |
| The connector you want is not listed. | Only import connectors that are Active and Connected are offered, and an absent one is not explained. | Finish it first — see Verifying and Enable, disable, delete. |
| Save is greyed out in the Connect panel. | Access is internal with no Access role, Department or People group — nobody could retrieve the documents. | Tag one of them, mark one Unrestricted / all internal users, or turn on Public. |
| The pane is replaced by Access Forbidden. | Every tab is visible to everyone; the permission is checked when the page loads its data. | Ask a workspace administrator — see Permissions and module visibility. |
Next
- Uploading documents to a knowledge base — one-off files and new versions.
- Sources — pausing, editing and disconnecting one.
- Ingest status — following content as it is indexed.