I would look into creating a specific ‘offline’ entity that is connected to each account. That way you can retrieve the account over asscociation in a nanoflow and after this retrieve the specific userroles of that user.
Found a possible workaround.
Created a separate UserRole entity with association to Account 1 – *, and settedup Before Commit Action in microflow on saving account entity, this action will take System.UserRole and store its name in to custom UserRole object.
Looking to solve the same problem, anybody have any suggestions for best practices? Alternatively, is there a way to set a default role when a new account is created? I’m testing out adding an after create microflow on the Account entity that adds the user role desired.