Cover: original AI-generated concept illustration with a fictional interface, not a working product screenshot.
Consider a document someone can read but cannot edit. A disabled Edit button tells them there is a restriction, but not whether they opened the wrong account, need a different role, or are looking at a locked document.
A generic "Ask your administrator" message leaves another question: which administrator? Naming an owner could help, provided the viewer is allowed to see that information. An access-request button could help too, but only if the request has a real destination and the interface explains what happens next.
For this case, would you keep Edit visible with a short reason, replace it with "Request editing access," or hide it and explain permissions elsewhere?
The interesting boundary is how much context to provide without exposing membership or resource details the viewer should not receive. What would your minimum useful explanation contain for an authenticated user who already has permission to view this particular document?