Answers: <p>Usually each projects would have teams defined with the team members. So if you have a team defined then add the team to the contributors list.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-05-17T12:20:41.780Z
Answers: Unfortunately I did already, but it doesn't change anything :(
Answers: iyenal
Answers: CC BY-SA 4.0
Answers: 2020-05-18T08:37:15.683Z
Answers: See if the same members\team are added as Readers. Azure DevOps might be using inherited permission. Try removing the contributors from readers list.
Answers: Jerry
Answers: CC BY-SA 4.0
Answers: 2020-05-14T09:17:01.403Z
Answers: 2020-05-14T09:17:01.403Z
Answers: Jerry
Body: <p>I have a public Azure DevOps project, and I want to allow everyone to add Work Items.</p>
  
  <p>However, adding the <strong>Readers group as a member of Contributors</strong> for the permissions doesn't change anything, and I can't find <em>"Add Work Items"</em> but only the <em>"Delete Work Items"</em> toggle for changing its own Readers perms so I am really stuck here.</p>
  
  <p>The contributors perms:
  <a href="https://i.sstatic.net/twqAh.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/twqAh.jpg" alt="enter image description here"></a></p>
  
  <p>Having to add every mail account to allow people to add work items isn't possible in my situation (Game Engine project) so I really have to find a solution.</p>
  
Comments: CC BY-SA 4.0
Comments: 2020-05-01T22:21:32.570Z
Comments: Even Stakeholder access level has permission to add work items now. What exactly does a user experience when trying?
Comments: Crowcoder
Comments: CC BY-SA 4.0
Comments: 2020-05-02T23:02:38.247Z
Comments: I have tried that, but unfortunately you can't inherit the group Readers to the group Stakeholder so everyone is able to work items, for a reason I ignore. So they just don't have any perms other than what allows Readers.
Comments: iyenal
Tags: <azure-devops><permissions>
Title: Add permissions to readers (DevOps Web Portal)
UserDisplayName: iyenal
ThreadText: # Add permissions to readers (DevOps Web Portal)
  
  (Asked by: username_0 on 2020-04-16)
  
  I have a public Azure DevOps project, and I want to allow everyone to add Work Items.
  
  However, adding the **Readers group as a member of Contributors** for the permissions doesn't change anything, and I can't find *"Add Work Items"* but only the *"Delete Work Items"* toggle for changing its own Readers perms so I am really stuck here.
  
  The contributors perms:
  [![enter image description here](https://i.sstatic.net/twqAh.jpg)](https://i.sstatic.net/twqAh.jpg)
  
  Having to add every mail account to allow people to add work items isn't possible in my situation (Game Engine project) so I really have to find a solution.
  
  **Tags:** azure-devops, permissions
  
  > **Comments:**
  > **username_1**: Even Stakeholder access level has permission to add work items now. What exactly does a user experience when trying?  
  > **username_0**: I have tried that, but unfortunately you can't inherit the group Readers to the group Stakeholder so everyone is able to work items, for a reason I ignore. So they just don't have any perms other than what allows Readers.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2020-05-14. Score: 1
  
  Usually each projects would have teams defined with the team members. So if you have a team defined then add the team to the contributors list.
  
  > **Comments:**
  > **username_0**: Unfortunately I did already, but it doesn't change anything :(  
  > **username_2**: See if the same members\team are added as Readers. Azure DevOps might be using inherited permission. Try removing the contributors from readers list.  
  
  ---
  
  