> So, if the user does not have permission to edit a resource, the edit button will not be displayed. This results in a much better UX, because it is obvious to

> So, if the user does not have permission to edit a resource, the edit button will not be displayed. This results in a much better UX, because it is obvious to the operator what actions are available based on their permissions at the time. This results in much worse UX, as the user is oblivious to what actions are unavailable due to their permissions! Back a little over 20 years ago, we would just grey out the button, to indicate that it was "disabled". (I'd also add that I think hovering over such UI ought to offer an explanation as to why that particular action is unavailable, and possibly, what steps to take to effect it.) And it can be downright confusing if someone is giving instructions: are you misinterpreting their instructions, are their instruction wrong, or is it that the software is hiding the UI from you?