> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insight.nobly.dk/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to AI assistant access

> Connect an AI assistant to Nobly Insight over the Model Context Protocol (MCP) — what it can reach, who decides, and what every request still has to pass.

## What is AI assistant access?

AI assistant access lets a tool such as Claude query Nobly Insight directly, using the **Model Context Protocol (MCP)** — an open standard for connecting assistants to the systems they need to answer with. Instead of pasting documents into a chat, the assistant asks Insight and gets the answer from your own content.

The assistant connects **as you**. It signs in with your account, and every request it makes carries your identity — so it sees exactly what you would see, and nothing more.

<Note>
  An assistant never gets its own account, and never sees more than the person using it. If you cannot open a document in Insight, neither can the assistant you are running.
</Note>

## What has to be true before an assistant sees anything

Three things stack, and all three must allow a request:

<Steps>
  <Step title="Available for your tenant">
    AI assistant access is provisioned per tenant. Confirm it is switched on for yours before you begin — if it is not, there is nothing to connect to.
  </Step>

  <Step title="Granted to the user's group">
    Availability alone exposes nothing. Each capability is a separate permission, granted per user group on the [Permissions screen](/permissions/managing-permissions). Someone with no MCP permission connects successfully and finds no capabilities at all. See [Granting access](/mcp/granting-access).
  </Step>

  <Step title="Allowed by the person's own document rights">
    The permissions decide *which capabilities* someone may use. Their existing [document access rights](/configuration/document-access-rights) still decide *which documents* they reach. A search through an assistant returns the same rows the same person would get from the search page — no more.
  </Step>
</Steps>

## What each capability exposes

Grant these deliberately: they differ sharply in how much they reveal. Decide with the data in mind, not the feature name.

| Capability    | What the assistant can reach                                                                                                  |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Catalog**   | Configuration names only — which document types and keyword types exist. No customer data.                                    |
| **Searches**  | Search results, including the keyword values on each row. For most solutions that includes personal data such as CPR numbers. |
| **Documents** | Document metadata, revision history, and **the document content itself**.                                                     |
| **Keywords**  | Keyword values on a document, and the contents of keyword datasets.                                                           |

Catalog is the mildest and is usually what makes the rest useful — an assistant cannot build a sensible search without knowing which document types and keyword types exist.

## What is recorded

Assistant activity is not a side channel. It lands in the same places you already review:

* **Document retrieval** is written to the document history, under the person whose account the assistant is using — the same record a download through the web client produces.
* **Searches** are recorded in the search audit trail, marked as having come from an assistant, so you can tell them apart from searches run in the product.

Search auditing for assistants is always on. It does not follow the setting that controls auditing for the search page, so a tenant that has not switched that on still gets a record of what its assistants searched for.

## What assistants cannot do

Access is **read-only**. An assistant can find, read, and summarise; it cannot create, edit, delete, or reindex anything, and there is no permission that lets it. Caseflow objects are not reachable either.

## Where to read next

<Card title="Granting access" icon="key" href="/mcp/granting-access" horizontal>
  The permissions that decide which capabilities a user group's assistants may use, and how to grant them.
</Card>

<Card title="Connecting an assistant" icon="plug" href="/mcp/connecting-an-assistant" horizontal>
  The exact commands for Claude Code, Codex, and the hosted Claude connector.
</Card>

<Card title="Application permissions" icon="key" href="/permissions/application-permissions" horizontal>
  The full catalogue of application permissions, grouped by area.
</Card>