Welcome to the Jazz Community Forum
How to limit access only to certain files
As a team member, "O" can download all the files in components in streams for the team.
Anyone comment on this "might be possible" solution below?
To limit access, "X" should not be a team member.
"X" needs his own repository workspace and his own components and these components will be filled by "O" who belong to the team.
After "X" finishes his work, "O" will pull the modification and push into the team stream.
Anyone comment on this "might be possible" solution below?
To limit access, "X" should not be a team member.
"X" needs his own repository workspace and his own components and these components will be filled by "O" who belong to the team.
After "X" finishes his work, "O" will pull the modification and push into the team stream.
3 answers
As a team member, "O" can download all the files in components in streams for the team.
Anyone comment on this "might be possible" solution below?
To limit access, "X" should not be a team member.
"X" needs his own repository workspace and his own components and these components will be filled by "O" who belong to the team.
After "X" finishes his work, "O" will pull the modification and push into the team stream.
Hi
In your example - do I understand you correctly that you want developer "X" to work on certain files only. and not see any other files or deliver them to a stream? And then "O" will deliver the files.
It sounds like you might be able to do something with the Deliver permissions - so "X" cannot deliver, but I am not sure you can hide other files in the stream from "X".
anthony
Hi
In your example - do I understand you correctly that you want developer "X" to work on certain files only. and not see any other files or deliver them to a stream? And then "O" will deliver the files.
It sounds like you might be able to do something with the Deliver permissions - so "X" cannot deliver, but I am not sure you can hide other files in the stream from "X".
anthony
The purpose is to allow read (& write) access only to selected files.
One component/team per a group of files scheme to support this seems not applicable if a Eclipse project needs several groups of files from multiple components.
To restrict read access to a set of files, you are correct that you
would need to put them in a separate component. But no need to prevent
X from being a team member.
An example would probably help:
Suppose your team area is MyTeam, in the project area MyProj. You would
assign both X and O as members of MyTeam. Files that you want visible
to everyone on the team would be assigned to components that belong to
MyProj. For files that should be visible only to O, you would create a
new project area, RestrictedReadProj (doesn't matter what process
template you use for it ... all you will be using from that project area
is its "read access" config data). In RestrictedReadProj, list the
users that should have read access to the restricted components. Now
put all the files that should have restricted read access into
components that belong to RestrictedReadProj. Note that you can add
components from any project area into a stream or a workspace ... as
long as you have read permission to that component and have write
permission to that stream or workspace. So O can put all components
into the MyTeam stream, but X will only be able to read/load the subset
of those components that he has read access to.
Of course, this doesn't help if the restricted files need to live in the
same directory as the non-restricted files. I've created work-item
118445 requesting that functionality. Note: There also is work item
63844, requesting read/write access at the folder level. If you need
functionality of this kind, it would be worth subscribing to one of
these work items, indicating whether you need file-level read/write
access, or whether folder level read/write access would be sufficient.
Cheers,
Geoff
On 6/18/2010 2:22 AM, kdyoung.kr.ibm.com wrote:
would need to put them in a separate component. But no need to prevent
X from being a team member.
An example would probably help:
Suppose your team area is MyTeam, in the project area MyProj. You would
assign both X and O as members of MyTeam. Files that you want visible
to everyone on the team would be assigned to components that belong to
MyProj. For files that should be visible only to O, you would create a
new project area, RestrictedReadProj (doesn't matter what process
template you use for it ... all you will be using from that project area
is its "read access" config data). In RestrictedReadProj, list the
users that should have read access to the restricted components. Now
put all the files that should have restricted read access into
components that belong to RestrictedReadProj. Note that you can add
components from any project area into a stream or a workspace ... as
long as you have read permission to that component and have write
permission to that stream or workspace. So O can put all components
into the MyTeam stream, but X will only be able to read/load the subset
of those components that he has read access to.
Of course, this doesn't help if the restricted files need to live in the
same directory as the non-restricted files. I've created work-item
118445 requesting that functionality. Note: There also is work item
63844, requesting read/write access at the folder level. If you need
functionality of this kind, it would be worth subscribing to one of
these work items, indicating whether you need file-level read/write
access, or whether folder level read/write access would be sufficient.
Cheers,
Geoff
On 6/18/2010 2:22 AM, kdyoung.kr.ibm.com wrote:
As a team member, "O" can download all the files in
components in streams for the team.
Anyone comment on this "might be possible" solution below?
To limit access, "X" should not be a team member.
"X" needs his own repository workspace and his own
components and these components will be filled by "O" who
belong to the team.
After "X" finishes his work, "O" will pull the
modification and push into the team stream.