Reviewing finance app access
Sarah Chen, IT manager at Acme Ltd, asked who could edit the finance apps. Memtro listed the permission groups with edit or own access to apps, and the members of each.
Who has access to what in Retool, and which approvals are waiting?
Retool shows you your organisation's users and pending invites, and permission groups with their members and access levels. It reads apps, workflows with their schedules, workflow runs, human-in-the-loop user tasks, resources and usage. When asked and granted, it can invite or create a user, revoke an invite, or disable a user. It can also create or delete groups and change their members. It can submit, reassign or cancel a user task, create a folder, and delete an app or workflow. Only an organisation admin on a Business or Enterprise plan can create the token.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Retool tool, reads what it needs, and answers with the source cited.
These tools change something in Retool. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Retool is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which user tasks are waiting for approval?
Who has admin access in Retool?
Which workflows run on a schedule?
How many active users did we have last month?
Who is in the Finance group?
Sarah Chen, IT manager at Acme Ltd, asked who could edit the finance apps. Memtro listed the permission groups with edit or own access to apps, and the members of each.
Tom Reilly, IT lead at Northwind, asked Memtro to disable a contractor who had left. With the action granted, Memtro disabled the user, so they could no longer sign in or use any app.
The teams that lean on Retool most, a question each of them asks, and what they connect beside it.
A record in Retool is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Retool open Settings, then Retool API, and create a token named Memtro. Choose the read scopes, plus write scopes only for the actions you want.
In Memtro open Connections → Retool and fill in Retool host with the host name only, then the API token.
An administrator grants the user, group and delete actions by name to the teams that may use them.
Ask: which user tasks are waiting for approval?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Retool tools are the same everywhere.
Only when you ask, and only what it has been granted: invite a person to the Retool organisation, optionally into groups (uses a seat once claimed); create a Retool user; revoke a pending invite; disable a user so they can no longer sign in; create a permission group; delete a permission group; add users to a group, or make them group admins; remove a user from a group; submit a workflow's user task (the workflow resumes); reassign a user task to other users or groups; cancel a user task; create a folder; delete an app; permanently delete a workflow. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Retool host and API token. In Retool open Settings, then Retool API, and create a token named Memtro. Choose the read scopes, plus write scopes only for the actions you want.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time