Project Admin Can't View Environments

Question

I have a user that is a member of Project Administrators in our project and I've granted Project Admin the Administrator role in Environments and he cannot view or create them.

Answer 1

If a user who is a member of Project Administrators and has been granted the Administrator role in Environments cannot view or create environments, there are a few things to check:

1. Role Assignment: Ensure that the user has the correct role assigned at the project level. The Administrator role should allow them to manage environments, but it's important to verify that the role is correctly applied.
2. Permissions: Check if there are any restrictions or additional permissions required for the user to view or create environments. Sometimes, even with the Administrator role, there might be project-specific settings that restrict access.
3. Access Level: Confirm that the user’s access level is appropriate for creating environments. Users with the Stakeholder role, for example, do not have permission to create environments.
4. Environment Visibility: If the environments are not showing up, it may be due to caching or loading issues. Encourage the user to refresh their view or check if the environments are hidden due to a large number of environments in the project.

If these checks do not resolve the issue, consider creating a support request for further diagnostics and assistance.

Answer 2

Refer to https://learn.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops

If you see the message Access denied: {User} needs Create permissions to do the action, go to Organization Settings > Users to check if you have the Stakeholder role. The Stakeholder role can't create environments because stakeholders don't have access to the repository.

---

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin