# Allow priority setting in automation rules **URL:** \ **Category:** Ideas & Features\ **Tags:** automations\ **Created:** [January 18, 2024, 11:03am UTC](https://community.fibery.io/t/allow-priority-setting-in-automation-rules/5707 "2024-01-18T11:03:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [January 18, 2024, 11:03am UTC](https://community.fibery.io/t/allow-priority-setting-in-automation-rules/5707/1 "2024-01-18T11:03:19Z")
I have a bunch of rules that need to follow a certain order or execution. Suggestion: It would be great to make rules entities, such that they can be better managed including their priorities and dependencies. ---
**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:** [January 18, 2024, 11:07am UTC](https://community.fibery.io/t/allow-priority-setting-in-automation-rules/5707/2 "2024-01-18T11:07:05Z")
> [@Yuri\_BC](#): > > It would be great to make rules entities, such that they can be better managed including their priorities and dependencies. I think there is next to no chance that automations will become entities in the traditional sense. However, being able to reorder automations in a space (and thereby control their relative priority) is something we may well get round to implementing. ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [January 18, 2024, 1:31pm UTC](https://community.fibery.io/t/allow-priority-setting-in-automation-rules/5707/3 "2024-01-18T13:31:43Z")
I’m now creating a RuleRun and RuleID database to faciliate dependencies and chaining of rules. Will share when a prototype is finished.