What permissions are needed for Automation with a Scope of Multiple Projects

Question

Recently we have started to create more Automation rules that have a scope of Multiple Projects; we have discovered that only some people are able to edit these.
We have permission groups set up as admin though they do not necessarily have Global Admin for Automation. 
We feel like this may have changed recently, can any one confirm if this is the way it has always work or if this is an permissions update? 
Can any one also confirm the specific permissions needed to be able to update automation rules with multiple projects in the scope. 
Thank you

John Funk · Answer

What I did in those cases was to create a new Group which I called Automation Administrators. And then placed the people in that group.

Finally, I added that group the to the global Configuration in the drop down there. Still not sure if they would be able to administer multi-project rules even if a project admin in both.

Jeanna Knowles · Answer

Here is the very basic rule and the automation configuration. 
We have a Scrum master group setup under user mgt - admin rights are set. This group does not include site admin. The SM group has admin rights on both projects.

John Funk · Answer

Hi Jeanna,

I don't think anything has changed recently with the way global permissions are setup for automations. Can you share the Global Configuration that you have set?

Also, keep in mind that if you have a rule with multiple projects, a project administrator must have project admin permissions on ALL projects used by the rule, not just one or a few.