Roles & permissions
The three roles of an organization (Owner, Admin, Member) and what each one can do in the web app.
An organization has three roles. Each role includes the rights of the roles below it: an Owner can do everything an Admin can, and an Admin everything a Member can.
| Role | Who | How many |
|---|---|---|
| Owner | The person who created the workspace, or who received ownership | Exactly one |
| Admin | People who run the organization day to day | Any number |
| Member | Everyone else; the default role | Any number |
The workspace is created by an Azure DevOps organization administrator (a member of Project Collection Administrators), who becomes its Owner. One Azure DevOps organization has one workspace.
Permissions
| Capability | Owner | Admin | Member |
|---|---|---|---|
| See repositories, reviews and members | Yes | Yes | Yes |
| Invite members, resend or revoke invitations | Yes | Yes | No |
| Change a member's role between Member and Admin | Yes | Yes | No |
| Remove a member | Yes | Members only | No |
| Connect or disconnect repositories | Yes | Yes | No |
| Manage the Azure DevOps access token | Yes | Yes | No |
| Change the membership policies (Configuration page) | Yes | Yes | No |
| See usage and billing, change plan, cancel, update the card | Yes | No | No |
| Configure BYOK (Business and Enterprise) | Yes | No | No |
| Transfer ownership | Yes | No | No |
Every member sees all the reviews of the organization, whatever their access in Azure DevOps.
Ownership
There is always exactly one Owner. Ownership cannot be given by invitation or by a role change: the Owner transfers it to another member, and the previous Owner becomes an Admin. See Members & invitations.
Commands in pull requests
@codingassist commands do not depend on the role: anyone who can comment on the pull request in Azure DevOps can use them.