Connect your AI assistant

You can connect the AI assistant you already use (Claude, ChatGPT, Cursor, and any other assistant that supports remote MCP connectors) to your Alchex workspace. The assistant can then answer questions from your own documents, registers and tasks, and from the standards in your catalog, without you copying anything across.

Turn it off or on (admins)

AI assistant access is on for every workspace, so members can connect straight away. To stop it:

1. Open Settings → General.
2. Under AI assistants, switch off Allow members to connect their own AI assistant to this workspace.

Switching it off stops every connected assistant at its next request. Switching it back on lets them in again.

Connect an assistant

Copy the address shown under AI assistants, then add it to your assistant as a custom connector:

• Claude (web, desktop and mobile): Settings → Connectors → Add custom connector, paste the address, and sign in when asked.
• Claude Code: claude mcp add --transport http alchex <address>, then sign in when prompted.
• ChatGPT, Cursor and others: add a remote MCP server with the same address; the assistant takes you through the sign-in.

You sign in with your normal Alchex account. If you belong to more than one workspace, the assistant works with the one you choose when you sign in.

What the assistant can and cannot do

A connected assistant works with the same tools Alchex's own assistant uses in the chat, so what it can read and change is the same, and a new ability the Alchex assistant gains reaches your own assistant at the same time.

• It reads. It can find and read documents and what they say, the evidence registers your teams keep, your methods and processes, your roadmap, the compliance overview, a clause's record and what its last check said, the receipts of calls to connected apps, and the standards in your catalog. Unless changes are turned on for your workspace (below), that is all it can do.
• It sees what you see. A connected assistant has exactly your access: the teams you are on, your role, and the standards your workspace has added. Another team's records stay out of reach, and a Reader's assistant is offered no change at all.
• Every read is recorded. Each request appears in your workspace's activity as Read by an AI assistant, with who asked and which kind of read it was. The words you asked about are not stored.
• There is a limit on how fast it can ask. If an assistant asks too much too quickly it is told to wait a moment and try again.

What stays in Alchex: your connected apps (your own assistant brings its own) and the questions and panels the Alchex chat draws.

Making changes

While your workspace has AI assistants switched on, a connected assistant can also change things for you, with exactly your permissions, through the same tools the Alchex assistant uses:

• create a document in one of your teams from the design you settled with it, in its type's standard structure, with anything it assumed marked (recommended default) in the rule it sets;
• edit a document's draft, section by section. If someone has changed a section since the assistant read it, its edit waits as a suggestion instead of overwriting them;
• send a document to someone for approval, the same way the Submit button does, and publish one if you are an owner of its team and no approval is waiting on it;
• create an evidence register, or add rows to one, as suggestions a person confirms;
• run a clause check, and start, switch or build a process;
• build a whole standard in one run: it asks every open question first, asks once to go ahead, then builds each process in the standard's order without stopping to ask between documents, reports each phase as it ends, and picks up where it stopped if you start it again;
• archive a document you asked it to archive. Nothing is deleted: the document leaves the library and you can restore it from its own page;
• delete a document for good, when you ask it to delete one and you are an owner of its team. Its versions and the controls set up on it go with it, and it cannot be restored, so ask for an archive unless you mean it;
• remove a register row you asked it to remove. That is permanent too;
• delete a whole register you asked it to delete, with every row in it. It cannot be restored. Findings, controls and projects are removed one record at a time, never as a whole register;
• remove a control from its document when you ask. The control stops running; the runs it already made stay in their history;
• stop following a standard, when you are the workspace owner and ask it to. The standard leaves your compliance record, its evidence and history stay, and adding it again brings it back.

It deletes only what you asked it to delete, and it can never send anything outside Alchex. Each change is recorded on the record it changed, like any edit you make, and in your workspace's activity as Changed by an AI assistant.

Every change also says why. The assistant gives a reason with each change, the same way Alchex's own assistant does, and the reason is kept in the record's history beside the change. A change that gives no reason is not made.

Disconnect

Remove the connector in your assistant's settings. An admin can also switch off AI assistants for the whole workspace at any time.