About settings for users, teams, projects, or organizations

Supported tasks

Notes

• Set your preferences

For an overview of default permission assignments by role, see Default permissions and access

• View permissions
• Add an alternate account to your Visual Studio subscription

For an overview of default permission assignments by role, see Default permissions and access.

• Authenticate access with personal access tokens
• Use SSH key authentication

For an overview of supported authentication methods, see Authentication overview.

• Set personal or team favorites

For an overview of supported authentication methods, see Authentication overview.

• View your subscriptions, opt-out as needed
• Change your preferred email address
• Manage personal notifications

Notifications alert you through email messages when changes occur to work items, code reviews, pull requests, source control files, builds, and more. When a project is created, a number of notifications are defined. If you want to opt out of these, you can.

Supported tasks

Notes

• Add users to a project or specific team
• Add team administrators

Members of a team are included within the team group, which can be used in queries and @mentions in pull requests and work item discussions.

• Backlog levels
• Show bugs on backlogs & boards
• Set working days
• Configure area paths
• Select active iteration paths (sprints)
• Define work item templates

For an overview of team resources, see About teams and Agile tools. You configure Kanban boards from the board view - Columns, Swimlanes, Cards, WIP limits.

• Create team dashboards
• Set default team dashboard permissions, manage dashboard permissions

New dashboards added to a project are associated with a team. The default permissions allow team members to create and edit dashboards for their team.

• Manage team notifications

Many team notifications are automatically defined when a team is added. For more information about how notifications are managed, see About notifications.

Supported tasks

Notes

• Set project description

Update the project description or change its visibility.

• Add another team and team members
• Add a team administrator

A default team is created when you create a project. You add a team when you want to provide a group of users in your organization a set of Agile tools, which they have full ownership to configure and manage. Teams have access to a product backlog, portfolio backlogs, sprint backlogs, dashboards, team-scoped widgets, and more. For an overview of all tools that support a team, see About teams and Agile tools.

• Add user to a project
• Add a team administrator
• Request an increase in permission levels
• Look up a project administrator
• Change project-level permissions
• Set object-level permissions
• Grant or restrict permissions to select tasks
• Set dashboard permissions
• Set Wiki permissions
• Set feedback permissions
• Set build and release permissions

Project Administrators can add users to a project or a team. When you add a user to a team, you automatically add them to the project. Users added to a project can only view and contribute to that specific project. For an overview of security concepts, see Get started with permissions, access, and security groups and About access levels. For a list of project-level permissions, see Permissions and groups reference, Project-level permissions.

• Manage project-level notifications

Many project-level notifications are automatically defined when a project is added. Notifications at the project-level are managed in much the same way as they are at the team level.

• Configure service hooks

With service hooks, you can automate a task on other services, such as Campfire, Flowdock, HipChat, and more. You can use service hooks in custom apps and services to drive activities as events happen.

• Set default dashboard permissions

New dashboards added to a project inherit the default dashboard permissions. The default permissions allow team members to create and edit dashboards for their team.

• Define area paths
• Define iteration paths or sprints

Area and iteration paths set at the project level are then used to set team defaults. To configure additional product backlogs, Kanban boards, and dashboards, you first add a team.

• Manage Agent queues and agent pools
• Manage service connections
• Manage deployment pools and groups
• Set retention policies

Area and iteration paths set at the project level are then used to set team defaults. To configure additional product backlogs, Kanban boards, and dashboards, you first add a team.

• Create additional Git repositories
• Set Git repository permissions
• Set TFVC repository permissions
• Manage branch policies
• Add Team Foundation Version Control (TFVC) Check-In Policies

You can manage code using Git repositories or one TFVC repository..

• Manage test-related permissions at project level
• Set area path-level test permissions

Manual testing relies on work item types to create and manage test plans, test suites, test cases, shared steps, and shared parameters. You can customize the test plans, test suites, and test cases using an inherited process. For more information, see Customize a process.

• Manage README and Wiki permissions

To share information with your team, you can use Markdown format within a project Wiki, within your project README file, or other repository README file. For more information, see About READMes and Wikis.

• Request a Marketplace extension

Individual contributors and project administrators can request a Marketplace extension is installed. Only members of the Project Collection Administrators group can respond to these requests and actually install extensions.

• Manage and configure team tools
• Manage notifications

For more information, see About teams and Agile tools.

• Manage service connections in Azure Pipelines

For more information, see a list of common service connection types.

Supported tasks

Notes

• Add and manage projects: Create, Rename, Delete
• Add users to projects
• Save project data

A project provides the fundamental resource for storing your code, managing your CI/CD operations, and planning and tracking work for your project. In general, minimize the number of projects you create, to keep things simple. For more information, see About projects and scaling your organization.

• Manage collection-level notifications

Many notifications are automatically defined when an organization is added. Notifications at the organization-level are managed in much the same way as they are at the team level.

• Install and manage Marketplace extensions
• Approve extensions
• Grant permissions to manage extensions
• Uninstall or disable extensions

An extension is an installable unit that contributes new capabilities to your projects. You can find extensions from within the Visual Studio Marketplace in the Azure DevOps tab to support planning and tracking of work items, sprints, scrums, and so on; build and release flows; code testing and tracking; and collaboration among team members.

• Look up the organization owner
• Look up a project collection administrator
• Add administrators, set organization-level permissions
• Grant or restrict access to select features

For an overview of security concepts, see Get started with permissions, access, and security groups and About access levels. For a list of collection-level permissions, see Permissions and groups reference, Collection-level permissions.

• Set retention policies
• Set resource limits for pipelines
• Add and manage agent pools

You manage resources that support CI/CD operations for all projects through the Agent pools page.