Skip to main content

ChapterArtificial intelligence

Chapter 13 — Connecting an outside AI assistant

Your own AI assistant (Claude Code, Codex…) can read the firm's data and prepare drafts, through a connection that you authorize, that you follow and that you cut whenever you want. Sensitive actions wait for a person, except those you yourself tick « without approval ».

In this chapter

  • What a connection is, and who can create it
  • Connecting step by step, the consent page
  • What the assistant reads, prepares and asks
  • The console: approve, view, revoke
  • Actions without approval, firm rules, limits
  1. Your assistant
  2. Consent
  3. Connection
  4. Console
Book contents

What a connection is

IntegraSys speaks the MCP language, which several AI assistants on the market understand. An assistant you already use on your computer can therefore plug into the ERP: it reads the firm's data and prepares drafts, in one company only and with your own rights.

QuestionAnswer
For which firm?Open to every company: there is nothing to switch on.
Which module?None to connect. Each tool needs the module of its screen: invoices need Operations, tasks the Tasks module. A tool follows the access of its screen: when the module's screen is closed to the company, the tool is not offered.
What cost?No IntegraSys AI credit is used: you pay for the outside assistant with its own vendor.
Where?In your assistant, and in the console at the address platform.integrasys-erp.com. The ERP has no menu entry for it.

Who can connect an assistant

Line in the role editorWhat it allowsWho has it by default
AI connections › Connect an AI agentAuthorize an outside assistant on the company.The owner and administrators; no Manager, Member or Viewer.

To open it to a colleague, tick Connect an AI agent in a custom role (list of rights by groups). Without this right, the consent page refuses: « Votre rôle dans cette société ne permet pas de connecter un agent IA : le droit « Connexions IA - Connecter un agent IA » est accordé par le propriétaire ou un administrateur. » (Your role in this company does not allow connecting an AI agent: the right « AI connections - Connect an AI agent » is granted by the owner or an administrator.) A client portal account can neither connect an assistant nor open the console.

The right is checked at the moment of consent. Then, at every call from the assistant, IntegraSys reads your account, your membership of the company, your rights and the modules again: a role taken away or a module stopped applies from the next call.

Connecting, step by step

The assistants tried with IntegraSys are Claude Code and Codex. The other MCP-compatible applications (ChatGPT, Claude on the desktop or on the web…) have not been assessed yet.

The address to give your assistant:

  1. Add IntegraSys to your assistant with this address. In Claude Code: claude mcp add --transport http integrasys https://platform.integrasys-erp.com/mcp, then claude mcp login integrasys. In Codex: codex mcp add integrasys --url https://platform.integrasys-erp.com/mcp, which starts the connection by itself.
  2. Your browser opens. If you are not signed in to IntegraSys, the ERP's sign-in page appears first, then brings you back to the consent.
  3. On the consent page, read what the application asks for and choose the Société (company).
  4. Click Autoriser (Authorize). Your assistant is plugged in: it can work.
Screen to comeThe page « Connecter une application à IntegraSys » (connect an application to IntegraSys): the application's name, the line « Nom annoncé par l'application elle-même, non vérifié par IntegraSys. », the « Société » box with two companies, the « Ce que l'application pourra faire » box with its three lines, the « Refuser » and « Autoriser » buttons.

