If it is about user roles that are not allowed to execute an action, it would be better (from a security standpoint) to not make it invisible via a visibility constraint. You should make the microflow behind that button only executable for defined roles. The button will disappear for all other roles.
If the administrator can see both rows that means the administrator user role has the “administrator” module role and the “user” module role. The way that you are building your page then a user role should either have either “administrator” or “user” as a module role, not both.
Also, the same conditional visibility settings exist on the buttons. If you open the buttons properties, there is a visibility section where you can configure the button to show based on certain module roles.
Hope this helps!
The top buttons is the container way
and bottom one is the grid layout way or button way
If you want to display buttons from different contains in one line then you should add the ‘display: inline-block;’ to the container css.
This will move the containers inline and the user will see all the buttons on one line, even if they have different roles
Hope this helps.
By the way: Shouldn’t Mendix show/hide the Save and Cancel buttons similar to a microflow-button: only show when the user’s role has entity write-access?
That would make this question’s scenario a lot simpeler.
The reason why the administrator was considered a user is because in the screen below the user choice was checked