AI assistant authentication and permissions

A connected assistant never has your credentials: it receives a token, a kind of digital badge that carries a precise list of permissions. By the end of this page, you will know what you grant on the authorisation screen, how these permissions are capped, who can connect an assistant, and how to cut off access.

OAuth in a nutshell

The browser connection relies on OAuth, the standard used when an application asks you “Allow access to your account?”. You sign in to SynkriaOps, you choose what the assistant will be able to do, and SynkriaOps gives it a token limited to those choices. Your password never leaves SynkriaOps.

1. You add the MCP server address in the assistant.
2. The assistant opens your browser on app.synkriaops.com. If you are not signed in, SynkriaOps asks you to sign in, then brings you back to the request.
3. The authorisation screen appears: you choose the scope and the permissions.
4. You click Allow N permissions (or Cancel).
5. The browser sends you back to the assistant, which receives its token.

Check the address

The authorisation screen is always served by app.synkriaops.com. If the address shown by your browser is different, do not enter anything and close the page.

The authorisation screen, block by block

Block	What it shows
Allow [assistant] to access [company]?	The name declared by the assistant and the chosen target. The mention “Access revocable at any time” reminds you that you can withdraw it.
Scope	The companies and firm where you can connect an assistant, with your role, the currency and the accounting system (normal system or minimal cash system). If there is only one choice, it is preselected.
Branches of this token	Only if the company uses branches: where the assistant will be able to Read and Act.
Accessible files	Only for a firm: the client files the assistant will be able to read.
Access level	Read only (recommended), Accounting assistant or Custom.
What you are allowing	Permissions grouped by area: Financial overview, Purchases and suppliers, Sales, customers and reminders, Accounting entries, Sensitive actions, Firm client files.
What this allows	A plain-language summary of what the assistant will and will not be able to do.

Permissions that your subscription, rights or tier do not include are not shown: a note indicates how many were hidden.

The three access levels

Level	What the assistant can do
Read only (recommended)	Read financial data: general ledger, trial balance, entries, banking, third parties, matchings, VAT, journals, fiscal years, supplier invoices, reminders. Nothing is changed.
Accounting assistant	In addition: prepare draft entries, record and categorise supplier invoices, create and edit third parties, propose a third party on a bank transaction, prepare reminder templates and scenarios. You keep the final validation.
Custom	You tick permissions one by one, including sensitive actions.

Sensitive actions

Posting an entry, sending an invoice or a reminder, paying or posting a supplier invoice, matching, unmatching, reconciling, cancelling an entry, changing a customer’s email address, generating, stopping or archiving a recurring invoice: no predefined level includes these actions.

To grant them, you tick them one by one, then tick I understand and I allow these actions. Unticking this confirmation immediately removes the sensitive actions already ticked.

Booby-trapped documents

A document written by a third party (supplier invoice, PDF, label) can contain hidden instructions aimed at the assistant. For an assistant that reads this kind of document, the screen recommends “Accounting assistant” and keeping validation, payment and sending for yourself. See Security and good practice.

The principle: never more than you

An assistant’s actual permission is the intersection of four limits:

• your role in the company (Administrator, CFO, Accountant, Auditor);
• your subscription;
• your assistant tier, if the Administrator has assigned you one;
• what you ticked at authorisation (and, where applicable, the branches or files chosen).

This calculation is redone on every call. If your role is lowered, the assistant immediately loses the corresponding permissions. A permission that has not been granted does not cause an error mid-conversation: the corresponding tool simply does not exist for the assistant.

Who can connect an assistant

In a company, the Administrator can always connect an assistant, within the limits of their own permissions. They decide who else can, in Settings → AI assistants and MCP, Who can connect an assistant? block:

Setting	Effect
Only you (default)	No colleague can connect an assistant.
People you choose	Only the colleagues authorised in the list.
All colleagues	Everyone connects their own assistant, within the default tier or the one you assign them.

For each colleague, the Administrator chooses a tier (Read only or Accounting assistant) and can add Custom actions, including sensitive actions, for that person only. Each change requires an identity confirmation and is recorded in the audit log. The full guide for management (example profiles, effect of a withdrawal on assistants already connected) is in Management decides who uses an AI assistant.

