CODEWITHSUNDEEP
azure-devops
bitshift
bitshift

Reputation: 6852

Access level - stakeholder vs visual studio user

Can a user that has a Visual Studio subscription be given only "stakeholder" access? That way they can still use Visual Studio for their purposes, but as for VSTS and a team project, they can only do things such as enter bugs, get to the kanban boards (and update it if needed), define sprints etc. Basically "management stuff".

Upvotes: 2

Views: 2666

Answers (1)

Negatar
Negatar

Reputation: 809

VSTS automatically assigns them Basic features, if your account has seats available, or Stakeholder features, if not. -Microsoft Docs

What this effectively means is that VSTS will upgrade your user to the highest available license when the user logs in.

  • Any unassigned Basic License registered to your account automatically get assigned to stakeholders as they log in. (based on Microsoft Docs)
  • The same auto upgrade happens when the user have some sort of MSDN license. (based on personal experience)

So due to the auto upgrade process, trying to keep a user in the Stakeholder License as a means to restrict access might be a losing battle. You might want to modify permissions around this user instead or create a custom security group between Readers and Contributors.

Upvotes: 4

Related Questions