How can I set up TFS 2010 permissions in such a way that only developers can access Source Control, but other groups can view or edit Work Items, all within the same Team Project?
I need to have my business analysts and QA testers be able to update user story states, assignees, etc. within an Iteration, but deny them access to the source code for security reasons.
The previous answer is partially correct. This is how you set permissions within your source control tree. That answer also assumes that every single file and folder in your source control tree has the "Inherit Security Settings" box checked. Permissions within TFS 2010 source control can be much more granular than that.
Permissions for work items are handled at a work item "Area" level. Since Areas are per-team-project work item permissions are also per-team-project.
In Team Explorer right click on your Team Project -> Team Project Settings -> Areas and Iterations. This is where you can setup new Area \ Iterations. There is also a "Security" button at the bottom of the window that will pop the security settings for the selected area node. You can set these permissions very granularly as well... Area nodes always inherit security from their parent node, but can have individual permissions set as well.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With