| title | titleSuffix | description | ms.custom | ms.service | ms.assetid | ms.author | author | ms.topic | monikerRange | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|
Default permissions and access for Azure Boards |
Azure Boards |
Learn about default permissions and access levels in Azure Boards. |
boards-get-started, engagement-fy23 |
azure-devops-boards |
chcomley |
chcomley |
conceptual |
<= azure-devops |
02/02/2023 |
[!INCLUDE version-lt-eq-azure-devops]
As a member of an Azure Boards project, you can use most features to track work. Limitations to select features are based on the access level and security group to which a user is assigned. The Basic access level and higher supports full access to all Azure Boards features. Stakeholder access level provides partial support to select features, allowing users to view and modify work items, but not use all features. The built-in security groups—Readers, Contributors, and Project Administrators—and team administrator role grant permissions to specific features.
In the tables provided in this article, a ✔️ indicates that the corresponding access level or security group has access to a feature by default.
Note
Team administrators can configure settings for their team's tools. Organization owners and members of the Project Administrators group can configure settings for all teams.
For a comparison chart of Stakeholder versus Basic access, see the Feature matrix. To assign or change an access level, see Add users and assign licenses. If you need to grant specific users select permissions, you can do so.
You can use work items to track anything you need to track. For more information, see Understand how work items are used to track issues, tasks, and epics.
[!INCLUDE temp]
Boards present work items as cards and support quick status updates through drag-and-drop.
[!INCLUDE temp]
Backlogs display work items as lists. A product backlog represents your project plan and a repository of all the information you need to track and share with your team. Portfolio backlogs allow you to group and organize your backlog into a hierarchy.
[!INCLUDE temp]
Sprints provide a filtered view of work items that a team has assigned to specific iteration paths or sprints.
[!INCLUDE temp]
Queries are filtered lists of work items based on criteria that you define by using a query editor.
Tip
By default, Contributors can't create and save shared queries. We recommend that Project Administrators create a query folder for each team and give the team administrators or the team group query permissions to manage their folder. You need Delete permissions to rename or move a shared query or folder, and Contribute permissions for the folder where you move the query to. For more information, see Set permissions on queries and query folders.
[!INCLUDE temp]
Stakeholder access supports business owners. It also supports analysts and other team members who don't manage the work of a project, but need to view and add ideas to the backlog, add context and information to work items, and review status and progress. All members of an organization who don't use Visual Studio but want to contribute to work item tracking and monitor progress can be assigned as a stakeholder. Note, even if you change the permission level for a user assigned Stakeholder access, the user is blocked from accessing the feature.
::: moniker range="azure-devops"
Note
For public projects, Stakeholder access gives users full access to all work-tracking features. For more information, see Stakeholder access quick reference.
::: moniker-end