Team Development with Visual Studio Team Foundation Server

You can create security groups for your team project to better meet your organization’s
security requirements. Creating a security group is an efficient way to grant a specific set
of permissions to a group of users on your team project. Make sure that you allow only
the minimum permissions necessary for the group, and add only those users or groups
who must belong to this new team project group.
Additionally use the following guidelines:
• Do not change the permissions on default groups (or if you do, do it in every project
the same way)
• Use Active Directory (AD) groups for membership on server level only
• Use TFS groups for permissions settings (rather than AD groups)
• Never deny anything (usually deny means that the partitioning you use is less than
ideal); make sure you reason is sound when you do
Additional Resources
• For more information on creating security groups, see “How To – Manage Projects in
Visual Studio Team Foundation Server” in this guide.
• For more information on TFS permissions, see “Team Foundation Server
Permissions” at http://msdn2.microsoft.com/en-us/library/ms252587(VS.80).aspx
Assign Team Members to the Appropriate Security Group
Identify the team members who will be working on the project and their roles, and assign
these team members to TFS by using existing team project groups, server-level groups, or
custom security groups that you create.
When assigning members to a security group, assign only those members who need the
permissions available to that security group. If necessary, you can create custom security
groups with appropriate security permissions and then assign users to those security
groups.
Additional Resources
• For more information about security groups, see “How To – Manage Projects in
Visual Studio Team Foundation Server” in this guide.
Team Projects
• Create one team project per application if you want to migrate work items and
other assets between application versions.
• Create one team project per version if you want to start with new work items
and other assets with each application version.
• Create one team project per team when working with large projects that span
multiple projects.
• Grant only required permissions on project assets.
• Structure your source tree to support branching.