# Limit # of assignees

**URL:** <https://community.fibery.io/t/limit-of-assignees/841>\
**Category:** Ideas & Features\
**Created:** [July 17, 2020, 7:55am UTC](https://community.fibery.io/t/limit-of-assignees/841 "2020-07-17T07:55:46Z")\
**Posts on this page:** 6\
**Page:** 1

<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:** [July 17, 2020, 7:55am UTC](https://community.fibery.io/t/limit-of-assignees/841/1 "2020-07-17T07:55:46Z")

</div>

I often want to ensure that an entity is assigned to one (and only one) person (e.g. a training record). Can we have the ability to constrain relationships (including min & max number of links)?  
Also, limiting links based on filters would be great e.g. so I can’t assign a Task entity to a User unless the User is a member of the category ‘engineer’.

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [July 17, 2020, 11:09pm UTC](https://community.fibery.io/t/limit-of-assignees/841/2 "2020-07-17T23:09:59Z")

</div>

This could be incredibly helpful for creating clean data hirearchies.

---

<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:** [July 18, 2020, 6:47am UTC](https://community.fibery.io/t/limit-of-assignees/841/3 "2020-07-18T06:47:08Z")

</div>

For what it’s worth, I realised after writing, that one can link Users either with the Assignment extension or just by using a normal entity Relationship. If limiting to max one user is desirable, the latter method (defining as many-to-one or one-to-one) is useful. The Assignment extension seems to be fixed as ‘many-to-many’.  
I think there’s still lots of value in being able to set constraints on relationships (min/max count or based on filters).

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [August 20, 2020, 4:01pm UTC](https://community.fibery.io/t/limit-of-assignees/841/4 "2020-08-20T16:01:22Z")

</div>

I didn’t know we could do that! 🤯

@Polina_Zenevich can we consider this an official solution? If so, we can mark this closed 😉

---

<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:** [August 20, 2020, 4:36pm UTC](https://community.fibery.io/t/limit-of-assignees/841/5 "2020-08-20T16:36:55Z")

</div>

@helloitse It’s worth noting that the Assignee field support auto notifications, whereas a simple relationship field to a User entity does not. I guess you need to decide what matters more: limiting to one user vs the user(s) getting notified when they are linked (assigned) to an entity…

---

<div class="post-metadata">

**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\
**Post date:** [August 21, 2020, 8:55am UTC](https://community.fibery.io/t/limit-of-assignees/841/6 "2020-08-21T08:55:22Z")

</div>

Chris is right in another answer 🙂  
Relation, I suppose, is a workaround only, as notifications are missed at all.  
We have a solution in our minds, but not sure about development terms 🦄