How can I stop the “rule owner” from being added as a project member to projects created by the rule? I.e. projects converted from a task to a project triggered by a form.
I would like the task assignee to become the owner, and the collaborators to become project members, but I would not like the rule owner to be attached to the new projects.
Thanks in advance!
@Rochelle_Hunter1 - I actually didn’t know this was an issue. However, I tested just now and can confirm that this is exactly how it works, for better or for worse.
What happens:
Other than a custom 3rd-party automation, I can’t think of any workaround.
Just wanted to let you know.
Also, how can I automate adding an additional “project admin” via this rule based on other conditions (not based on them being the rule owner).
@Rochelle_Hunter1 - to my knowledge, you can’t do this directly. However, you can pre-add fixed list of people as project admins using the project template. Or, you can set your template so that anyone who has access is a project admin (not recommended).
But, you can’t dynamically add project admins, except via 3rd party automations, like Zapier or Make.com.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.