In this guide, I will walk you through exactly how to add team members in Azure DevOps, and how I manage team additions—from the high-level organization settings down to granular team permissions.
Table of Contents
How to add team members in Azure DevOps
Managing Azure DevOps effectively means understanding the hierarchy. You aren’t just “adding an email”; you are assigning a License (Access Level) and a Permission Set (Security Group).
Prerequisites:
Before we start, you need to ensure you have the right permissions to actually add people.
- Organization Level: To add users to the organization, you must be a member of the Project Collection Administrators group or be the Organization Owner.
- Project Level: To add users to a specific project team, you should be a Project Administrator or a Team Administrator.
If you’re sitting there looking at a greyed-out “Add” button, check your own profile settings first!
Understanding Azure DevOps Access Levels
| Access Level | Who is it for? | Cost (Typical) | Key Features |
| Basic | Developers, Designers, PMs | First 5 free, then ~$6/mo | Boards, Repos, Pipelines, Artifacts |
| Stakeholder | Clients, Executive Sponsors | Free (Unlimited) | View Boards, Add/Edit Work Items |
| Basic + Test Plans | QA Engineers, SDETs | ~$52/mo | Everything in Basic + Manual Testing tools |
| Visual Studio Subscriber | Developers with MSDN | Included in Subscription | Automatically detected based on login |
Step 1: Adding a User to the Organization
I always recommend adding users at the organization level first. This makes them “available” to be picked for any project within your company.
The Walkthrough:
- Log in to your Azure DevOps organization (e.g.,
dev.azure.com/YourCompany). - In the bottom-left corner, click on Organization Settings.
- Under the General section, click on Users.
- Click the blue Add users button at the top right.
- Enter Information: * Users: Type in the email (e.g.,
chloe.baker@yourcompany.com).- Access Level: For a developer, I’ll choose Basic.
- Add to Projects: Select the specific project they’ll be working on.
- Azure DevOps Groups: By default, I usually add them to [Project Name]\Contributors.
- Click Add. Check out the screenshots below for your reference.




Step 2: Adding Members to a Specific Team
Sometimes a project is so large that it’s split into multiple teams—like “Mobile App Team” and “Cloud Infrastructure Team.” Adding someone to the project isn’t enough; you need to put them where the work is happening.
The Walkthrough:
- Navigate to your Project Home Page.
- Click on Project Settings (bottom-left).
- Under the General category, select Teams.
- Click on the specific team name (e.g., Sprint Squad A).
- Click the Add button in the Members section.
- Search for Robert’s name (since he was added to the Org in Step 1, his name will auto-populate).
- Click Save Changes. Check out the screenshots below for your reference.




Managing Security Groups: Who Can Do What?
- Readers: Perfect for stakeholders who only need to see progress but shouldn’t touch the code or the tasks.
- Contributors: The “Goldilocks” zone for 90% of your team. They can push code, create work items, and run pipelines.
- Project Administrators: Reserved for the “Captains.” They can change project settings, delete repositories, and manage other users.
Troubleshooting: “I Can’t See the Repos!”
- Check Access Level: Is he a “Stakeholder”? Stakeholders cannot see Repos by default. Switch him to “Basic.”
- Check Group Membership: Is he in the “Readers” group by mistake?
- Conditional Access: If your company has strict security, he might need to be on the VPN or a managed device to see the code.
- License Expiration: If you are using a monthly Basic license and the credit card failed, he might have been downgraded to Stakeholder automatically.
Video Tutorial
Conclusion
Mastering user management in Azure DevOps is about balancing accessibility with security. By following the hierarchy—Organization > Project > Team—you ensure that every member is added to the team.
If you are just starting out, keep it simple: use “Basic” access and “Stakeholder” for viewers.
You may also like the following articles:
- How to get Project ID in Azure DevOps
- How to Abandon PR in Azure DevOps
- How To Recover Deleted Branch In Azure DevOps
- Azure DevOps What Is It
- How To Delete Pull Request In Azure DevOps

I am Rajkishore, and I am a Microsoft Certified IT Consultant. I have over 14 years of experience in Microsoft Azure and AWS, with good experience in Azure Functions, Storage, Virtual Machines, Logic Apps, PowerShell Commands, CLI Commands, Machine Learning, AI, Azure Cognitive Services, DevOps, etc. Not only that, I do have good real-time experience in designing and developing cloud-native data integrations on Azure or AWS, etc. I hope you will learn from these practical Azure tutorials. Read more.
