Release Management permissions
While implementing the Release Management application, it is important to identify the people in your organization who will need access to the Release Management application.
Release management permissions
The following permissions are available in Release Management.
Application user license type?
Users with Release Master permission can perform the following functions:
The use of the Master permissions groups should be limited to key personnel who either own a process, or have full control over Release Management schedules.
Fixed or Floating
Users with Release User permissions can perform the following functions:
A user must have the Release Coordinator Functional Role to be able to modify Release request and they must be a member of the Release Coordinator Group. The Asset Viewer and Infrastructure Change Viewer permissions are also granted automatically from the application UI when these permissions are granted.
Best practice: Limit the use of these permissions to users playing a Release Coordinator role.
Fixed or Floating
Users with Release Viewer permissions can query all release requests. They cannot submit or modify release requests.
Important: Infrastructure Change Viewer permissions are also granted automatically from the application UI when these permissions are granted.
Best practice: Grant these permissions to users who need only read access to view release requests. Typically, these permissions are given to most Remedy ITSM application suite users (that is, users who do not already have the Master or User permission) for them to access information regarding release planning activities.
Users with Release Config permissions can perform functions that span the following five components:
Best practice: Grant these permissions to users requiring access to configure the functions in the preceding list. Users with this set of permissions typically are Application Administrators.
Fixed or Floating
The Activity subcomponent is installed with all Remedy ITSM applications. However, it currently is used only by Release Management. The Activity subcomponent is used to manage a release and to track its progress from initiation to completion.
Application user license type
Users with Activity User permission can create and modify all activities
Users with either the Release Master or Release User permissions do need the Activity User or Viewer permission. These permissions grant full access to Activities.
Best practice: Grant these permissions to users working with the Release Management application who were not granted the Release Master or Release User permissions.
Users with Activity Viewer permission can view all activities
Users with Release Viewer permissions do not need the Activity Viewer permission. These permissions grant view access to Activities.
Best practice: Grant these permissions to users working with the Release Management application who have not been granted the Release Viewer permissions.
Users with Activity Config permissions can perform the following functions that span the following two components:
The Release Config permission grants full configuration access to the Activity configuration settings, with some exception regarding the Task Management settings. If a user does not need full access to the Task Management settings, do not grant them Activity Config permission if they already have Release Config permissions.
Best practice: Grant these permissions to users requiring configuration access to the component functions in the preceding list. Typically, you grant these permissions to someone playing the role of an Application Administrator.