> ## Documentation Index
> Fetch the complete documentation index at: https://flow9.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# AI connections

> Turn AI assistant access on for your workspace and choose what it may do.

**Settings → Developers** controls whether people in your workspace can connect
an AI assistant such as Claude or ChatGPT to Flow9. The same page holds
**Connected Apps**, where connections are reviewed and revoked, and **Deletion
Requests**, where an admin approves anything an assistant asked to delete.

<Note>
  Access is **off by default**. Nobody can connect an assistant until an admin
  turns it on, and only workspace admins can change these settings.
</Note>

## Enable MCP access

The card is called **AI Assistant (MCP)**. Its first switch, **Enable MCP
access**, allows connecting an AI assistant to this workspace. Until it is on, any attempt to connect signs in successfully and
then reports that MCP access is not enabled — which is the intended behaviour,
not a fault.

<Frame>
  <img src="https://mintcdn.com/flow9/nKfA6qJ3O3HRrwzV/images/connect-ai/admin-mcp-access-card.png?fit=max&auto=format&n=nKfA6qJ3O3HRrwzV&q=85&s=0afe0c1317d9bb7c5c8eaaeb582aa121" alt="The Developers page with the AI Assistant (MCP) card" width="1906" height="919" data-path="images/connect-ai/admin-mcp-access-card.png" />
</Frame>

Switching it off later ends every existing connection at once.

## Allow record writes

The second switch, **Allow record writes**, lets an assistant create and update
records rather than only read them.

Leave it off to keep every connection **read-only**. In read-only mode people can
ask questions, search and get summaries, but every tool that would change a
record is withheld — regardless of what an individual ticked when connecting.

<Tip>
  A good way to start: enable access with writes off, let the team use it for
  reading and reporting for a week, then decide about writes.
</Tip>

## Deletion is separate

Allowing writes does **not** allow deletion. Deletion is a further step and is
off unless your workspace has specifically asked for it.

Even when enabled, an assistant cannot destroy a record. It creates a **deletion
request**: the record is hidden, an administrator reviews it under
**Settings → Developers → Deletion Requests**, and it can be restored until
approved.

## Where people connect

Once you have enabled access, people connect from their own assistant using:

```
https://mcp.flow9.online
```

Each person signs in as themselves and approves their own permissions. An
assistant can never do more than the person who connected it — if someone has no
access to a module, neither does their assistant.

The user-facing steps are in [Connect your AI](/guide/connect-ai/overview).

## Seeing and removing connections

Each person manages their own connections under **Settings → Connected Apps**,
where they can see what has access and revoke it.

To end everything at once, switch **Enable MCP access** off.

## What an assistant can never do

Regardless of these settings, an AI connection cannot send SMS or email, place
calls, permanently delete records, or reach another workspace's data. See
[Security](/guide/connect-ai/security).
