> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/kaiya/ask-across-your-documents-unstructured/how-to-connect-to-unstructured-data.md).
# How to connect to unstructured data?
Learn how Tellius connects to unstructured data sources for AI-powered search, document analysis, and conversational insights across enterprise content.
To add a new unstructured data source, click the **"Create new connection"** button on the **Unstructured** tab of the **Data → Connect** page. This takes you to the **Add new connectors** page, open on its **Unstructured** tab. The **Structured** tab next to it lists the database and warehouse connectors.
A **Search** bar in the top-right corner lets you filter the available connector types by name if needed. **Import Dataset** next to it brings in datasets from a Tellius export file (.zip); see [Create new datasource](https://help.tellius.com/data/create-new-datasource).
### Available Content Repositories
Under the **Content Repositories** section, the following seven unstructured connector types are available. Clicking on any connector type except **File Upload** opens the **"Add a connection"** dialog with fields specific to that connector.
**Google Drive:** Connects to files and folders stored in Google Drive.
**Amazon S3:** Connects to objects stored in Amazon S3 buckets.
**Gong:** Connects to call recordings and transcripts stored in Gong.
**Azure Blob Storage:** Connects to blobs stored in Azure Blob Storage containers.
**Google Cloud Storage:** Connects to objects stored in Google Cloud Storage buckets.
**SharePoint:** Connects to files in Microsoft SharePoint. See [Connect to SharePoint](https://help.tellius.com/kaiya/ask-across-your-documents-unstructured/how-to-connect-to-unstructured-data/connect-to-sharepoint).
**File Upload:** Uploads documents straight from your computer. Selecting the tile opens your computer's file picker, where you can pick one or more files. In Tellius 6.4 you can upload **PDF**, **DOCX**, **PPTX**, **MD** and **TXT** files. A message confirms how many files were uploaded, and the uploaded files are listed under the **dataset\_upload** connection on the Unstructured tab. If a file has another format, Tellius shows "Only PDF, DOCX, PPTX, MD and TXT files are supported." and uploads nothing. In releases before Tellius 6.4, File Upload took PDF files only.
{% hint style="info" %}
**File Upload or a connector?** Use **File Upload** for a handful of documents you have on your computer. Use a connector, such as Google Drive or SharePoint, for a library that keeps growing, so new files reach Kaiya with each sync.
{% endhint %}
Once your unstructured sources are connected and indexed, Kaiya can search the documents in them. In Tellius 6.4 you don't need @ mentions. Kaiya picks the right workspaces and documents from your question, so name the report, document or topic in the question. In releases before Tellius 6.4, you could scope individual Kaiya questions to documents and folders using @ mentions in the conversation input, to target a specific report or library instead of searching the full workspace every time.
## Add @ mentions in conversations
{% hint style="warning" %}
**In releases before Tellius 6.4.** This section describes @ mentions in releases before Tellius 6.4. In Tellius 6.4 you don't need @ mentions. Kaiya picks the right workspaces and documents from your question, so name the report, document or topic in the question. If the **@** list appears in the message box, you don't need it. See [How Kaiya uses your documents in Tellius 6.4](https://help.tellius.com/kaiya/ask-across-your-documents-unstructured#how-kaiya-uses-your-documents-in-tellius-6.4).
{% endhint %}
In releases before Tellius 6.4, you could scope a Kaiya question to specific documents or folders by typing `@` directly in the chat input. Kaiya then searched only the sources you selected, returning answers grounded in exactly those files instead of your full workspace.
### Why use @ mentions
In releases before Tellius 6.4, in unstructured mode, when you ask Kaiya a question without an @ mention, it searches the full workspace corpus. This works well when you want broad coverage. It works less well when you already know the answer lives in a specific quarterly report, a single payer policy, or one folder of summaries. Without scope, the relevant document competes with hundreds of others for retrieval attention, and your answer can come back diluted.
@ mentions solve this by letting you state the scope inline, while you type. You do not open a separate filter panel. You do not navigate to a document picker. You do not restate which files you mean across follow-up questions. The mention pills sit in the message itself, and your chat history preserves them so you (and anyone the chat is shared with) can see what was scoped at every turn.
The result: precise answers from exactly the sources you care about, without leaving the chat input.
{% hint style="info" %}
**In Tellius 6.4** you don't need @ mentions. Kaiya first checks which document workspaces can answer and searches those. It can search again with different wording, narrow the search to specific documents, or read a whole document. Kaiya picks the right workspaces and documents from your question, so name the report, document or topic in the question. If the **@** list appears in the message box, you don't need it. See [How Kaiya uses your documents in Tellius 6.4](https://help.tellius.com/kaiya/ask-across-your-documents-unstructured#how-kaiya-uses-your-documents-in-tellius-6.4).
{% endhint %}
#### How to use @ mentions
**1.** Type `@` anywhere in your message. A dropdown opens, listing:
* Recent documents in your workspace
* Folders derived from your document paths
In Tellius 6.4 you don't need this list, because Kaiya picks the right documents from your question. If the list appears, it shows your indexed documents, each with an icon for its source, such as Google Drive or Amazon S3, and the name of the connection it comes from.
**2.** Use the arrow keys to move through the list, then press **Enter** to select.
**3.** Each selection appears as an inline pill in your message, showing with an **×** button to remove that mention
{% hint style="info" %}
You can add more mentions to the same message. The total cap is 10 selections per message (documents and folders combined).
{% endhint %}
**4.** Finish typing the rest of your question and send. In releases before Tellius 6.4, in unstructured mode, Kaiya searches only within the sources you selected. In Tellius 6.4 you don't need @ mentions: name the report, document or topic in your question instead.
**Example:**
*@Q3 Financial Report.pdf What were the key revenue drivers?*
#### What you can mention
You can mention:
* **Documents** you have access to in the current workspace.
* **Folders** derived from your document locations.
When you mention a folder, the scope expands to every document inside that folder path. This is useful when you want Kaiya to search a whole library, for example all payer policies in a `/policies/payers/` folder, without selecting each file one by one.
#### How scope is enforced
{% hint style="info" %}
**In Tellius 6.4** you don't need @ mentions. Kaiya picks the right workspaces and documents from your question, and your document access is applied to every search. The two behaviors below describe unstructured mode in releases before Tellius 6.4.
{% endhint %}
Two behaviors define how Kaiya handles the scope you set:
* **Explicit scope is respected.** Kaiya informs if you @ mention sources that do not contain information relevant to your question. It does not silently widen the search to other documents in your workspace. Your selection is the authoritative scope.
* **Mentions are preserved.** Your chat history shows the mention pills exactly as you sent them. Anyone with the chat shared can see which sources each answer was based on.
This matters for trust and auditability. When someone asks "where did this number come from," the chat itself shows the scoped sources alongside the citations in the response.
#### Access and visibility
@ mentions follow the permissions you already have in Tellius:
* Admins see all workspace documents in the autocomplete.
* You only see documents and folders you have permission to access. Items you do not have access to never appear in the dropdown.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.tellius.com/tellius-6.4/kaiya/ask-across-your-documents-unstructured/how-to-connect-to-unstructured-data.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
