# Allow automations/rules to apply to multiple databases

**URL:** <https://community.fibery.io/t/allow-automations-rules-to-apply-to-multiple-databases/4827>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [July 21, 2023, 8:01pm UTC](https://community.fibery.io/t/allow-automations-rules-to-apply-to-multiple-databases/4827 "2023-07-21T20:01:08Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [October 19, 2023, 4:08pm UTC](https://community.fibery.io/t/allow-automations-rules-to-apply-to-multiple-databases/4827/6 "2023-10-19T16:08:16Z")

</div>

I can understand the desire for automations that affect multiple DBs but in practice it’s probably too complex to implement for the modest gain in capability. However I think at least some of the core desires here could be met more simply while providing other utility with implementation of feature requests like:  
[Duplicate automations](https://community.fibery.io/t/duplicate-automations/3205) (if it allowed duplicating to other DBs)  
and especially:  
[Centralized script management for Workspace](https://community.fibery.io/t/centralized-script-management-for-workspace/3039) if it could be made to encompass Automations in a sort of library. There is more discussion of all this in that thread.

---

_[View the full topic](https://community.fibery.io/t/allow-automations-rules-to-apply-to-multiple-databases/4827)._