restrict specific users to specific projects
![](http://jazz.net/_images/myphoto/e5fb04d48d73529c3220d87b45d1d538.jpg)
Hi,
Apologies if this has been asked before.
How can I restrict access to a project to a specific set of users.
For example,
Users in GroupA can only access and do things with ProjA,
Users in GroupB can only access and do things with ProjB
etc
Users in GroupA and GroupB would have same privileges apart from access to different projects.
Many thanks
Apologies if this has been asked before.
How can I restrict access to a project to a specific set of users.
For example,
Users in GroupA can only access and do things with ProjA,
Users in GroupB can only access and do things with ProjB
etc
Users in GroupA and GroupB would have same privileges apart from access to different projects.
Many thanks
3 answers
![](http://jazz.net/_images/myphoto/e5fb04d48d73529c3220d87b45d1d538.jpg)
Hi,
Apologies if this has been asked before.
How can I restrict access to a project to a specific set of users.
For example,
Users in GroupA can only access and do things with ProjA,
Users in GroupB can only access and do things with ProjB
etc
Users in GroupA and GroupB would have same privileges apart from access to different projects.
Many thanks
for a basic primer, check the bottom of the deploying buildforge article I wrote late last year. http://jazz.net/library/article/584 But you should also investigate the infocenter documentation on access groups available from publib at http://publib.boulder.ibm.com/infocenter/bldforge/v7r1m2/index.jsp?topic=/com.ibm.rational.buildforge.doc/topics/admin_access_groups.html
or also through your management console's help application.
![](http://jazz.net/_images/myphoto/e5fb04d48d73529c3220d87b45d1d538.jpg)
The section of your basic primer covering access groups is a great start, but unfortunately, the devil is in the details. It doesn't mention anything about having shared environments, libraries, or projects and how to effectively have two distinct groups of "Build Engineers" but only with the ability to manage their own objects, even with visibility to other things.
Is there a way to get there?
Is there a way to get there?
![](http://jazz.net/_images/myphoto/e5fb04d48d73529c3220d87b45d1d538.jpg)
The section of your basic primer covering access groups is a great start, but unfortunately, the devil is in the details. It doesn't mention anything about having shared environments, libraries, or projects and how to effectively have two distinct groups of "Build Engineers" but only with the ability to manage their own objects, even with visibility to other things.
Is there a way to get there?
Not really. in buildforge, permissions are applicable to all visible objects. The only way to accomplish this is through multiple user accounts. You can keep others from viewing and modifying your projects, but if a user has modify rights to their projects, and you add them to the group to let them see your projects, they can now modify your projects as well.