Skip to main content
The Data Sources area is the central hub for every external data connection in Nexalytica. Everything that powers your chats, dashboards, and agents — databases, AI embedding stores, and uploaded documents — lives here. You can add new sources, monitor their health, control who can use them, and manage their full lifecycle from a single interface.

​
Source types

Nexalytica organises sources into three distinct categories, each optimised for a different kind of access pattern.

Data Stores

Relational databases and file imports queried live at runtime. Supported connectors: PostgreSQL, MySQL, BigQuery, MongoDB, CSV, and Excel.

Vector Stores

AI embedding stores used for semantic search. Supported connectors: Pinecone, Weaviate, ChromaDB, and Qdrant.

Knowledge Bases

Uploaded files and folders indexed for retrieval-augmented generation (RAG). Use these to ground chats and agents in your own documents.

​
Browse and filter sources

When you open Data Sources you see a card grid of every source you have access to. Use the controls at the top to narrow the list.

​
Reading a source card

Each card surfaces the key health and ownership signals at a glance. Click any card to open its detail view in the current tab. Hold Cmd / Ctrl or use a middle-click to open the detail in a background tab.

​
Inside a source — the detail view

Opening a source card takes you to its detail view in its own tab. A header shows the source’s status, name, description, and a summary line (last sync, record count, owner), with two action buttons — Test (checks the connection) and Sync now (refreshes the data). Below the header is a strip of sub-tabs; which tabs appear depends on the kind of source. Your last-used tab is remembered per source, so reopening a source returns you to where you were.

​
Add a source

1

Open the connector picker

Click + Add Source in the top-right corner of the Data Sources page.
2

Choose a connector

The picker is grouped into three sections. Select the connector that matches your source type.
3

Fill in the connection form

Enter the required credentials and connection details for your chosen connector. Credentials are stored securely and are never shown in plain text after saving.
4

Save

Submit the form. Nexalytica tests the connection and creates the source card. A status badge reflects the outcome immediately.
Adding a source requires permission to create resources in your department. Contact your department administrator if the + Add Source button is unavailable.

​
Source card actions

Every source card exposes a set of action controls. The controls available to you depend on your permission level.
Disabling a source immediately hides it from all chats, dashboards, and agents that depend on it. Notify affected users before disabling a shared source.

​
Manage Knowledge Bases

Knowledge Bases use a file-browser interface rather than a connection form. The left panel shows your folder tree and the right panel lists the files inside the selected folder.
1

Create folders

Click New Folder to organise your uploads into logical groups (e.g. by project, team, or document type).
2

Upload files

Select a destination folder, then click Upload to add files. Nexalytica indexes uploaded content for RAG automatically.
3

Use in chats and agents

Once indexed, a Knowledge Base appears as a selectable source inside Chat and Agent configuration.
Organising uploads into folders makes it easier to share subsets of your Knowledge Base with specific teams without exposing unrelated documents.

​
Permissions reference

  • Sync, test, and configure the source
  • Enable and disable the source
  • Share the source with others (up to your own permission level)
  • Schedule deletion and restore pending-deletion sources
  • Open the source detail view
  • Read source metadata, status, and schema information
  • Cannot modify, sync, configure, share, or delete
All Owner/Editor capabilities, plus:
  • Toggle the admin view to see all sources across the organisation
  • Filter by owner in admin view
  • Admin view access is logged to the audit trail