Projects are usually tackled by teams rather than individuals, so when we revamped Projects we aimed to make it more team focused. That meant making it easier to see who’s a part of your team, whether they’re a colleague or a contractor. While this new team feature makes working together simpler, it didn’t have a lot of functionality around permissions - until now.
Before the new Team Permissions feature, you could theoretically add someone to your team of a certain type (historically known as a Contributor type), but they still wouldn’t be able to necessarily access the project everyone was working on - frustrating, we know. On the other hand, we didn’t want to give everyone permission to everything just because they were added to the team either.
So, rather than just giving everyone permission to everything, our engineering team has gone through and enabled a basic level of permission for all your team types. This means any staff added to a project team (or sale, or ticket team) can now access that project.
Right now, we’re working on the ability for admin users to take it a step further and configure the permission set for each team type. So, if you add someone to your team under a certain type (i.e. Project Managers), they’ll be able to have more project specific rights than someone who was added under a type like “Stakeholder”, for example. Essentially, this new Team Permissions feature will enable you to work as a team more freely, but with the control you need to feel confident and secure.
As always, if you’ve got any questions we’d love to help! Email our Support team and we’ll get you the answers you need.
