Users destroy automations without realising it

🔧 Bugs & Issues
1

It was only part of a discussion, but I want to raise it as an issue. Especially in a larger installation, where many people are involved and have different access rights, this issue causes support effort.

People have rights to admin applications and automations in their own workspaces. However, some automations are connected to apps they don’t have access to. But there is no warning or locking mechanism.

Editing the automation shouldn’t be allowed to users, which don’t have all necessary rights for all involved apps. Currently this breaks the automation, which we think is a bug. Especially as its not obvious - saving appears to be working, but automations start to fail from now.

2 Likes
2

You know, I just ran into this internally yesterday. We have two different seats. One for doing all of the automation and then I have my regular seat. Sometimes I save over automations and accidentally break them while using my personal account.

I believe that the automation holds on to the permissions from the last user who saves.

I’m not sure of the best way to handle this but I figured it might be worth sharing in hopes it helps to move us closer to a solution.

1 Like