User guide

A1. SECURITY MANAGEMENT

Release Path Security

Introduction

The release path can be secured to control who can view, edit or manage security on them. Security definition of the

release path is a “most permissive” kind of security. For example, if a user is in 2 different groups and a release path

is accessible for one of the 2 group and not for the other group, this user will have access to this release path. Also,

keep in mind that if a user is a release manager, he will have access to view and edit all release paths. 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:

 In release management, Security groups, Stages and Application Categories are defined.

Define Security

Define “View” “Edit” and “Can Manage Security” through Release Paths

1. Navigate to Configure Paths, Release Paths.

2. Open or create a New Release Path

3. Choose the Security tab.

4. By default, the system’s reserved group named Everyone will have View, Edit and Manage Security

permissions. Since the security is “most permissive,” you will have to clear the View, Edit and Manage

Security permissions of this group to be able to control manually over other groups.