What would Retool add to an order follow-up queue?

Retool can display orders from your database or an API and give staff a place to take specific actions. The connected system still determines what a request can read or change.

Imagine a teammate wants to find orders that need a reply. Build a table with an order label and a status. Start with a connection that can only read those fields. Retool calls a configured connection a resource. Ask the resource for the records the screen needs.

For an approved status change, use a separate connection or a request to your app’s own service that can enforce the allowed update. If the app normally checks who can change an order, a direct database edit may skip that check. Give the underlying connection only the access the job needs.

Who can open the queue and make changes?

A published app has a link. Use Retool’s access settings and the permissions on the data connection to decide who can open the app and what they can do.

Separate the people who use the queue from the people who can edit the screen or its connections. Retool documents custom permission groups on Business and Enterprise. Its resource guide says users on Free and Team can use all resources. Keep sensitive connections out of a shared Free or Team setup if that access is wider than you want.

Published apps in the current app builder can be shared with authorized external users. Check the plan and sign-in requirements if you want to build a separate customer tool. The current app builder does not offer public links or external embedding. Classic apps have a different set of sharing options.

How can you rehearse a read-only view and one approved edit?

Sketch two staff views on paper with fictional orders. Decide which requests each person should be able to make.

Give the reader a list
Draw orders P-14 and P-15 with the status Needs follow-up. Write the two fields a read-only teammate needs to see. They should have no way to change a status.
Approve one action
Have a fictional supervisor approve setting P-14 to Ready to contact. Write down the exact permitted change and whether the app’s existing service should enforce it. Leave P-15 as it was.
Check the boundary
Ask what should happen if the read-only teammate tries to make the same request without the screen. It should be denied. The rehearsal does not connect a database, change an order, or send a message.

What does Retool count when it bills your team?

The public Free plan lists up to five users. On paid user-based plans, Retool uses different monthly rates for people who build or edit an app or workflow and people who only use them.

A teammate with edit permission can be billed as a user in a cycle when they make no edits. The applicable rate can change if they build during that cycle. Check the plan separately for external users. Retool lists self-hosted deployment under Enterprise. If you choose a self-managed deployment, budget for its infrastructure and updates as well as the plan.

What can you keep if you change tools?

Retool documents Git source control for current apps on Enterprise, and different export options for Classic apps. The current app builder does not export a standalone app for running outside Retool.

A Classic app can be downloaded as JSON or a Toolscript archive. That download includes its queries and components, with data connections set up separately. Keep a separate record of the app’s data sources, required permissions and operational records. When moving a dashboard, check both the screen and whether its read and update rules still work.