# Global picklist values for different types

**URL:** <https://community.fibery.io/t/global-picklist-values-for-different-types/1971>\
**Category:** Get Help\
**Created:** [September 2, 2021, 2:10pm UTC](https://community.fibery.io/t/global-picklist-values-for-different-types/1971 "2021-09-02T14:10:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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 2, 2021, 2:23pm UTC](https://community.fibery.io/t/global-picklist-values-for-different-types/1971/2 "2021-09-02T14:23:34Z")

</div>

Related:

> [@Reusing Single- and Multi-Select options?](https://community.fibery.io/t/reusing-single-and-multi-select-options/1952/8):
>
> Actually, my original request was more about laziness(!) in that I thought it would be nice to be able to define a workflow once and make it available for multiple types simultaneously, but I can see why what i wrote can be thought of as large set of cases, including this one. Yeah, i get that. I think i might have even asked in the past if there was a technical reason why a single- or muli-select couldn’t be ‘owned’ by more than one type (and the answer was, yes, there is). There is actual…

---

_[View the full topic](https://community.fibery.io/t/global-picklist-values-for-different-types/1971)._
