Current plan level: Business
Monthly/Annual: Monthly
Version of Retool (if self-hosted):
Question / Description:
Hi everyone,
What is the recommended way to configure the All Users group so that a user can access and use a published application without being able to edit it or modify other resources?
Since every registered user is automatically added to this group, I’m unsure which permissions it should have and which should be granted through a separate group.
The intended setup is for a user to:
Open and use a specific published app through its URL.
Have no access to the app editor.
Be unable to directly access or modify databases, workflows, or other resources outside the app.
Have no access to other apps unless explicitly granted.
The app should still be able to run the queries and workflows needed for its functionality.
How should I configure All Users, and what additional app and resource permissions should I assign to achieve this?
On a Cloud Business org, how should the default "All Users" group be configured so that users can only open and use a specific published app via its URL — with no app-editor access and no direct access to databases, workflows, or other apps — while the app itself can still run its queries and workflows?
AI Response
Because access in Retool is additive and users always receive the most permissive level across all sources, keep the "All Users" group at the lowest possible access (remove its app/resource permissions and leave 'View account details' and similar options unchecked). Then create a dedicated permission group granting only 'Use' access to the specific app(s) the users need, and add those users to it. Also remove those users from the default Viewers/Editors/Admin groups so nothing grants broader access. With Use-only access, the app runs its queries and workflows normally, but users get no editor access and are blocked from opening resources directly or seeing apps they haven't been granted.
Sources
End user resource access
A solved thread where Retool staff lay out the exact recipe: strip permissions from the 'All Users' group, remove end users from default groups, and create a Use-only group scoped to the needed app(s) and resources. Share apps with users and groups | Retool Docs
Documents that access is additive and users receive the most permissive level across all sources, explaining why the 'All Users' group must be kept minimal to avoid overriding a narrower Use-only group.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a , , or . Or by marking this post as the "Solution"! Let us know if you have any feedback here.
Our Support team sent you a couple of follow-up emails recently, so it’s worth checking your inbox (and spam folder) when you get a chance. Happy to help here too if you still need a hand!