# Card color based on single select option **URL:** \ **Category:** Ideas & Features\ **Created:** [January 10, 2025, 4:59pm UTC](https://community.fibery.io/t/card-color-based-on-single-select-option/8097 "2025-01-10T16:59:27Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [January 11, 2025, 8:02pm UTC](https://community.fibery.io/t/card-color-based-on-single-select-option/8097/3 "2025-01-11T20:02:29Z")
I hope that if this is considered for implementation (which I support), the team will try to make the solution a bit more general, or at least build it in such a way that it can be extended in the future more aspects of the UI can be controlled by data in databases. Here is what I was thinking: > [@Setting field/UI properties based on conditions](https://community.fibery.io/t/setting-field-ui-properties-based-on-conditions/5226): > > With the excitement and discussions around [[IN DEV] Entity-level permissions](https://community.fibery.io/t/in-dev-entity-level-permissions/2163) I have been thinking about field level permissions. I know that the Fibery team has said that field level permissions are not on the roadmap and unlikely in the near term (see below from recent posts as well as [Field-level permissions](https://community.fibery.io/t/field-level-permissions/2799) request): There has also been some discussion that maybe view permissions and multi entity views might make this not as a big deal: However, I was thinking that there might be another … I also hope that if we are going to have more dynamic colour coding, that ‘colour’ is also added as a field type with formula functions that could help you manipulate it (it is one of the things that Power Apps implement and is really useful). I think the UI for colour selection and even a colour field type already exists in fibery. It would just require it to become available to users. See also: > [@Colour Field Type](https://community.fibery.io/t/colour-field-type/3137): > > This might be a bit out there, but I was wondering if it makes sense to include a “Colour/Color” field type. I think if there is a possibility of [colouring cards](https://community.fibery.io/t/aproved-color-coding-of-entire-card-entity-not-just-bar-of-color/654) in the future, it might be good to be able to predefine the colours in some way and then have that value as the colour rather than having to explicitly define this in every view from scratch. I feel this enables long-term customization/consistency better. If this is something that has support, I would also suggest that it would be real… --- _[View the full topic](https://community.fibery.io/t/card-color-based-on-single-select-option/8097)._