# Exploring solutions for a controlled relationship structure

**URL:** <https://community.fibery.io/t/exploring-solutions-for-a-controlled-relationship-structure/5577>\
**Category:** Get Help\
**Created:** [December 22, 2023, 8:21pm UTC](https://community.fibery.io/t/exploring-solutions-for-a-controlled-relationship-structure/5577 "2023-12-22T20:21:58Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [December 22, 2023, 11:13pm UTC](https://community.fibery.io/t/exploring-solutions-for-a-controlled-relationship-structure/5577/3 "2023-12-22T23:13:13Z")

</div>

I don’t think field level permissions is the correct 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 though.

---

_[View the full topic](https://community.fibery.io/t/exploring-solutions-for-a-controlled-relationship-structure/5577)._