Integrations
Connecting the platform to your own assistant
Letting an AI assistant of yours query and act on your cases.
If your team already works with an AI assistant, it can query your cases directly instead of someone copying and pasting what is inside. It is a connection that is authorised and scoped, not open access.
The three access levels
| Level | What it allows | When to use it |
|---|---|---|
| Read only | Query and answer questions about what is there | Nearly always. It solves 90% of cases |
| Read and write | Also create and modify | When the assistant has to leave work done |
| Full | All of the above without restriction | Rarely, and with a very good reason |
Important
Start with read-only and stay there if it serves you. An assistant that can write can make mistakes writing, and what it does is recorded in the name of the organisation that authorised the connection — yours.
What it genuinely solves
Watch out
The connection inherits permissions: the assistant sees no more than the account that authorised it. If that account is an administrator's, the assistant sees everything. Authorise it with a scoped account, not your most privileged one.
Worth knowing
Every query the assistant makes consumes, exactly as if a person made it. An assistant querying in a loop spends in a loop: check the breakdown in the first week.
Before connecting
Decide which assistant, with which account and at what level. Those three answers written down somewhere avoid the conversation a year from now about who authorised what.
›Can I revoke it?
Yes, at any time.
›Is what it queries recorded?
Yes, like any access to data.
›Does it see other organisations' documents?
No. Nothing crosses the separation between organisations.
A real case
The situation
A team authorises the connection with an administrator account to move fast.
What you do
- Redoes it with a scoped, read-only account
What you get
The assistant still answers what they needed and can no longer see payroll.
The situation
The team wants to query files from their own internal assistant.
What you do
- Connects the assistant through the supported route
- Limits the scope to the files that account can see
What you get
Queries happen where people already work, and the assistant sees no more than the person would.
The situation
The in-house assistant returns data from other files.
What you do
- Reviews which permissions it is connected with
What you get
The assistant's scope is the account's, not the company's.
The situation
It is connected and nobody knows what it queries.
What you do
- Checks the assistant's call log
What you get
Usage is auditable like any other access.
The situation
The assistant asserts things that are not in the documents.
What you do
- Checks which files the answers come from
What you get
Claims can be cross-checked.
The situation
An assistant answer is shared with a client.
What you do
- Reviews the text and its source before sending
What you get
What goes out carries your judgement.
This article answers
- connect claude or chatgpt to the platform
- mcp assistant integration
- query cases from my assistant
- give an external ai access