Adding people to an Asana task one at a time is tedious, and it is easy to forget someone who needed to be in the loop. Astogi's Team Collaborators integration adds every member of a team as a collaborator on a task in a single step, so the right people automatically follow the work. Asana has no button that adds a team to a task. You can @mention someone in a comment and they become a collaborator, and Asana does let you add a team as a collaborator on a goal, but on a task it is one person at a time. That is fine for a task or two. It stops being fine when the same group has to be on every task in a project, and someone always ends up out of the loop. This page covers how the integration decides who to add, who it deliberately leaves out, and what everyone gets once they are on the task.
Astogi's team collaborator user is added to the task as a collaborator, the same way you would add a person. That is the whole trigger. Asana sends a webhook when a task's followers change, Astogi checks that the person just added was its own team collaborator user, and a queued job takes over from there. Nothing runs in your browser and nobody has to press a button. The job reads the task back from Asana and looks at which projects it belongs to. For each project it asks Asana which team owns that project, then reads that team's membership list. Every member becomes a collaborator on the task. A task that sits in three projects gets the members of all three teams, with duplicates removed, so a person who is on two of those teams is added once rather than twice. Two kinds of team member are left out on purpose. A membership with no user behind it is skipped, and so is a member with limited access, which is how Asana marks guests and people who can only see what has been shared with them. The aim is to add the team, not to widen access to a task beyond what those people can already see. Adding the same team twice is safe. Webhook events for the same task that arrive within two minutes collapse into a single run, so a burst of follower changes does not add the same group over and over. The job only ever adds. It never removes a collaborator, changes the assignee, renames the task or moves it between sections, so switching it on cannot undo work someone else did on the task. Once people are collaborators they get the normal Asana notifications for that task: new comments, changes to the due date, completion, anything that happens to it. That is the point of the integration. The alternative most teams actually use is to @mention each teammate in a comment, one at a time, on every task where the whole group needs to follow along, and to remember to do it again on the next task. It is worth being clear about when not to use it. If your team is small and only a few tasks need everyone, mentioning people in a comment is fine and needs nothing installed. This integration earns its place when the same group has to be on task after task, when the group changes as people join and leave, or when a handover means a whole team has to see a task it did not create. The team is read from the project at the moment the task is triggered, not from a list you maintain inside Astogi. When someone joins the team in Asana they are included from the next task onward, and when someone leaves they stop being added. There is no second roster to keep in sync.
Team Collaborators adds members as collaborators (followers) on a task. Team Alias is about notifying a team about a task so they stay updated on progress.
Yes. Once added as collaborators they receive the normal Asana notifications for that task.
Not on a task. Asana lets you add a team as a collaborator on a goal, and an @mention in a comment adds that one person as a collaborator on a task. There is no built-in way to put a whole team on a task in one action, which is the gap this fills.
The team that owns the project the task is in. If the task is in more than one project, it uses every team that owns one of them and removes duplicates, so each person is added once.
Team members with limited access, which is how Asana marks guests and people who can only see what was shared with them, and any membership that has no user behind it. The integration adds the team without widening what those people can see.
Nothing to maintain. The membership list is read from Asana each time the integration runs, so a new team member is included on the next task and someone who left stops being added.
No. It only adds followers through Asana's own add followers endpoint. It does not remove anyone, change the assignee, rename the task or move it between sections.
Events for the same task within two minutes collapse into one run, so a burst of follower changes does not add the group repeatedly.
You can try Astogi for free on your first project. Need more? Get more for just €29/month.
If you have any question or need support, feel free to contact us, our team is always happy to come up with the best solutions to your problems.
Overvoorde 49,
Amsterdam, The Netherlands
Made with ❤️ in the Netherlands
©Astogi 2026
Registered at the
Chamber of Commerce #42271509