It shows at every authorization, whatever the application. It is written in French. It carries:

  • the title Connecter une application à IntegraSys (connect an application to IntegraSys) and the sentence « Cette application pourra agir en votre nom, dans une seule société, avec vos propres permissions. » (this application will be able to act on your behalf, in one company only, with your own permissions);
  • the application's name, with the warning « Nom annoncé par l'application elle-même, non vérifié par IntegraSys. » (name stated by the application itself, not checked by IntegraSys), and the place the authorization code will go to (« Le code d'autorisation sera envoyé à … », the authorization code will be sent to …; for an application on your computer: « Adresse locale : cet ordinateur. », local address: this computer);
  • the Société (company) box: one option per active company of your account. Choose one;
  • the Ce que l'application pourra faire (what the application will be able to do) box, one line per request:
LineMeaning
« Se connecter à IntegraSys et voir l'identité de la connexion » (sign in to IntegraSys and see the connection's identity)Knowing who is connected, in which company.
« Lire les données autorisées de la société choisie » (read the authorized data of the chosen company)Reading what your rights show you on screen.
« Préparer des brouillons ; les actions sensibles restent soumises à votre approbation » (prepare drafts; sensitive actions remain subject to your approval)Creating drafts, and proposing the sensitive actions.
  • two buttons: Refuser (Refuse: nothing is saved) and Autoriser (Authorize);
  • under the buttons, a reminder: sensitive actions remain subject to your approval, except those ticked « sans validation » (without approval) in the console; the connection can be cut at any time; the data sent is then governed by the policy of the connected application.

What the connection allows, and what it does not

  • One connection = one assistant, one person, one company. The assistant can neither change company nor name another one: the connection is sealed to the one you chose. For another company, go through the consent again.
  • Your rights, no more. Each call is bounded by what the consent page granted and by what your rights allow on that day.
  • Nothing but the assistant. The key the assistant receives only serves this connection: it opens neither the ERP nor the console, decides no approval and manages no connection.
  • It lasts. Access renews by itself every hour as long as the assistant is in use. The connection stays in the console until you revoke it, but an assistant left unused for 30 days must go through the consent again, which unticks its actions without approval. If an old key is used again, IntegraSys cuts the whole chain as a precaution: the assistant then asks you to connect again, and you go through the consent again.

What the assistant reads, prepares and asks

It reads

AreaExamples
Sales and day-to-dayClients, articles, invoices, quotes and pre-invoices, suppliers, purchases, CRM, conventions, domiciliations, disbursements, time entries, calendar, tasks, notifications, library (without the files).
Finance, accounting, stockCash registers, bank loans, financial years (without the entries), tax returns, audit missions, stock, bills of exchange.
LegalThe company's record, articles of association, minutes, notices of meeting, share transfers, deeds, forms.
OtherNumbering sequences, your own rights, Business Plan, extractor results, complaints and tickets, activity log.

It reads as your screens do: the cash registers assigned to you (when the firm assigns its cash registers); for a staff member, only their own files and their own time entries; your CRM records when the firm restricts visibility; archived lines stay hidden where the screen hides them. A list reaches it in pages of 25 rows, 100 at most.

