I find that the "End Users" vs standard user management feature is not well-developed. In my opinion, being an end-user should be decided by the manager who shares limited access rights, and not by a system. As it stands, it is almost impossible to use this feature, thus requiring higher costs.
Hi,
I agree with you.
I'm on the Team plan and the end-user feature (at 5$ a month) is not a thing.
I've been said by the Support that the end-user feature is not available for Team, but for Business and Entreprise.
I'm not sure what is true and what's not.
Yes, It indeed have end-user in both Team and Business plan, but in team you can't set the access right to it. This means end-user in team still has access to edit the apps.
If you don't use that end-user to edit the app in specified charge period, it will regards as end-user, otherwise standard user. If you use many end-users to edit your apps. these users will charge as standard users.
I also have feedback my confusion about these too before.
Totally agree, I just switched to team plan (i was using the free plan before for my mockup). Honestly it does not make any sens to not be able to setup end-user as use only profil...
Hi everyone! Thank you for taking the time to chime in, and I definitely understand the confusion. Our approach to pricing is decoupled from access controls and is based on users' usage. In other words, "standard users" and "end users" are pricing and billing concepts, rather than permissions concepts.
So, for example, a user who has editor permissions in Retool, but didn't build in Retool in a given month, would only be charged as an "end user" in that month. You can read more about our approach to billing in our billing docs.
On the Business and Enterprise plans, customers can use permission groups to control who has the ability to edit Retool apps and workflows. You can learn more about permission groups in our permission docs.
We do track every point of feedback, so please feel free to continue sharing your thoughts and questions!
Hello,
I'm well-versed in Retool, but I had my uncertainties. Now that I'm on the Business plan, I've begun experimenting with permissions. I find the terminology a bit perplexing.
I believe it would be beneficial to have a distinct End-user group (without viewing access to Workflows, Resources, and Database) and a separate Viewer group (with viewing rights). Naturally, we would also have the Admin and Editor roles.
I grasp the idea behind the Viewer role—it's more cost-effective for those not involved in development edits. However, the primary notion showcased in the Portal is the End-user without viewing permissions. This isn't available by default.
I suggest adjusting the pricing structure accordingly. For instance, under the Business plan:
- Admin/Editor: $50/month
- Viewer: $15/month
- End-user: $5/month
At $15/month per end-user (taking the pharmacist in the given example), it becomes challenging to establish a feasible business model for the suggested product. This leaves little to no profit margin for startups. Given that startups appear to be a key demographic for Retool, this is concerning.
1 Like
100% agree with MicExpert
Thank you - I’ve shared your feedback with our team working on pricing. As a quick note, just in case it’s helpful, have you looked into our Startup credits? We actually created this program to address your last point!