Release Management user roles and 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.
Permissions | Description | Application user license type? |
|---|---|---|
Release Master | 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 |
Release User | Users with Release User permissions can perform the following functions:
A user must have the Release Coordinator Functional Role to be able to modify the 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: Grant these permissions only to users performing a Release Coordinator role. | Fixed or Floating |
Release Viewer | 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 only to users who need only read access to view release requests. Typically, these permissions are given to most BMC Helix ITSM users (that is, users who do not already have the Master or User permission) for them to access information regarding release planning activities. | None |
Release Config | 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 |
Activity permissions
The Activity subcomponent is installed with all BMC Helix 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.
Permissions | Description | Application user license type |
|---|---|---|
Activity User | Users with Activity User permission can create and modify all activities. Users with either the Release Master or the Release User permissions also 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. | None |
Activity Viewer | 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. | None |
Activity Config | 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. | None |
Release coordinator role
Release coordinators use the Release Management application to monitor issues pertaining to the daily aspects of Release Management activities and how they can help their staff meet their commitments to the organizations they support.
The release coordinator in ITIL terminology is typically a member of the support staff who is responsible for the following release tasks:
Responsibility | Explanation |
|---|---|
Manages all aspects of the end-to-end release process | Makes sure the build and test environment team and the release team are coordinated. Establishes final release configuration, builds the final release delivery, and tests the final delivery before independent testing. |
Creates releases, change requests, and activities | Creates the release manifest that consists of change requests and activities, and reviews the RFCs if they have been passed on from BMC Helix ITSM: Change Management. Manages release, distribution, and the installation of packaged software. |
Submits the release request for approval | Configures the approval process to determine which approval phases are available for the release request. Note that whether a release request requires an approval is based on the organization's business rules. |
Plans and schedules the release | Organizes and facilitates the CAB meetings and schedules the release request. Determines the impact by assessing the different kinds of risks. Splits the requirements of releases into logical groups that can be handled efficiently by change coordinators. Prepares a business case for a new release when additional funding is needed for its implementation. Schedules people and resources to implement each task. |
Initiates the implementation of releases | Decides on corrective actions as needed. Estimates the costs of the release request. Coordinates release acceptance, rollout planning, release communications, preparations and training activities, and distribution and installation of releases. Provides management information about the Release Management quality and operations. |
Closes release requests | Organizes and conducts post-implementation meetings to collect improvement suggestions for future releases and resolves the release request when all the work is completed.. |
The release coordinator is usually responsible for addressing general, day-to-day issues from a personnel and customer satisfaction standpoint.
The release coordinator requires the following permissions and functional roles:
- The Release Coordinator functional role is required to be assigned as the Release Coordinator for individual releases.
- Membership in your company's support group is required to create release templates for that group.
- Release User permission is required for access to release and manifest records.
- Release Config permission is required to set up and modify the Release Module configuration forms.
The Release Coordinator user role is mapped to the following permission groups:
- Release User
- Incident User
- Problem User
- Infrastructure Change Viewer
- Contract Viewer
- Asset Viewer
- Knowledge Viewer
Comments
Log in or register to comment.