+1 specifically for adding access to button presses in access templates. The ideal would be able set which buttons they can press and which they don’t.
For example, I dont want them to be able edit the entity, but I do want them to be able to press “Approve”.
But the same entity might have another button for “Toggle send to client”. I don’t want them to be able to press that and remove their own access, for example.
Regarding the frustration with button access vs edit access, this is just up to the Architect to build properly. Those who are configuring custom access are already far into learning Fibery.