User guide

50
What is affected?
Release Paths
Only Release Paths accessible with the View or Edit permission for the user will be visible in the list. When a user
opens a Release Path which is not allowed in Edit, it will be in Read-Only and saving will not be allowed. If the user
is a release manager, all release paths will be visible and editable. Also, if the user is not part of a group that has
access to the Can Create Release Path security, the New button will not be accessible. The security tab is only
available when the current user is a release manager or if the current user is member of at least one group who has
the Manage Security permission.
Release Template Security
Introduction
The release template can be secured to control who can view, edit or manage security on them. Security definition of
the release template is a “most permissive” kind of security. For example, if a user is in 2 different groups and a
release template is accessible for one of the 2 group and not for the other group, this user will have access to this
release template. Also, keep in mind that if a user is a release manager, he will have access to view, edit and manage
security on all release templates. The manage security permission is used to delegate security management to other
groups in the system.
Prerequisites
Here are some prerequisites in order to use this security level:
 Security groups, Application Categories and Release Paths are defined.
Define Security
Define Security through Release Template
1. Navigate to Configure Apps, Release Templates.
2. Open or create a New Release Template (it is also possible to create a copy of an existing one).