About settings at the user, team, project, or organization-level

Azure DevOps Services | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013

You configure resources either for yourself, your team, a project, or your organization from an administrative Settings page. The settings you can configure depend on the security group or administrative role you belong to.

If you're just getting started as a Project Administrator, see Get started as an administrator.

Note

You can delegate several tasks to a user with Stakeholder or Basic access by adding them to the Project Collection Administrators group. To learn more about Stakeholder access, see About access levels, Stakeholder access.

You configure resources either for yourself, your team, a project, or your project collection from a Settings page. The settings you can configure depend on the security group or administrative role you belong to.

User settings

Individual contributors can set their user preferences, enable features that are in preview, and manage their favorites and notifications.

Area Supported tasks Notes
General For an overview of default permission assignments by role, see Default permissions and access.
Security For an overview of default permission assignments by role, see Default permissions and access.
Authentication For an overview of supported authentication methods, see Authentication overview.
Favorites Favorites provide a quick way to navigate to backlogs, boards, dashboards, and more artifacts. Any member of the Contributors group or team member can set their own favorites. Team members can set team favorites.
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.

Team Administrator role and managing teams

Team administrators are tasked with configuring team resources which mostly correspond to Agile tools and dashboards. To configure team resources, you must be added as a team administrator for the specific team, or be a member of the Project Administrators or Project Collection Administrators groups.

For a complete overview of all Agile tools that you can configure, see Manage teams and configure team tools.

Area Supported tasks Notes
Team profile 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.
Boards, Team configuration 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.
Dashboards 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.
Notifications A number of team notifications are automatically defined when a team is added. To learn more about how notifications are managed, see About notifications.

Project Administrator role and managing projects

Members of the Project Administrators group are tasked with configuring resources for a project and managing permissions at the project-level. Note that members of the Project Collection Administrators group can configure team settings as well.

See also Get started as an administrator.

Project settings
From the administrative Project settings pages, you can configure settings available from the tabs shown in the following image.

Project settings, new nav

Project-level settings
From the administrative Project settings pages, you can configure settings available from the tabs shown in the following image.

Project settings, conceptual

Note

Project settings differ depending on your on-premises TFS version. Some settings aren't available for earlier versions of TFS.

Area Supported tasks Notes
General Update the project description or change it's visibility.

Services Services that aren't use by project members can be disabled so that they don't appear in the web portal. Turning a service off removes the service from the user interface for all project users. However, data defined for the service is preserved and available if you later decide to turn the service on.

Teams 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.

Security 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 About permissions and groups and About access levels. For a list of project-level permissions, see Permissions and groups reference, Project-level permissions.

Notifications
  • Manage project-level notifications
A number of 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.
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.
Dashboards 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.
Boards, Project configuration 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.
Build and release (Agent Pools, Release) To build your code or deploy your software you need at least one agent. Agent and deployment pools are build and release resources that you manage across projects.
Repos, Code, version control You can manage code using Git repositories or one Team Foundation Version Control (TFVC) repository.
Test Manual testing relies on work item types to create and manage test plans, test suites, test cases, shared steps, and shared parameters. Of these, you can customize the test plans, test suites, and test cases using an inherited process. See Customize a process.
Wiki 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. To learn more, see About READMes and Wikis.
Extensions Individual contributors and project administrators can request a Marketplace extension be installed. Only members of the Project Collection Administrators group can respond to these requests and actually install extensions.

Project Collection Administrator (PCA) role and managing collections of projects

Members of the Project Collection Administrators group are tasked with configuring resources for all projects defined for an organization or collection. They also can perform all tasks to add projects, manage projects, and manage permissions for the collection, a project, or an object.

Organization settings
From the administrative Organization settings pages, you can configure settings available from the tabs shown in the following image.

Organization settings, new nav

Project collection-level settings
From the administrative pages for a collection, you can configure the settings shown in the following image.

Note

Project collection settings differ depending on your on-premises TFS version. Some settings aren't available for earlier versions of TFS.

Collection settings, TFS, conceptual

For an overview of managing your organization, see About organization management.

Area Supported tasks Notes
Preview features Organization administrators can enable or disable account-level features that are in preview.
Overview (Settings) From the Settings page, you can manage the time zone, owner, region, and other settings that apply to all projects defined under your account.
Billing All billing is managed through Azure. To learn more, see Billing overview.
Projects 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, you'll want to minimize the number of projects you create, to keep things simple. Learn more About projects and scaling your organization.
Policy Set policies to allow or disallow access by other applications or services to the organization.
Users For large organizations with a sizable number of users, we recommend that you manage user access through Azure Active Directory. For a small number of users, you can manage user access by adding their Microsoft Service Account (MSA) email. From the account-level Users page, you can also export the set of users and their access levels.
Security For an overview of security concepts, see About permissions and groups and About access levels. For a list of collection-level permissions, see Permissions and groups reference, Collection-level permissions.

Notifications A number of 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.
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, etc.; build and release flows; code testing and tracking; and collaboration among team members.
Usage Certain rate limits are in place to ensure performance across the cloud service platform.
Boards, Process Process customization applies to Azure Boards only. To customize the Agile tools and work tracking artifacts, you create and customize an inherited process and then update the project to use that process. To learn more, see About process customization and inherited processes.
Build and release You manage resources that support CI/CD operations for all projects through the Agent pools, Deployment pools, and Retention and limits pages.

For an overview of managing collections, see Configure and manage Azure DevOps Server resources.

Area Supported tasks Notes
Settings From the Settings page, you can manage the time zone, owner, region, and other settings that apply to all projects defined under your account.
Projects 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, you'll want to minimize the number of projects you create, to keep things simple. Learn more About projects and scaling your organization.
Security For an overview of security concepts, see About permissions and groups and About access levels. For a list of collection-level permissions, see Permissions and groups reference, Collection-level permissions.

Notifications
  • Manage collection-level notifications
A number of notifications are automatically defined when a project collection is added. Notifications at the collection-level are managed in much the same way as they are at the team level.
Boards, Process Process customization applies to Azure Boards only. To customize the Agile tools and work tracking artifacts, you create and customize an inherited process and then update the project to use that process. To learn more, see About process customization and inherited processes.
Build and release, Agent pools, Deployment pools You manage resources that support CI/CD operations for all projects through the Agent pools, Deployment pools, and Retention and limits pages.
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, etc.; build and release flows; code testing and tracking; and collaboration among team members.

For an overview of managing collections, see Configure and manage TFS resources.

Area Supported tasks Notes
Settings From the Settings page, you can manage the time zone, owner, region, and other settings that apply to all projects defined under your account.
Projects 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, you'll want to minimize the number of projects you create, to keep things simple. Learn more About projects and scaling your organization.
Security For an overview of security concepts, see About permissions and groups and About access levels. For a list of collection-level permissions, see Permissions and groups reference, Collection-level permissions.

Notifications
  • Manage collection-level notifications
A number of notifications are automatically defined when a project collection is added. Notifications at the collection-level are managed in much the same way as they are at the team level.
Build and release, Agent pools, Deployment pools You manage resources that support CI/CD operations for all projects through the Agent pools, Deployment pools, and Retention and limits pages.
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, etc.; build and release flows; code testing and tracking; and collaboration among team members.

Server Administrator role

Members of the Team Foundation Server Administrators group are tasked with configuring resources for all project collections. They also can perform all tasks to administer projects, collections, and server instances.

The main task they perform from the web portal is to set access levels for a user or security group. See Change access levels.

For additional information, see Team Foundation Server Administration Documentation.