# Global single and multi-select field options

**URL:** <https://community.fibery.io/t/global-single-and-multi-select-field-options/2779>\
**Category:** Ideas & Features\
**Created:** [May 9, 2022, 8:57pm UTC](https://community.fibery.io/t/global-single-and-multi-select-field-options/2779 "2022-05-09T20:57:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\
**Post date:** [May 12, 2022, 12:23pm UTC](https://community.fibery.io/t/global-single-and-multi-select-field-options/2779/3 "2022-05-12T12:23:21Z")

</div>

Yeah this works very well, but there are two problem with this approach:

**1)** Its unintuitive - only seasoned Fibery users know that multi-select fields are secretly hidden mini-databases.

Maybe having a normally off checkbox on the single/multi-select field creation modal for something like “Make these options available globally (in other databases)” which automatically does what you suggest, but creates them as “hidden” space/databases. Something like this:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/65f321d28e226d9dadd0afba00a077c2918e0aa0.png)

**2)** It creates a bit of clutter - having to create several spaces/databases just to contain a few entities used as global single/multi-selects creates for messy relationships and clutters up the UI. Because then you have one or more space/databases which really don’t do anything more than hold a few entities.

Happy birthday by the way! 🎉

---

_[View the full topic](https://community.fibery.io/t/global-single-and-multi-select-field-options/2779)._