Restricting delivery permissions on Streams

I know it's and old post, but I found a better solution in RTC 6.0.

I have not really tried this but my approach would be to try the following.

I believe, who is allowed to deliver to a stream is based upon his role in the team that owns the stream. The role carries the specific permissions and can be configured in the team process.

Think about roles such as ProductionIntegrator, Integrator, Developer.

Set up a team e.g. Production where the roles and permissions are set to the limited number of users you want to be able to deliver. E.g. only ProductionItegrators can deliver to a stream owned by this team.

Set up a team integration configured to this specific roles and permissions and the users having the desired role assignment. e.g. Integrators are allowed to deliver to Streams owned by this Team.

Set up a team a development team likewise.

Set up Streams for the specific teams.

Production, Integration, Development can be nested to reduce administration, where the roles have more rights in the sub teams. Production could be the Main team on the development timeline, containg the other teams.

Just my thoughts on this one.

Ralph

Thank you Ralph,

In other words you are suggesting to create

One team per stream, and If i need to give permissions to any of the streams, I would simple have to add the member to the team that owns the stream.

To me this looks like a bit of an overhead, don't you think ?

Is there a way to say for instance:

Role 1 has delivery access to Stream 1
Role 2 has delivery access to Stream 1 and 2
Role 3 has delivery access to Stream 1 2 and 3.

All Roles and Streams are under one team area.

Yes, there is support in 2.0 for this. See the
following chapter in our permissions article:

http://jazz.net/library/article/215#componentadvisor

Cheers,
Jean-Michel

On 8/25/2009 2:07 PM, bsalami wrote:

Hello great experts,

Is there a way
to restrict access to individual streams in the same team
?

My scenario work like this: I like to maintain 3 streams:
Development: Everyone on
the team has access to check in code
Integration: Only a handful of folks have
access to this stream to select stories from dev and deliver into to
this Stream
Production: Only a smaller number of
folks have access which can promote a stable snapshot of the
Integration stream to production.
I like this all to be under the same project with the same team area.
Any help is appreciated

Thanks for pointing that out!

Ralph

This article may answer your question:

http://jazz.net/library/article/215

Michael

bsalami wrote:

Thank you Ralph,

In other words you are suggesting to create

One team per stream, and If i need to give permissions to any of the
streams, I would simple have to add the member to the team that owns
the stream.

To me this looks like a bit of an overhead, don't you think ?

Is there a way to say for instance:

Role 1 has delivery access to Stream 1
Role 2 has delivery access to Stream 1 and 2
Role 3 has delivery access to Stream 1 2 and 3.

All Roles and Streams are under one team area.

That is great, One small problem.

I am using 1.0.1.1 client and can not upgrade to 2.0 client anytime soon.
Unfortunately, our server is going to stay at 1.0.1.1 for a long time.

Is there another way in 1.0.1.1 ?

This article may answer your question:

http://jazz.net/library/article/215

Michael

bsalami wrote:

Thank you Ralph,

In other words you are suggesting to create

One team per stream, and If i need to give permissions to any of the
streams, I would simple have to add the member to the team that owns
the stream.

To me this looks like a bit of an overhead, don't you think ?

Is there a way to say for instance:

Role 1 has delivery access to Stream 1
Role 2 has delivery access to Stream 1 and 2
Role 3 has delivery access to Stream 1 2 and 3.

All Roles and Streams are under one team area.

Hi,

RTC 2 added a lot of capabilities. I currently don't have a 1.x installation available so I can't check. I think the one option you can try is looking for the Streams belonging to different Teams solution. I would check first if Team permissions allow restricting which role can deliver to which teams Stream.

Ralph