VSTS SaaS版:Scrum Master修改项目Sprint成员容量所需权限配置
Alright, let's walk through exactly what permissions your Scrum Master needs to modify team members' sprint capacity in VSTS (now officially Azure DevOps Services) when you're managing users directly via the web portal (no Azure AD integration):
Required Permissions for Sprint Capacity Modification
The necessary permissions split into two focused areas—team-specific settings and iteration (sprint) access. Here's the breakdown:
1. Team-Level Core Permission
- View and edit team capacity: This is the critical permission for managing capacity. You'll need to grant this to your Scrum Master (or the group they belong to) for the specific team they're supporting.
- To configure: Navigate to your project, go to Project Settings > Teams > [Your Team Name] > Permissions. Locate the "View and edit team capacity" permission and set it to Allow for the user/group.
2. Iteration (Sprint) Access
- Edit work items in this iteration: Modifying capacity ties into the sprint's work item context, so the Scrum Master needs permission to edit items within the target sprint.
- By default, members of the Contributors group have this access, but if you've tightened security, verify it explicitly: Go to Project Settings > Project Configuration > Iterations > [Your Target Sprint] > Permissions, and ensure "Edit work items in this node" is set to Allow for the user/group.
Quick Notes
- You don't need to grant full Project Administrator rights here—these targeted permissions are enough to let the Scrum Master manage capacity without overassigning access.
- If you use custom security groups, double-check that the Scrum Master's group inherits or is explicitly granted these permissions (default settings might not apply if you've customized access).
内容的提问来源于stack exchange,提问作者garfbradaz
相关产品推荐
相关产品推荐

