Skip to content

What is Stakeholder user in Azure DevOps

Vlada Karpovich: https://www.pexels.com/fi-fi/kuva/naine-luova-kasi-alypuhelin-4050319/

What are Stakeholders in Azure DevOps and how you can gain all the benefits from this user type?

Stakeholders are special users in Azure DevOps. They are free tier user, who don’t have basic or any other Azure DevOps license assigned. However they have some restrictions and they cannot perform all the same things than users with basic or some any other license in Azure DevOps.

With Stakeholder user, you can add and edit work items, manage build and release pipelines + view dashboards. You can view the project status and provide feedback, feature ideas and communicate with the team. You cannot access repositories (view or edit code), edit all the project/organization settings and prioritize boards/sprints.

Basic Stakeholder features

This is the Stakeholder feature set addressed by learn.microsoft.com. Most of the Azure DevOps projects are private, so that is the column you most likely want to view for. I have highlighted the most important parts of permissions.

Service, application, or settingPrivate projectPublic project
Azure BoardsPartial accessFull access
Azure ReposNo accessFull access
Azure PipelinesFull accessFull access
Azure Test PlansNo accessNo access
Azure ArtifactsFull accessFull access
NotificationsFull accessFull access
Semantic searchFull accessFull access
Project settingsPartial accessPartial access
Organization settingsPartial accessPartial access
DashboardsPartial accessFull access
Wiki (Project wiki)Partial accessFull access
Wiki (Code wiki)No accessFull access
Stakeholder features

If we go through this bit by bit. Azure Repos is logically ruled out here. Stakeholders cannot contribute on code level and they cannot view the source code. They also have no access for Test Plans, which requires own license (Test Plan) + Basic user license. Other than those Stakeholders have quite wide access set. Stakeholders have partial access on Azure Boards and let’s take a closer look what it means.

How to view what license you have

If you don’t know what license you currently have, you can navigate into organization settings > users page. The Access Level column shows your current license and if you have enough permissions, you can view all the other users licenses.

Current license for panu.oksala is Stakeholder

You can change the license by clicking button at the end of the user row. Available license is based on your organization subscription (see billing page for more details). You can also set the default user license at Billing page. So if you want to add all the new users with basic license, you can do it from that page.

User license can be changed from Users page…

Azure Boards partial access

To give a short description about what Stakeholders can do for work items, I would say: “They can create, edit and view work items. Change and prioritize backlogs, but they cannot prioritize sprint boards. They also cannot create or edit queries, but they can run them.” The biggest drawbacks that causes pain with stakeholder license are the restriction to delete work items and change priority of item within Board/Sprint view. Other than that Stakeholder license can contribute well with the team as a non-coder role.

Dashboard partial access basically means that Stakeholders can view dashboards, but not edit or create them.

Enable full pipeline access for stakeholder

If you want to give full access to Azure Pipelines for Stakeholder users, you have to enable the preview feature from top right corner. Click User settings > Preview Features and select “For this organization” from top most dropdown menu. After that you can see “Full access to Azure Pipelines for Stakeholders” setting. By enabling this preview feature, Stakeholders can edit build and release pipelines like basic users. Stakeholders are still subject to permission set for their security group, so you can restrict them to read-only user group if you want to.

Enable this preview feature to allow Stakeholders to edit pipelines

Summary

You can assign Stakeholder license to basically every member of the team, who don’t contribute on code level, or prioritize boards/sprints. We mainly use Stakeholder license for users who create new work items (bugs and users stories), but who aren’t part of daily job. For example beta testers and managers. Stakeholders can be easily upgraded into Basic license through Users page.