Hi there, I would like to create different roles in my app. Each role grants read access to all objects. The role determines which groups, including associated categories, the person has write access to. I am currently encountering the problem that the buttons for editing objects are displayed even if the person does not have write access, but only read access. This means that the visibility 'Show the action button for applicable roles' is not sufficient. Here's an example: I have "GroupA" and "GroupB". Max is allowed to write on GroupA, but should not be allowed to edit GroupB. Anna, on the other hand, is allowed to edit GroupB, but not GroupA. The same behavior for the categories. You can see in the Screenshot below that Max can see all buttons, even if he has no write access to the belonging objects. Max view: desired view: What I could do: I can limit the buttons for the group using visibility. However, this no longer works for the categories (error "Retrieving over association is not allowed here"). My only alternative seems to be placing the button in a DataView with a microflow checking write permissions, then limiting visibility based on the result. Because I have this issue in many places and with many different entities, I prefer not to implement this solution using microflows+dataviews. Do you have any suggestions for a more efficient solution? Thanks in advance! Best regards, Simone