Currently, the project area is what defines the set of people that have
read access, so you would have to create a project area for each
distinct "visibility group". You would then make a particular component
owned by the appropriate project area.

There is the concept of a "sub-project" (it would be a child team area),
but read access to the artifacts owned by a team area is currently just
inherited from the root project area, so creating nested team areas
doesn't help you control the visibility of artifacts.

Cheers,
Geoff

sfrancis wrote:

Hi, hopefully this is a basic question.

I have a project area in place and doing what I need. Now I have some
utilities written related to it that I'd like to manage in RTC. I
would like to have the code in the same project area, but limit
access to the source code to a smaller team of developers since these
are internal to our department. I'd rather not have to create a new
project area, but I want to do the 'right thing' in terms of managing
my project area in RTC. Is there a concept of a sub-project?