# Separate permission for buttons and workflows

**URL:** <https://community.fibery.io/t/separate-permission-for-buttons-and-workflows/8350>\
**Category:** Ideas & Features\
**Tags:** permissions\
**Created:** [February 27, 2025, 2:10pm UTC](https://community.fibery.io/t/separate-permission-for-buttons-and-workflows/8350 "2025-02-27T14:10:26Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 5, 2025, 12:57pm UTC](https://community.fibery.io/t/separate-permission-for-buttons-and-workflows/8350/9 "2025-09-05T12:57:55Z")

</div>

> [@RonMakesSystems](#):
>
> 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)

Linking entities requires edit rights for at least one end, so it might be possible for someone to click Approve on a Task they don’t have edit rights for if the action is to link the User entity to the Task.  
But in general, a lot of the actions require edit access for the item on which the button lives.

> [@RonMakesSystems](#):
>
> 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.

Indeed, button’s don’t have values, so can’t be queried, but my point is, the idea of a capability called “Can Edit this entity” is something that can be applied to all entities in the workspace, no matter what fields the database has.  
But the idea of a capability called “Can press the ‘Approve’ button” and a separate capability called “Can edit the ‘Toggle send to client’ button” implies that capabilities are not conceptually universal across all dbs, but are dependent upon which buttons exist in any given database.  
In that sense, it would mean controlling permissions as a function of what buttons (= ‘fields’) a database has (aka field-level permissions).

---

_[View the full topic](https://community.fibery.io/t/separate-permission-for-buttons-and-workflows/8350)._