I would love to see the action of this rule to Remove All Collaborators .
Need:
I might not know who has been added as a collaborator, but when I move a task to a different workflow (department) I want to zero out all previous collaborators.
I would love to see the action of this rule to Remove All Collaborators .
Need:
I might not know who has been added as a collaborator, but when I move a task to a different workflow (department) I want to zero out all previous collaborators.
Hi @Getz_Pro, thanks for taking the time to provide this feedback! This Rule action would be a great addition ![]()
Hopefully this is something our Product team can add when making future updates to Rules. I’ll keep you posted.
I have the same need
Is there another way to do this?
I want this feature!!!
It doesn’t make sense to specify a specific collaborator in the add rule as not all tasks have the same collaborator.
Looking for it as well! They still do not provide this option.
My workaround is just to select all the people that need to be removed and update the rule with team changes ![]()
I’m using automation rules and I see there’s an option to “clear assignees”. This clears all assignees of a task. However, when I want to clear all collaborators, there’s no such option and I need to specify the collaborators by email address. The problem is that I don’t know yet who will collaborate on the task.
So, I suggest adding an action to clear all collaborators.
Hi @Ron_Gilad , welcome to the forum ![]()
I was fairly certain this already existed (at least in the past) but I guess not… I’ve moved your post into this existing thread that I found - I’ve also voted!
Btw, worth noting that ‘Add collaborators’ has the ‘+’ variable icon available but ‘Remove collaborators’ does not.
Also, just in case others may get confused, there is only ‘Clear assignee’ (not assignees), since there can only be one.
We desperately need this feature to streamline some of our processes —unfortunately it appears the “Remove Collaborators” rule hasn’t seen any love since it was intro’d back in 2021… ![]()