Accept and activate Automations



I'm new to using PipeDrive Automations. Can someone at PipeDrive PLEASE explain to me, when I as an Admin create an automated workflow that all members of my team must use, why EVERY user has to go in and accept/activate EACH automation??? It isn't their choice whether they want to use it or not… it's our PROCESS that all users must use for consistency and an Admin should be able to activate the workflow for everyone. It's a huge waste of time that I have to send an email to each team member telling them step by step the name(s) of each automation, where to find them, and how to activate them. Waste of time that they have to go in and activate them. Waste of time that I have to follow up with the ones who didn't activate them. Please tell me why PipeDrive thinks it makes sense that an Admin should not be able to activate workflows/automations for their team. Thank you.
Answers
-
hi @JB04 there's a difference between date triggered and event triggered activities. event activities can be activated by every user. date triggers need to be activated by each user individually. thats just a very unfortunate way how date based automations work currently.
i do agree - @Manuel Oliveira its actually super inconvenient as many pipedrive users are very unfamiliar with workflow automations and an admin usually understands when date based workflows should trigger for all or specific users. this creates unnecessary friction and an additional task to chase users
0