I am currently using the Free plan and considering upgrading to the Team plan. I’ve noticed that, in the Free plan, internal users seem to have permission to edit any application, almost as if they all have admin-level access. This feels unexpected and could pose governance risks.
My question is: In the Team plan, is it possible to restrict internal users so they cannot edit applications? Are there more granular access controls available (for example, view/use-only permissions without edit access)?
I believe it’s only available in the Business plan.
So if governance and edit restrictions are a real requirement, Business is the minimum plan recommended for teams with more granular permissions requirements.
Team plan: Organizations on a Team plan aren't able to specify individual user permissions, meaning everybody in the org is able to act as an editor. this is the same situation you're already experiencing, just with a staging environment added.
Business plan: You can create custom permission groups and configure them with the granularity of access you require. This is where you get true Use/Edit/Own distinctions per app or folder, and can lock down who can edit vs. just usingan app.
One workaround if you stay on Team: You can build UI-level permission simulation using current_user.email or group membership checks to hide or disable components. but this wont’ actually prevent someone from opening the editor. It's cosmetic and not a true access control - just viewing specific components as a viewer.
I understand, but the way Retool plans are presented can be a bit confusing.
If all internal users in the Team plan can edit applications, what is the practical difference between a builder and an internal user, given the pricing difference?
Builders are enabled users who built or edited an app or workflow during the billing cycle. Internal users are enabled users who didn't build or edit apps or workflows during the billing cycle. There's nothing preventing an internal user from becoming a builder by simply opening the editor.
It’s more like Business lets you actually govern these permissions.
