All documentation

Documentation Security and your data

Connected assistants' access

How an AI assistant connects to Sterodata, what it can reach, how its access is stored, and how that access ends.

Members can connect an AI assistant, such as ChatGPT, Claude or Codex, at https://api.sterodata.com/mcp. This page is about what that connection can do and how it is kept. How to connect one is in Assistants.

It acts as the person who connected it

  • An assistant gets exactly the access of the member who connected it, in every workspace they belong to, and nothing more. Field limits, views and every other access rule apply to it as they apply to that person (see Access).
  • It cannot reach a workspace that person is not a member of.
  • It works through the same API as the app, so every request is checked the same way.
  • What it changes carries that person's name in Created by and Updated by, and the record of access changes names the assistant too.

How it connects

The assistant sends the member to Sterodata to sign in, and the member sees which assistant is asking, that it will act as them, and where they will be sent back. Nothing is connected until they choose Allow. A request lapses after 15 minutes if nobody answers it, and the one-time code that Allow gives the assistant lapses after 5 minutes if it is not used.

How its access is stored

  • The assistant holds an access token that lasts one hour, and a refresh token that lasts 60 days and is replaced by a new one each time it is used.
  • Sterodata stores only a SHA-256 hash of each token, code and client secret, never the value itself. A copy of Sterodata's database holds nothing that could be used to connect.

How its access ends

  • The member chooses Disconnect in Connected assistants, from the account icon in the top bar (see Your connected assistants).
  • An administrator chooses Disconnect beside it in Settings, General, Access, which lists the assistants of every member of the workspace. That is recorded with who did it.
  • Removing the member from a workspace ends what the assistant can reach there.

A disconnect takes effect at once: the connection's tokens are deleted, and the next request from the assistant is refused.

What an assistant reads on a member's behalf goes to the company that runs that assistant, under its terms (see Where your data is kept).

Last updated 29 October 2026