Never sent to it: bank details (suppliers' RIB, bills of exchange), salaries, CNSS numbers, RIB and addresses of employees and agents, keys and secrets, the raw text of OCR readings, the text of articles of association and the remarks of minutes, the internal notes of tickets, the before / after values and the IP addresses recorded in the activity log. A text written outside the firm (a supplier invoice, a ticket from a client) is presented to it as data, never as an instruction.

It prepares

Without asking anyone, within your rights: a draft invoice, a draft quote, and with the Tasks module, create a task, tick a step, complete a task. A draft stays a draft: its validation goes through the screen, or through the console.

It asks

The four sensitive actions become an approval request in the console:

Action (name in the « Actions without approval » box)
« Validate a sales document (invoice, quote, pro forma, credit note) »
« Record a received payment »
« Prepare a credit note »
« Send a payment reminder by e-mail »

In Approvals, the card also carries the document's number, for example « Record a payment received on FAC00013 ». The assistant gives you the link to the request in the console. A request not decided expires after 30 minutes.

The console: approve, view, revoke

The console is called MCP Platform. Click Sign in with IntegraSys: it goes through your usual account, « no password is typed here ». The session lasts 8 hours; Sign out closes it. A menu changes the language: French, English or Arabic.

TabWhat it shows
ApprovalsThe pending requests of your companies, with their number in a badge.
ConnectionsYour connections (and, for an owner or an administrator, those of the whole company), the actions without approval, the firm rules.
ActivityThe decided requests, and the reads made by the assistants.

Approve or refuse

Screen to comeThe « Approvals » tab with a « Record a payment received on FAC… » card: requested by, expires, the payment's preview, and the « Approve and run » and « Refuse » buttons.

Each card shows the action, who asked for it (« requested by »), its deadline (« expires ») and a preview of what will be written. It is seen by the members who have the right to make this action on screen and the module concerned; the author of the request or a colleague who has this right can decide.

ButtonWhat happens
Approve and runGreyed out as long as the preview is not loaded. The console asks « Approve and run this action? » and warns that the action runs at once and cannot be undone here. Keep it pending keeps the request.
Refuse« Refuse this action? »: the refusal is final; to do it, the assistant will have to propose it again.

If you answer no in one of these windows, the card says so: « Nothing was sent: the action is still waiting for your decision. »

View and revoke a connection

Screen to comeThe « Connections » tab: a connection card (assistant's name, company, « Authorized on », « Last call », « Revoke » button), the « Actions without approval » box and the « Firm rules » line.

Each connection shows the assistant's name, the company, its authorizations (as codes: mcp:use, mcp:read, mcp:write), Authorized on and Last call. On a colleague's connection, the card says « Connected by … ». You see your connections; an owner or an administrator sees and revokes all those of the company.

  1. Connections tab, on the assistant's card: Revoke.
  2. The console asks « Revoke this connection? » and states that its tokens are destroyed immediately.
  3. Confirm Revoke (or Keep the connection). The message « Connection revoked. » appears.

The assistant loses access at once; it will ask you to connect again if you start it again. When the firm deactivates or removes a member, their connections stop working from the next call (they stay displayed); when the IntegraSys account itself is deactivated, all its connections are revoked.

The activity

The Activity tab lists the last 100 decided requests; an action that went through by itself is marked there « Ran without approval: the action is ticked on its connection. ». The Agent reads section keeps one line per read by an assistant: when, which connection, which tool, how many rows, and the outcome (Served, Failed, Refused). These lines are kept 90 days.

Actions without approval and firm rules

On their own connection, the person who created it can tick actions that the assistant will carry out without going through the console, in the Actions without approval box. They can only tick actions they have the right to approve themselves. Nothing is ticked at the start.

  1. Connections tab, Actions without approval box: tick the actions (or Select all).
  2. Click Save. For an action added, the console asks « Run without approval? »: Run without approval confirms, Keep approvals gives up. Removing an action asks nothing.

The safeguards of these boxes:

  • a box is valid for 30 days; saving again extends it;
  • a payment or a credit note goes through by itself up to a ceiling, 1 000,000 in the invoice's currency by default, which you can change;
  • 20 actions at most per connection and per 24 hours, 5 of them reminders;
  • never the validation of a credit note, nor that of a document created by an outside assistant connected to the company;
  • each action that goes through this way rings the bell;
  • a new authorization of the same application on the same company unticks everything; the consent page says so before Autoriser;
  • saving needs a recent sign-in: « For safety, this setting needs a sign-in less than 15 minutes old: sign in again, then retry. » (link Sign in again).

Beyond a safeguard, the action does not go through by itself: it comes back as a request in Approvals.

The firm rules. On the same tab, an owner or an administrator decides, company by company, whether actions without approval are allowed: Allow them or Forbid them (the badge says « Actions without approval allowed » or « … forbidden »). They are allowed at the start. Forbidding them unticks nothing: everyone's boxes take effect again when they are allowed again, as long as their 30 days have not run out. This setting also needs a sign-in less than 15 minutes old.

The limits

LimitWhat happens
One reminder per invoice every 7 days, whoever sends it« A reminder for this invoice left less than 7 days ago: nothing was sent. »
60 saves per hour on invoices, payments, purchases and cash registers, for the person who connected the assistant (even when a colleague approves), shared with what they enter on screen« IntegraSys is limiting writes right now: nothing ran, and the action is still waiting. »
4 calls at a time per connectionThe next ones wait up to 30 seconds, then are refused.
45 seconds per requestBeyond that, the assistant receives an error and can try again.
A console session of 8 hoursYou must sign in again.