# \[REJECTED\] Associations locking and unlocking

**URL:** <https://community.fibery.io/t/rejected-associations-locking-and-unlocking/1536>\
**Category:** Ideas & Features\
**Created:** [April 7, 2021, 6:55pm UTC](https://community.fibery.io/t/rejected-associations-locking-and-unlocking/1536 "2021-04-07T18:55:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Ricciardi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ricciardi/32/1647_2.png) [@Michael\_Ricciardi](https://community.fibery.io/u/Michael_Ricciardi)\
**Post date:** [April 7, 2021, 6:55pm UTC](https://community.fibery.io/t/rejected-associations-locking-and-unlocking/1536/1 "2021-04-07T18:55:37Z")

</div>

When I am adding stories to an epic, i would like the ability to lock associations so I don’t accidentally redirect an existing association

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [April 9, 2021, 8:02am UTC](https://community.fibery.io/t/rejected-associations-locking-and-unlocking/1536/2 "2021-04-09T08:02:40Z")

</div>

It’s hard to do since Fibery has no field-level permissions (and we are not going to implement them).

---

<div class="post-metadata">

**Author:** ![Michael\_Ricciardi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ricciardi/32/1647_2.png) [@Michael\_Ricciardi](https://community.fibery.io/u/Michael_Ricciardi)\
**Post date:** [April 9, 2021, 4:55pm UTC](https://community.fibery.io/t/rejected-associations-locking-and-unlocking/1536/3 "2021-04-09T16:55:20Z")

</div>

Then can we toggle off the ability to re-associate an exiting type when creating a new occurrence of same type?

---

<div class="post-metadata">

**Author:** ![Michael\_Ricciardi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ricciardi/32/1647_2.png) [@Michael\_Ricciardi](https://community.fibery.io/u/Michael_Ricciardi)\
**Post date:** [April 21, 2021, 1:58pm UTC](https://community.fibery.io/t/rejected-associations-locking-and-unlocking/1536/4 "2021-04-21T13:58:58Z")

</div>

We need something that prevents the disconnect of established associations. This is an reoccurring issue, tasks and stories and loosing their hierarchy connection, by accident, from our devs/engineers. if it is not possible to lock, what a bout a prompt on established connections when an object can have only one association?

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [September 16, 2021, 6:50pm UTC](https://community.fibery.io/t/rejected-associations-locking-and-unlocking/1536/5 "2021-09-16T18:50:04Z")

</div>

What you can do right now is define a Rule that will trigger when a relation (or any field) is changed, that will cause an error message to be displayed in certain conditions.

You can also mark a field as “read-only” (via the API), which will prevent it from being changed from the UI. But that’s probably only useful for situations where the field will be maintained from scripts/API.