To use Azure DevOps features, users must be added to a security group with the appropriate permissions and granted access to the web portal. 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. Stakeholder access is available to support free access to a limited set of features by an unlimited set of stakeholders.
Get hands-on experience on Azure DevOps from live experts at DevOps Online Training India
The most common built-in security groups—Readers, Contributors, and Project Administrators— and team administrator role grant permissions to specific features.
In general, use the following guidance when assigning users to an access level and security group:
- Grant Basic access or higher and add to the Contributors security group full-time workers who contribute to the code base or manage projects.
- Grant Stakeholder access and add to the Contributors security group managers or users who don't actively contribute to the code base but want to check project status and provide direction, feedback, feature ideas, and business alignment to a team.
- Grant Stakeholder access and add to the Project Administrators security group users tasked with managing project resources. If they also need to contribute to the code base, then you must assign them Basic or higher-level access.
- Grant Stakeholder access and add to the Project Collection Administrators security group users tasked with managing organization or collection resources. If they also need to contribute to the code base, then you must assign them Basic or higher-level access.
In the tables provided in this article, a 
checkmark indicates that the corresponding access level or security group has access to a feature by default.
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.
Dashboards, charts, reports, and widgets
You can define and manage team and project dashboards from the web portal, Dashboards. For an overview of dashboard and chart features, see Dashboards. You can set individual dashboard permissions to grant or restrict the ability to edit or delete dashboards.
Users granted Stakeholder access to private projects can't view or create query charts. Stakeholder access to public projects can view and create query charts.
Notes:
- Public project Stakeholders have full access to all features.
Power BI Integration and Analytics views
From the web portal Analytics views, you can create and manage Analytics views. An Analytics view provides a simplified way to specify the filter criteria for a Power BI report based on the Analytics Service data store. The Analytics Service is the reporting platform for Azure DevOps.
To learn more, visit DevOps Online Training India
You set permissions for the service at the project level, and for shared Analytics views at the object level. Users with Stakeholder access have no access to view or edit Analytics views.
Azure Boards
You can plan and track work from the web portal Boards hub, and using Eclipse, Visual Studio, Excel, Project, and other clients. For an overview of work tracking features,
Users granted Stakeholder access are granted different access to features depending on whether it is a private or a public project. For private projects, Stakeholders have limited access to select work tracking functions, whereas for public projects, Stakeholders enjoy full access to work tracking features.
Comments
Post a Comment