Permissions lookup guide for Azure DevOps

TFS 2017 | TFS 2015 | TFS 2013

Use this index to locate the article on how to manage a specific permission. Most permissions are managed through the user interface for an object, project, or collection. Other permissions are managed by adding users and groups to a role.


You can manage permissions through a command line tool or REST API. Some permissions are only managed through these tools. To learn more, see Security and permission management tools and Security namespace and permission reference.

If you're new to Azure DevOps, review Get started with permissions, access, and security groups and About security roles.

Values in parenthesis indicate what level the permission is managed:

  • Object: Permissions are managed at the object-level
  • Project: Permissions are managed at the project level
  • Collection: Permissions are managed at the account or project collection level
  • Role: Permissions are managed through a security role.
  • Server: Permissions are managed at the instance level for a server
  • Team: Permissions are managed via the team administrator role.















Edit project-level information

The Edit project-level information permission is set through the Project settings page. It includes the ability to perform the following tasks for the selected project defined in an organization or collection.


The permission to add or remove project-level security groups and add and manage project-level group membership is assigned to all members of the Project Administrators group. It isn't controlled by a permissions surfaced within the user interface.

Edit instance-level or collection-level information

The Edit instance-level information (formerly Edit collection level information) permission is set through the Organizations settings or Collection settings page. It includes the ability to perform the following tasks for all projects defined in the organization or collection:

  • Add and administer teams and all team-related features
  • Edit collection-level permissions for users and groups in the collection
  • Add or remove collection-level security groups from the collection
  • Implicitly allows the user to modify version control permissions
  • Edit project level and collection level permission ACLs
  • Edit event subscriptions or alerts for teams, projects, or collection level events.