Add all users as members of the top-level Team Area?
Hi,
I work on a few different projects which use RTC, and were set up by different admins.
Some of them add *everybody* to the top-level Team Area, and some don't.
I find that kind of annoying, because that gives *everybody* inherited pseudo-membership in *every* team. So Team Plans show EVERYBODY unless you hide empty folders, etc.
What's the recommended practice here? Is there a reason for adding everybody to the top-level team area?
I work on a few different projects which use RTC, and were set up by different admins.
Some of them add *everybody* to the top-level Team Area, and some don't.
I find that kind of annoying, because that gives *everybody* inherited pseudo-membership in *every* team. So Team Plans show EVERYBODY unless you hide empty folders, etc.
What's the recommended practice here? Is there a reason for adding everybody to the top-level team area?
2 answers
On Wed, 22 Sep 2010 15:53:02 +0000, tvolin wrote:
Assigning everyone at a top-level team area can make administration
easier because this lets you grant everyone the a role (e.g.
"Contributor") that will apply in every team.
In the Jazz Foundation project area, we don't do this. We only assign the
Contributor role to people who work on each individual team and we use
different roles in higher-level teams to express permissions that people
have at those higher levels (for example, we have a buildmeister role for
everyone who can deliver to our Integration stream).
- Jared
---------------------------
Jazz Team Process
Hi,
I work on a few different projects which use RTC, and were set up by
different admins.
Some of them add *everybody* to the top-level Team Area, and some don't.
I find that kind of annoying, because that gives *everybody* inherited
pseudo-membership in *every* team. So Team Plans show EVERYBODY unless
you hide empty folders, etc.
What's the recommended practice here? Is there a reason for adding
everybody to the top-level team area?
Assigning everyone at a top-level team area can make administration
easier because this lets you grant everyone the a role (e.g.
"Contributor") that will apply in every team.
In the Jazz Foundation project area, we don't do this. We only assign the
Contributor role to people who work on each individual team and we use
different roles in higher-level teams to express permissions that people
have at those higher levels (for example, we have a buildmeister role for
everyone who can deliver to our Integration stream).
- Jared
---------------------------
Jazz Team Process
Assigning everyone at a top-level team area can make administration
easier because this lets you grant everyone the a role (e.g.
"Contributor") that will apply in every team.
In the Jazz Foundation project area, we don't do this. We only assign the
Contributor role to people who work on each individual team and we use
different roles in higher-level teams to express permissions that people
have at those higher levels (for example, we have a buildmeister role for
everyone who can deliver to our Integration stream).
Thanks. That's just what I was looking for.