We’re running into issues with editing each other’s rules for third party integrations. I understand the security concern of allowing someone else to affect the third party integration except it seems strange that I could create a rule, add a slack integration, then go on PTO and leave everyone else to deal with my mess.
I guess the rule could be disabled in that case?
I also find it odd that the solution is:
- Centralize rule ownership: Setting up a shared service account, such as automations@yourcompany.com, to create and manage all automation rules can help ensure that they’re not tied to a single person. This gives your team more consistent access and avoids roadblocks if someone is unavailable.
- Coordinate rule updates through the owner: If the rule is already created and tied to someone’s account, any updates will need to go through that user. Having a clear process for requesting changes can help avoid confusion or delays.
We would spend extra money to do 1. for a workaround and not even a product solution.
If we’re doing 1. shouldn’t we just have 1 account and then use labels for team member tasks or even create rules the then give each team member a project and all use the same account? I’m sure this violates the TOS; just giving an example of how this approach could be abused by the end user.