Comment 2 for bug 1760856

This still occurs in 3.10 as well. It will also give the false success message if you try to grant a permission at a depth that you do not have the permissions to grant. For example, using a profile group that can assign a permission at system level, after I assigned the permission at the consortium level and clicked Save, I received the "User Successfully Modified" message, but the permission was only assigned at the system level. So it's still acting as it should, but more detailed messages would be helpful. (Wondering if it may be a viable wishlist bug to gray out any depths that aren't able to be applied.)