Permissions and safety
Whose rights a connected assistant uses, which of its requests only read, which delete or reach outside the workspace, and how its sign-in and tokens work.
This page is for the people who approve tools for a business: what a connected assistant can reach, how Sterodata checks each request, and how the connection is secured.
It acts only as the person who connected it
- Every request is made as the signed-in person who allowed the connection, through the same routes and checks as the app's screens: the same roles, the same table and field permissions, the same validation. Sterodata adds no permission of its own for assistants, and grants them nothing extra.
- It reaches the workspaces that person is a member of, decided again on every request. Remove someone from a workspace and their assistant loses it too.
- Fields hidden from the person are hidden from the assistant.
- There is one level of access: what the person can do. A read-only connection is not offered.
- A refusal comes back with the app's own reason, and the assistant is told not to retry a request the person is not permitted to make.
Which requests only read, and which change things
Every tool Sterodata offers carries marks that assistants read to decide when to ask you before acting: read-only for tools that only read, destructive for tools that delete or overwrite, and open world for tools that reach beyond the workspace.
| Marked | Tools for |
|---|---|
| Read-only | Listing workspaces; describing a workspace, a table, a view or a summary; answering questions from records; listing pages, reading a page's draft and a dashboard's figures; listing apps; checking an import's or a file download's progress. They never change data. |
| Destructive | Changing records; deleting records; changing or deleting a field; deleting an empty table; changing or deleting a view or a summary; changing a page's draft; unpublishing or deleting a page; downloading files into a field. |
| Open world | Publishing a page (it gives out an address others can open); deleting a page (its address stops working); downloading files from web addresses. |
| None of these | Creating a table, adding a field, adding records, importing CSV, creating a view, creating a page, installing an app, creating a workspace, changing a workspace's locale or exchange rates. |
Sterodata marks the tools; the assistant decides whether to ask you first. Whether it asks before a destructive or open-world action depends on the assistant and its settings. Sterodata does not ask a second time.
Some things an assistant cannot do at all, such as deleting a table that holds rows or changing who can reach what. See What an assistant cannot do.
Sign-in and tokens
- The person signs in on Sterodata's own sign-in page. The assistant never sees their password.
- The connection uses OAuth 2.1 with PKCE. The tokens it gets are issued for
https://api.sterodata.com/mcponly and are accepted nowhere else. - The consent request lasts 15 minutes. An access token lasts one hour. A refresh token lasts 60 days and can be used once; each use gives a new one.
- Sterodata stores only a SHA-256 hash of each token and code, never the token itself.
- Disconnecting deletes the connection's tokens at once: its next request is refused. See Disconnect an assistant.
What leaves Sterodata
What a tool answers is sent to the assistant that asked: the rows, figures and definitions it read. From there it is handled under your assistant provider's terms. Sterodata does not receive your conversation with the assistant, only its requests. One answer holds at most 60,000 characters.
Where Sterodata keeps your data, and how, is in Security. See also the privacy policy.
Last updated 29 October 2026