User guide

59
What is affected?
Release Paths
Only environments allowed by the selected stage type will be available in the Environment dropdown list. Also, if
the user does not have access to Edit Approvals and Environment permission, all stage information will be read-
only. If the user is a release manager, all information will be editable.
Release Templates
If the user does not have access to the Edit Values and Target Servers permission for a stage type, the information
of the Deployment Configuration and Configuration Variables tabs will be read-only for that stage type. If the user
is a release manager, all information will be editable.
Releases
If the user does not have access to the Edit Values and Target Servers permission for a stage type, the information
of the Deployment Sequence and Configuration Variables panel will be read-only for that stage type. If the user is a
release manager, all information will be editable.
Environment Security
Introduction
An Environment can be secured to control who can manage them (view, create or edit). Security definition of the
Environment is “most permissive.” For example, if a user is in 2 different groups and Can Manage Environment is
enabled for one of the 2 groups but not in the other group, the user will be considered to have the rights to manage
the environments. Also, keep in mind that if a user is a Release Manager, he is able to manage any Environment.