<p>Thanks to Daniel Mann (see the comment on <a href="https://stackoverflow.com/q/77852519/1637105">this SO post</a>), <a href="https://learn.microsoft.com/en-us/azure/devops/organizations/security/stakeholder-access?view=azure-devops" rel="nofollow noreferrer">the docs</a> clearly state that <strong>Basic</strong> access level is required to:</p>
<ul>
<li>Change the priority of an item within a board</li>
<li>Change fields on cards on a board, except for State field</li>
</ul>

CC BY-SA 4.0
2024-01-20T22:18:52.530Z
2024-01-22T03:10:18.957Z
2024-01-22T03:10:18.957Z
Bob.at.Indigo.Health
<p>EDIT: This is a duplicate of <a href="https://stackoverflow.com/q/77852519/1637105">https://stackoverflow.com/q/77852519/1637105</a>. I originally posted this question in this &quot;DevOps&quot; community, then I found a <a href="https://learn.microsoft.com/en-us/azure/devops/user-guide/provide-feedback?view=azure-devops" rel="nofollow noreferrer">Microsoft support article</a> that says to post questions in the main StackOverflow community with the <strong>[azure-devops]</strong> tag.</p>
<p>In my organization, I have a user who will serve as &quot;project manager&quot;. I want to give her the ability to move items around on the Kanban &quot;Board&quot;, assign personnel to user stories and tasks, and generally be in charge of dealing with the DevOps project management artifacts.</p>
<p>I'm trying to figure out the permissions I need to give her in Azure DevOps. I've put her in the <strong>Contributors</strong> project group.</p>
<ul>
<li><p>If I give her <strong>Stakeholder</strong> access level then she can move board items from one column to another, but she cannot move board items up or down within the same column or change the personnel assigned to an item.</p>
</li>
<li><p>If I give her <strong>Basic</strong> access level then she has full editing access to the board, including the ability to move items up or down within the same column.</p>
</li>
</ul>
<p>Do I really need to give users <strong>Basic</strong> access level for them to be able to serve as project managers, with the ability to add items, edit items, reorder items, assign personnel to items, and otherwise deal with project management features?</p>

<azure-devops>
Required permissions to reorder Board items
Bob.at.Indigo.Health
# Required permissions to reorder Board items

(Asked by: username_0 on 2024-01-20)

EDIT: This is a duplicate of <https://stackoverflow.com/q/77852519/1637105>. I originally posted this question in this "DevOps" community, then I found a [Microsoft support article](https://learn.microsoft.com/en-us/azure/devops/user-guide/provide-feedback?view=azure-devops) that says to post questions in the main StackOverflow community with the **[azure-devops]** tag.

In my organization, I have a user who will serve as "project manager". I want to give her the ability to move items around on the Kanban "Board", assign personnel to user stories and tasks, and generally be in charge of dealing with the DevOps project management artifacts.

I'm trying to figure out the permissions I need to give her in Azure DevOps. I've put her in the **Contributors** project group.

* If I give her **Stakeholder** access level then she can move board items from one column to another, but she cannot move board items up or down within the same column or change the personnel assigned to an item.
* If I give her **Basic** access level then she has full editing access to the board, including the ability to move items up or down within the same column.

Do I really need to give users **Basic** access level for them to be able to serve as project managers, with the ability to add items, edit items, reorder items, assign personnel to items, and otherwise deal with project management features?

**Tags:** azure-devops


---

## 1 answers

### Answer by username_0 on 2024-01-20. Score: 0

Thanks to Daniel Mann (see the comment on [this SO post](https://stackoverflow.com/q/77852519/1637105)), [the docs](https://learn.microsoft.com/en-us/azure/devops/organizations/security/stakeholder-access?view=azure-devops) clearly state that **Basic** access level is required to:

* Change the priority of an item within a board
* Change fields on cards on a board, except for State field


---

