Calvin Correli hey thanks for your fast reponse - yes I think it should be pretty easy to set up. the use case is any admin can assign a task to any/all team members. So on my team is Jennifer, Kimber, Madison & I for example. So I can create a task and assign it to just Jennifer, OR i can assign a task to all three of them. Likewise, Madison can assign a task just to me, or she can assign it to both Jennifer and I, but not Kimber. Does that makes sense? So when I click "assign task" i can either assign to one person (as it is now) or I can assign to multiple people, selecting each one at a time.

josea crossley I understood that part.

My question is, who's supposed to actually do the thing?

All three, or just any one of them?

Calvin Correli do you mean who is supposed to do the task? All of them who it is assigned to. So for example, a task could be "prepare for team meeting" and it is assigned to everyone.

Or another one could be "prepare materials for Marine Mammals Workshop" and that could be assigned to everyone, because they all know their different pieces already. Does that make sense?

Calvin Correlianother example - "research retreat centers and bring what you find to our meeting on X date" could be assigned to everyone.

josea crossleyGot it. So it's really x number of separate but identical tasks, each with one assignee and tracking completion individually.

Calvin Correli actually no, it's one task for multiple people...like "prepare for team meeting" and everyone would be tagged/assigned.

and then we'd just check it off after the meeting if that makes sense... but also being able to duplicate tasks 3x or 5x would be helpful, yes! Like for example for team meetings I want to duplicate the last one but change the date for the next meeting. :)

josea crossley but it has to be done exactly once by each person.

If it's assigned to Annie, Beatrice, and Camilla, then they each have to do it, and we need to track completion status for each one separately, correct?

As opposed to any one of them can do it, and whether it's Annie, Beatrice, or Camilla that does it, as long as someone does it, we're good.

Eg. Send flowers to Josea, we don't need all three of Annie, Beatrice, and Camilla to do it. Once is enough.

But "read this important document", we need all three of them to do it, and then we need to track whether each one did it.

There's a world of difference between the two scenarios.

Logically, that would make the latter case would be three separate tasks, because each task is a thing to be done by a person.

Calvin Correli i see what you mean. I think for our purposes, just being able to duplicate a repeating task and assign one task to multiple people that can be checked by anyone once they're done would be sufficient, but I can see your point how it would also be cool if each person could indicate they had done the thing individually...

Calvin Correli Honestly I think it would be both that are needed, I can see a task being assigned to all VA's to do, but only need it done once, so whoever gets to it first marks it off then would be off the to-do list for everyone when it was completed, so I think it probably needs to be both ways if you are going to do it. This show to many check off when done like normal probably the easier one.