Description
When assigning a new role to an existing user group, all other group settings are wiped - including app access, resource permissions, and workflow permissions. The same happens when removing a user from a group.
This means any permission change effectively requires rebuilding the group's entire configuration from scratch, which is both time-consuming and error-prone.
Steps to reproduce
Create a user group and configure app, resource, and workflow permissions
Change the group's assigned role (or remove a user from the group)
Observe that all previously configured permissions have been reset
Expected behavior
Changing a group's role or membership should only affect the targeted setting. All other permissions should remain intact.
Actual behavior
All group permissions (apps, resources, workflows) are reset to default.
Has anyone else run into this? Is there a known workaround?
Hey, thanks for bringing this up! Good news, the engineering team is already on it and we're aiming to push a fix to cloud by end of today. I'll post an update here once it's out!
The fix is out in Cloud version 3.360.0. Please give it another try and mark this comment as the solution if it works for you! Thank you! @leeharker-jta@TobiasOhlsson
Thanks for raising this — I’ve run into the same behavior when adjusting group roles. It’s definitely frustrating to have all app/resource/workflow permissions reset, since it means rebuilding the group from scratch each time.
Good to hear the engineering team is already working on a fix. Do you know if this patch will also apply to self‑hosted Retool instances, or just cloud deployments? Having clarity on rollout would help us plan around it.
In the meantime, I’ve started documenting group configurations before making changes so I can quickly re‑apply them if needed. Not ideal, but it saves some time until the fix is live.
Hi @web_star welcome to the Community! This has been fixed in cloud version 3.360.0. Are you self-hosted? If so, could you share which version you're currently on?
