Restricting access to some specific stream component

I reply my question:
there is no way to control read permission at stream component level unless you change the RTC source code on scm module.

But i really recommend RTC DEV group open this function to users

Create a new project area that you will use just to define the list of
users that should have read permission to that component, and then
change the owner of that component to be that new project area.

Cheers,
Geoff

On 7/12/2010 10:51 PM, uddi.luke wrote:

We now use RTC v2 to manage our develeopment , and we met a problem
about permission of stream component:

Our project includes many modules developed using many languages,like
Java, C(linux), C++(ms visual stadio), and delphi. In RTC, the main
development stream will have many components to cover the module
respectively. And we want the component only visible to its owner for
security
reason, that means we need grant/revoke read permision to stream
component, but we find no way to do it, can anybody help ?

Thank you.

PS. we found at projectarea level, we can control access permission,
but we prefer using one projectarea to manage our development.

Thanks for your reply!
But I think one project area may be better to manange our whole project then using serveral project areas.

Create a new project area that you will use just to define the list of
users that should have read permission to that component, and then
change the owner of that component to be that new project area.

Cheers,
Geoff

On 7/12/2010 10:51 PM, uddi.luke wrote:

We now use RTC v2 to manage our develeopment , and we met a problem
about permission of stream component:

Our project includes many modules developed using many languages,like
Java, C(linux), C++(ms visual stadio), and delphi. In RTC, the main
development stream will have many components to cover the module
respectively. And we want the component only visible to its owner for
security
reason, that means we need grant/revoke read permision to stream
component, but we find no way to do it, can anybody help ?

Thank you.

PS. we found at projectarea level, we can control access permission,
but we prefer using one projectarea to manage our development.

I agree that having one "real" project area (which contains team areas,
components, streams, etc.) is how you'll want to start.

But in addition to your real project area, you need to create "access
control" project areas for each access control list you want to define.
I agree that this is both a confusing and non-intuitive "overloading"
of the project area concept, but its what you need to do to create
access control lists.

One suggestion: Create your own "access control" process template (with
no work item types, iterations, or anything), and instantiate all of
your access control project areas from that access control process
template. That will help document that these are "access control
project areas" and not "real project areas".

Cheers,
Geoff

On 7/15/2010 2:06 AM, uddi.luke wrote:

Thanks for your reply!
But I think one project area may be better to manange our whole
project then using serveral project areas.


gmclemmwrote:
Create a new project area that you will use just to define the list
of
users that should have read permission to that component, and then
change the owner of that component to be that new project area.

Cheers,
Geoff

On 7/12/2010 10:51 PM, uddi.luke wrote:
We now use RTC v2 to manage our develeopment , and we met a
problem
about permission of stream component:

Our project includes many modules developed using many
languages,like
Java, C(linux), C++(ms visual stadio), and delphi. In RTC, the
main
development stream will have many components to cover the module
respectively. And we want the component only visible to its owner
for
security
reason, that means we need grant/revoke read permision to stream
component, but we find no way to do it, can anybody help ?

Thank you.

PS. we found at projectarea level, we can control access
permission,
but we prefer using one projectarea to manage our development.

Geoff - Your comment above about creating an "Access Control" only process template. Do you know of anyone currently doing this? Is it documented somewhere on how this might be accomplished? This may help simplify many projects who are facing this non-intuitive and overloaded access control issue.

I've just submitted a work item for this: 122029.

For anyone interested, please subscribe to the work item and add a
comment to indicate your interest/support.

Cheers,
Geoff

On 7/16/2010 8:53 AM, thloeber wrote:

Geoff - Your comment above about creating an "Access
Control" only process template. Do you know of anyone currently
doing this? Is it documented somewhere on how this might be
accomplished? This may help simplify many projects who are facing
this non-intuitive and overloaded access control issue.