# \[DONE\] Entity-level permissions

**URL:** <https://community.fibery.io/t/done-entity-level-permissions/2163>\
**Category:** Ideas & Features\
**Tags:** permissions, sharing\
**Created:** [October 29, 2021, 2:32pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163 "2021-10-29T14:32:55Z")\
**Posts on this page:** 1\
**Showing post:** 105

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [December 23, 2023, 7:43pm UTC](https://community.fibery.io/t/done-entity-level-permissions/2163/105 "2023-12-23T19:43:52Z")

</div>

Related:

> [@Exploring solutions for a controlled relationship structure](https://community.fibery.io/t/exploring-solutions-for-a-controlled-relationship-structure/5577/3):
>
> I don’t think field level permissions is actually the solution to this. A relationship is actually two fields (one at each end) so it begs the question which field governs the permissions. I think a more plausible solution is that the capabilities available in custom access templates get expanded so that the current ‘Edit’ capability (which encompasses the ability to link/unlink items) is split into a limited ‘Edit’ and a separate ‘Link/Unlink’ capability. No idea of if/when this will happen t…

---

_[View the full topic](https://community.fibery.io/t/done-entity-level-permissions/2163)._