Problem Definition

Deployment project and environment hierarchy is currently at least, unclear.

Where a user has environment permissions enabled but project permissions disabled, they will still be unable to access a deployment environment.

Source: Permissions for deployment environments

If the user has the View permission at the environment level but not at the project level, they cannot access the deployment environment which is consistent with the above documentation.

However if View is enabled at the Project level, the 'Edit' permission at the environment level takes precedence over the project Edit permission. I.E. If the user has Edit on the Environment but not on the Project, they can still Edit the environment which is not consistent with the behavior of the View permission.

From the Project permission UI:

Edit - Controls who can change the details of the project, related plan and any of the environment configuration. Users with edit permission can also create versions.

Suggested Solution

• Correct the permission precedence to work consistently or
• Amend the documentation to clearly state how it's currently meant to work.