Giving the whole team "edit" permissions across dozens of projects

This is how I would approach this. I might be missing something here, so please correct me if I am wrong and remove the “Solution” status.

:one: Everyone in the Team to have full project access

If you create a Public project in the specific Team, all team members have edit access without the need to add them manually every time.

This will solve the below.

If they are NOT part of the team, you can set the Team setting to allow people to find and join the team independently.

:two: All Team members have by default, view-only access.

The first thought that come to mind is

  • Create a separate Team where you plan to put view-only projects
  • Allow everyone to join the team like above
  • Give the Team a clear identifying name (Team Name - View-Only)
  • Add to this Team only projects that you set as View-Only for the Team members
  • If a specific team member needs edit rights, you will add him to the project individually and give him edit rights


The above screenshot is from the Project specific Share settings

:bulb: Worth noting
→ There is a caveat. If you want all of your Team members to receive Project Updates or Project Messages notifications, they must be added (manually) to the project, and there is no bulk solution for that yet.

So, in this case, the internal team convention should be that the critical stakeholders for the project, those who need such project-level updates to be pushed to them, should be added (manually) by the project owner. This usually varies from project to project. Therefore this is usually the right approach; it is unlikely, in my experience, that all of the 15 team members will always have to receive for all 40 projects such updates.

I’d love to actually have the option “@ team name” in the Project Share module as we can do for assigning duplicates of a task and adding the entire team to the project like that.

→ In my experience, opening the Team up to the whole company reduces admin work (not needing, for instance, to add newcomers), but it might, of course, also have the side effect of “unwished” visitors. So you have to strike the balance there and decide what’s the priority: privacy vs reducing admin work.

Does it help?

1 Like