➕ Why add a member to a public project in a team?

In Asana, a team member will see any public project from the team. So why on earth would you need to add them as project members as well?

There are 6 possible reasons:

  • you want specific permissions for those members (everyone can edit, those members can only comment)

:fr: Version française

  • you want specific permissions for others (everyone Comment only, those members can edit)

  • you want a member to be the owner of the project

  • you want them to be notified of a new task (see project notification settings)

  • you want them to be notified of a new conversation (see project notification settings)

  • you want them to be notified of a project status update (see project notification settings)

  • you want guests to see each other (otherwise they don’t, here’s why)

Did I miss anything? Apart from those reasons, it is way easier to not add team members as project members, as they will see the project by default.

4 Likes

You nailed it!

Should your title read “why add a member to a public project in a team?” though?

The only exception being if you want someone to be a member of a private project, but that seems outside the scope of the post.

Thanks, I updated the project name. Indeed private projects are outside the scope.

I found another reason! If you want guests to see each others, otherwise they don’t.

1 Like

@Bastien_Siebman I could be wrong, but wouldn’t someone need to be a member of a project in order to receive the project status update within the Portfolio? I’ve had members of my team tell me they are in the portfolio, but they can’t see the status of a project they haven’t been added to.

Receiving and being able to see is different. Indeed to receive the status update you need to be a member of the project with the status notification setting turned on. However, to be allowed to see the status, you need to either be a member of the project, or a member of the team with the project being public.