What is the best way to give some users access to workitems only in a project area?
![](http://jazz.net/_images/myphoto/d0d52111676e872b5a5823c286d5c996.jpg)
One answer
![](http://jazz.net/_images/myphoto/d0d52111676e872b5a5823c286d5c996.jpg)
Comments
![](http://jazz.net/_images/myphoto/e5e63d5878217b64611c1df9401b7cd3.jpg)
Another option is to move the source code completely out of the project area. Create another one that is limited to the members and put the members that should have access to the source there. Keep the other project area for work items only. This is how the RTC Development Team does it as far as I know.
![](http://jazz.net/_images/myphoto/d0d52111676e872b5a5823c286d5c996.jpg)
Thanks for the replies, however the project area is well established with both source code and work items present and we need to give another group visibility of the work items only.
![](http://jazz.net/_images/myphoto/a36d1dcfd3e1e1e00aeb18c860d1443d.jpg)
I wouldn't use the term "move" when setting the ownership field of a component. The ownership field is just used for access control ... so if you want to change the access control on a component (which you do), then you are going to have to change the ownership field on that component. On the other hand, the owner field of a work item is for more than access control ... it is also for the schema, editor, categories, etc. for that work item. So in your situation, where you want different access control for work items and for components, your simplest approach is to follow Michele and Ralph's advice ... create a team area or project area whose sole purpose is to define the access control list for components, and set the ownership field of the components to be that new team area or project area. Starting in 6.0.1, you'll be able to specify an access control group for a component, which will be a more intuitive way of achieving the same result.
![](http://jazz.net/_images/myphoto/d0d52111676e872b5a5823c286d5c996.jpg)
ok thanks/