Roles concerned

Only the CFO, Accountant and Auditor roles can receive this delegation. The Reader (client) role can never connect an assistant. A colleague who is not authorised sees the message “Only the company’s super administrator can connect an AI assistant…” but keeps the list of their own accesses and can delete them.

Firm: one access for several files

An accountant who is a member of a firm can choose their firm as the scope. A single access then covers several client files.

1. In Scope, choose the firm.
2. In Accessible files, tick the files (from 1 to 200). Files are split between Files created by the firm and Files where the company invited the firm; the latter may carry the mention Limited rights on this file, because the company sets what the firm can do there.
3. Choose the access level, then Allow N permissions.

For each request, the assistant must designate the target file: it gets the list with the list_firm_client_files tool (Firm client files permission), and the response always recalls the file on which the action was performed. Permissions are recalculated on every call: what you can do on the file, what the company grants the firm module by module, and the file’s visibility (a confidential file remains reserved for those who can see it).

Firm setting (“Who can connect an assistant”)	Effect
Managers only (default)	Colleagues cannot connect an assistant.
People I authorise	Managers, and the colleagues ticked.
All colleagues	Everyone can connect an assistant on their own files.

Firm accesses are managed in Firm settings → Machine access tab. The client company does not see and does not revoke the firm’s accesses: a colleague revokes their own, a manager those of the firm.

Branches

If the company uses branches, the authorisation screen shows Branches of this token: for each branch, your rights (Read or Read and act) and two boxes, Read and Act. At least one branch is required; the branch where you work is suggested by default.

• You can only entrust the branches where you read and act yourself.
• New branches: Do not add them to this token (recommended) or Add them automatically, within my rights.
• The assistant then has the list_agencies tool, which shows where it can read and act.
• An operation reserved for head office is refused for an access that does not cover all branches (code HEAD_OFFICE_SCOPE_REQUIRED).

Validity

Access	Duration
Browser connection	90 days, without automatic renewal. At expiry, the assistant reopens the browser and you see again what you are granting.
Agent key	The expiry chosen at creation, or none (until revoked).
Authorisation screen	The request expires after 10 minutes: beyond that, restart the connection from the assistant.

Each access has a status: Active, Expires soon (14 days before expiry), Expired, Revoked or Not active yet.

Revoking an access

1. Open Settings → AI assistants and MCP.
2. Find the access in Connected applications or Agents and automations, then click Manage access.
3. Click Revoke access, then Yes, revoke.

Revocation is immediate and final: the assistant’s next call is refused. The Administrator sees all the company’s accesses, with Filter by colleague as soon as there are several authors, and can revoke those of others. A colleague sees and revokes their own.

Removing the connector is not enough

Removing SynkriaOps from your assistant’s connectors does not revoke access on the SynkriaOps side. To cut off access, revoke it in SynkriaOps.

Other events cut off or reduce an access without revocation:

• SynkriaOps support closes the account’s machine access: all accesses stop at the next call;
• the user account that created the access is disabled;
• the Administrator lowers the tier or closes the “Who can connect an assistant?” setting: the effect applies within a few seconds.

Changing an access’s permissions

An access’s permissions cannot be changed afterwards:

• Browser connection: reconnect the application from the assistant, you see the authorisation screen again.
• Agent key: click Rotate. A new agent is prepared with the same permissions, which you adjust; deploy the new key, check that it works, then revoke the old one. In that order, so as not to cut the service.

Agent keys

An agent key is a secret of the form sk_live_…. SynkriaOps shows it only once, at creation, and only keeps a fingerprint of it: nobody, not even support, can retrieve it. If you lose it, create another one and revoke the old one.

Creating a key follows the same rules as a browser connection: machine access open, right to connect an assistant, permissions capped by your role, subscription and tier, identity confirmation. The procedure is in Connect an assistant.

See also

• Connect an assistant →
• Understanding roles and permissions →
• Accounting expert permissions →
• Security and good practice →