Connectors
A connector lets you point your own AI assistant at Teralo. Claude, ChatGPT, or anything else that speaks the same protocol connects to your account and can then search and act on your projects from inside its own window, without you moving to Teralo to look something up.
It is the same set of abilities AI Chat has, offered to an assistant you already use.
The page is Settings, then Account, then Connectors, titled AI Connectors.
What is actually connected
Your assistant is not given a copy of your data and is not given a login. It is given a permission to ask, on your behalf, and each question it asks is answered live, checked against your own account at the moment it is asked.
The reasoning stays where it was: Teralo does not run the model. Your assistant thinks with its own subscription, and calls Teralo only to look things up and to act.
It is an MCP server
If you have met the term, this is a remote MCP server: the Model Context Protocol, which is how an AI assistant is given tools it can call. Anything that speaks it can connect, not only the two assistants named below.
Connecting
The Connectors page shows a connector URL with a copy button. Everything starts by pasting that URL into your assistant.
Claude
- Open Settings, then Connectors
- Choose Add custom connector
- Paste the connector URL and confirm
- Sign in to Teralo when the browser opens, then choose what to allow
ChatGPT
- Open Settings, then Connectors, with developer mode enabled
- Choose Create and paste the connector URL
- Complete the Teralo sign-in and consent screen
Either way the sign-in happens in your own browser, on Teralo's own page. Your Teralo password is never given to the assistant, and the assistant never sees it.
Choosing read-only or read and write access
The consent screen carries one choice, and it is worth thinking about for a second rather than clicking past.
Read lets the assistant search and read: mail, contracts, drawings, inspections, the programme, who is on site, what is waiting on you.
Read and write adds the ability to create and send: raise an observation, send a reply, create a permit, act on a workflow step assigned to you.
The choice is stored with the connection and enforced by Teralo, not by the assistant. On a read-only connection the write abilities are not offered to the assistant at all, so it cannot propose one by mistake and cannot be talked into one.
Even on a read-and-write connection two things still hold. Your assistant asks you before it acts, in its own words and its own interface. And every action re-checks your Teralo permissions, so it can only ever do what you could have done yourself.
What it can see
The same as you, on the same terms as AI Chat: one project at a time, your own permissions, guest organisations still seeing only their own rows. See What the AI can read.
Your assistant can ask which projects are available to it, and gets back the projects you are on, or that your organisation hosts if you are an administrator, each of which needs the AI Chat permission on that project. A project with the permission missing is simply not in the list.
An archived project can be read but not written to. That holds even on a read-and-write connection.
What it costs
Nothing, in Teralo terms. Your assistant is doing the thinking, so a connected conversation spends no AI credits.
The one exception is asking it to read pages of a drawing or specification, because that lookup runs Teralo's own page reader rather than a database query. It is charged to the organisation that owns the document, exactly as it is in AI Chat, and it applies on a read-only connection too. See AI credits.
A record of what it did
Every lookup and every action a connected assistant makes is recorded: which assistant, which tool, which project, whether it succeeded. A connector is not a quieter route into your data than the app is.
Managing and revoking a connection
Connected clients lists everything currently connected to your account, each with its name, whether it has read or read and write, when it was connected and when it was last used.
Revoke cuts it off, and takes effect immediately rather than at the end of a session. You can reconnect it later with the same URL.
Revoke a connection whenever an assistant is one you no longer use, or is on a device you no longer have. It costs nothing to reconnect.
Connectors are personal
A connection belongs to one person. There is no organisation-wide connector, and connecting yours does nothing for anybody else: each person who wants one sets up their own, and each one sees only what that person can see.
That also means the answer to "can we connect the company's assistant to the project" is no in the useful sense, and yes in the practical one. Each person connects their own, and each gets their own access.
When it will not connect
Check that AI Chat is in your Teralo sidebar on the project you are asking about. Connectors are gated on the same permission, so a project where you do not have AI Chat is a project your assistant cannot reach either, and the failure shows up as an empty project list rather than as an error about permissions. See How permissions work.