Suggested improvements

• Ability to Save/disable a new automation Rule without being able to turn it on first
• We should background save edits in draft mode - right now any edit progress is lost if the session expires or the browser window is refreshed.
• If a rule save fails we should ensure it is very clear that is the case. At the moment the notification can easily be missed, and the “dirty” state doesn’t seem to warn the user if they navigate away. This can cause customers to lose updates if they don’t notice that the new rule creation has failed.

Global Admins can be rightfully nervy that project admins make unwanted changes to rules that could impact on server performance.

For this reason, many limit automation rules to Global admins only.

To solve this, we released permissions for project automation.
https://blog.codebarrel.io/permissions-for-project-automation-7e17c5c8cbb3

We could, however, go one better. It would be great if one could change a rule for a project and then just have an admin press one button to publish it. This is something Autoblocks have released and looks to be a handy feature.

Could also just enable permissions for certain classes of rules, like those that are scoped only to 1 project and that do asynchronous triggering for minimal performance impact.

_________

Would be good to be able to version changes to automation rules and be able to look at the history of a rule to see who changed what exactly.

Perhaps allow users to config a git repo and use that for history.