Separate permission for buttons and workflows

[RonMakesSystems]

@Chr1sG

In which case, the button presser needs the permissions not only to press the button but to execute the actions which the button is expected to carry out.

Yes and no. Its adding a relation of the person’s own entity (which they have edit access to) to the entity. This is possible to do without edit access (not sure if a bug or not, but possible)

Button click can do actions user does not have permissions to do... I think

A button that sets a relation, where the user does not have any access to that relating database. The user is able to click and set that relation, since they have edit access to the source entity. Not sure if this is a bug, but its a bit weird as they then added an entity that shows as “Private entity”. Without the button click the user would not be able to add that relation because they do not see it exists in the dropdown.

@Chr1sG

This is very unlikely, since it is basically field-level permissions, which is not on the horizon at all.

Calling buttons a “Field” isn’t really true as to what they are though. You don’t have a different button value per entity, which is what you have in a field. I’m pretty sure (but correct me if im wrong) that you can’t query an entity and get the value of the buttons. Hence, while it gets a bit close to field level permissions, I don’t think its exactly what it is.