# Assignee Specific Workflow **URL:** \ **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:** 19
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [October 5, 2022, 3:15am UTC](https://community.fibery.io/t/assignee-specific-workflow/2425/19 "2022-10-05T03:15:44Z")
I just discovered this thread and you are actually talking about a few things I’ve mentioned before. First, re: your original request: > [@webinit](#): > > It’s basically allowing collaboration on a single entity with each user being able to have that entity at a different stage in the workflow. I’m not sure if you exactly mean what it sounds like, but “each user getting an entity in a stage of a workflow” where the entity passes along to a specific user upon one completing a previous stage is typical for process management apps like Pipefy, and I think that would be great to have more built out in Fibery as well, per some earlier requests I’ve had: > [@Workflow Extension Enhancements for Advanced Dev Teams](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266): > > Hi guys, I really like the fact that in this early phase of Fibery, we already have a concept of “Workflow”, thanks to the extension, that has some nice handling that you don’t see in other Nocode, where generally you have to use a single-select Property in a Field to get Workflow. In Fibery we have an element of Conditional Formatting already built in if you think about it with “done” items both “graying out” on boards, and showing as “strikethrough” when referenced - terrific work with those… > [@webinit](#): > > One user can have the thread as “Active” while another has it as “Done.” So simple, yet so powerful. Here though it sounds like you are simple requesting that each assignee can have their own state of an entity. I wanted to point this out as you mention the app Twist, and I have talked a lot about how some stuff in Twist - although not this feature - would be very useful around improving chats and comments, so I’m glad you mentioned it. Here I talk about how Twist handles well some of @mdubakov 's vision for conversations in Fibery: > [@Workflow Extension Enhancements for Advanced Dev Teams](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266): > > Hi guys, I really like the fact that in this early phase of Fibery, we already have a concept of “Workflow”, thanks to the extension, that has some nice handling that you don’t see in other Nocode, where generally you have to use a single-select Property in a Field to get Workflow. In Fibery we have an element of Conditional Formatting already built in if you think about it with “done” items both “graying out” on boards, and showing as “strikethrough” when referenced - terrific work with those… And a great feature of Twist I’ve requested is the ability to comment when you resolve or “close” an entity, it really gives context to what was actually done in an entity to finish it, instead of just clicking “done” and then leaving teammates guessing as to the final step to get something done: > [@Next iteration of Comments - Commenting when Resolving & assigning as tasks/reminders](https://community.fibery.io/t/next-iteration-of-comments-commenting-when-resolving-assigning-as-tasks-reminders/527): > > Hi once more, I wanted to make some suggestions for comments as you guys evolve them. This is coming mainly from my extended use of a ton of apps in the last several years, and none seem to be able to pull all the best methods for implementing comments all in one place. You guys have a good chance to do that now! Resolving Comments I’ve seen a great way to close out comment resolutions in some apps where they will prompt an extra comment around the “resolve” action. In most cases, you can… Hope you might find some of that useful, thanks! --- _[View the full topic](https://community.fibery.io/t/assignee-specific-workflow/2425)._