# Color Coding Rule Presets **URL:** \ **Category:** Ideas & Features\ **Created:** [June 22, 2022, 4:46pm UTC](https://community.fibery.io/t/color-coding-rule-presets/2991 "2022-06-22T16:46:17Z")\ **Posts on this page:** 3\ **Page:** 1
**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:** [June 22, 2022, 4:46pm UTC](https://community.fibery.io/t/color-coding-rule-presets/2991/1 "2022-06-22T16:46:17Z")
I have many different views where I want the same Color Coding Rules applied. Currently it is quite laborious to re-create the same Rules in every view – and if there is a change to the Rules, the change must also be manually applied to every View. Ideally we could create named Color Coding Rule “presets” that could be applied to different Views, but created/updated from a single location. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [April 2, 2025, 5:25pm UTC](https://community.fibery.io/t/color-coding-rule-presets/2991/2 "2025-04-02T17:25:42Z")
I’d love to be able to have this! My thoughts are to set it on the DB level. Where it is then persistent in search as well. (Like how anything in final state is gray.) Then maybe per view you could override / add to it? Would this solve the problem? Or do you have multiple presets per db you need in different views? ---
**Author:** ![Renato\_Carvalho](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/renato_carvalho/32/11001_2.png) [@Renato\_Carvalho](https://community.fibery.io/u/Renato_Carvalho)\ **Post date:** [April 3, 2025, 12:24am UTC](https://community.fibery.io/t/color-coding-rule-presets/2991/3 "2025-04-03T00:24:14Z")
Love the idea. I needed that so many times already.