I’m struggling with a permission issue. As I have an action in one app that creates a user or updates the user if it exists. When trying to update an existing using a custom role, I get the error message “Missing required permissions to update account“.
I have scrolled through all permissions several times and can’t locate what I’m missing to get this to work.
Have you tried looking at the “Update User in Role” section? Believe this is something that the role must have as well, as this determines what kind of users the role is allowed to change. Usually when I am not allowed to update a user, this is the settings that prevents me from doing something as I have forgotten to update it.
My experience with these settings is that they are somewhat suboptimal, as you will manually need to toggle every role (also when you add new roles in the future), because if the user you try to update even have one single role that you haven’t given access to, you will get this error. In addition to this, there is a limitation as of now with these settings, since you are not allowed to update users with the roles of Owner, Maintainer or Developers from a custom role. This is because you are not allowed to toggle updating users in these roles in the permission settings.
This is not an issue when developing, as owners will always have permission to update all users in all roles.
Thanks for you reply, I believe you are correct. I checked of all roles (24) in the section “Update User in Role” and the error went away.
This should not be neccessary as this have to be maintained every time a new role is created. Specially for large solutions with many different roles / apps.
Completely agree! I have several services running to make sure that our users and their access roles are synced from our Azure/ Entra tenant, and since Service Accounts only can have custom roles, this is something that causes a lot of frustration, as I sometimes forget this with new roles, until the services in production suddenly starts throwing a lot of exceptions.
Would welcome a change - I posted a feature request about this issue earlier that hopefully can get some more traction now