# Workflow Extension Enhancements for Advanced Dev Teams **URL:** \ **Category:** Ideas & Features\ **Created:** [December 24, 2020, 7:13am UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266 "2020-12-24T07:13:27Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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 8, 2021, 3:29pm UTC](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266/3 "2021-07-08T15:29:42Z")
I actually think it is sub-optimal to have the workflow states (or superstates) too strictly pre-defined, given that there could be just as many preferences as there are users 🙂 As an example, my preference for workflow states is sometimes Draft - Under Review - Reviewed - Approved - Obsolete and at other times is Pending - In Progress - Done. I would rather have the option to choose names/icons/colours and fallback values if no choices are made. And in a perfect world, each user could define their own workflow templates that can be chosen from for each type. There’s a related discussion here: > [@Allow custom colours (or shading) for workflow states](https://community.fibery.io/t/allow-custom-colours-or-shading-for-workflow-states/1442): > > In some cases I use the workflow states to indicate when an entity is progressing from ‘draft’, through ‘in review’ to ‘approved’ state. In these cases, it’s actually preferable that the ‘draft’ and ‘in review’ states are greyed out, and only the ‘approved’ state is shown in white (i.e. the opposite of the current functionality). Can we have the ability to customise the shading (or even the colours) of the workflow states. Also, although it is nice that there are little icons to represent the … And here: > [@Proper workflow: States, Transitions, etc](https://community.fibery.io/t/proper-workflow/1626): > > Workflow should consist of States and Transitions. States have Transitions. Transitions have Guards (conditions and permissions) and target States. Transitions can be triggered via a user action (e.g. button) if they have the required permission, or automatically if the condition formula is true. A Role has Permissions on an entity based on the State of the entity. Groups can have roles. Users can have roles, and they can belong to groups (inheriting the roles of the group). --- _[View the full topic](https://community.fibery.io/t/workflow-extension-enhancements-for-advanced-dev-teams/1266)._