Hi All,
I noticed that when a person is member of a team with project admin rights on a certain project (and the project is shared with the team), those users still see a “Join” button in the top of the project and in the share menu. Even though they have project admin rights. It only seems to disappear when the actual person is added to the project (instead of through the team). Is this expected behaviour? Or am I missing something? Is there a difference between granting rights through teams vs specific persons?
Hi @Dries-B,
Adding a team gives all team members access to the project as indirect members. If you add someone directly, they become an explicit project member with their own permission level.
As for the Join button, it appears to be tied to whether the user has been added directly to the project.
Thanks for the clarification!
I also noticed that a user that is within a team (with project rights) gets a seperate mail confirmation if he places a comment on a task himself. Which seems rather superfluous. Is this also expected behaviour? Any way to circumvent is, without disturbing other mail notifcations (e.g. from other persons)?
It’s unclear to me why the behaviour between an indirect vs direct project member would be so different. What’s the reasoning behind this? In my use case, I use teams to onboard people more easily (and immediately/automatically give them access to multiple projects, simply based on the team they are in). But right now it still means they have to actually join the project to get the same experience.
