# Assignee Specific Workflow

**URL:** <https://community.fibery.io/t/assignee-specific-workflow/2425>\
**Category:** Ideas & Features\
**Created:** [January 21, 2022, 3:35pm UTC](https://community.fibery.io/t/assignee-specific-workflow/2425 "2022-01-21T15:35:49Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [January 21, 2022, 7:38pm UTC](https://community.fibery.io/t/assignee-specific-workflow/2425/4 "2022-01-21T19:38:14Z")

</div>

If we had [Relationship properties](https://community.fibery.io/t/relationship-properties/887) then having multiple relations to users (each with their own workflow state) would be possible.  
The overall entity’s workflow state could then be defined using an aggregation formula.

---

_[View the full topic](https://community.fibery.io/t/assignee-specific-workflow/2425)._