Assigning Users to Roles

Each process app contains roles with privilege assignments that control access to your release process. Roles also populate the various fields, such as Release Manager and Product Owner. Roles are provided for each of the participants described in Release Manager Participants.

Most process apps have dependencies on other process apps. To ensure users can seamlessly work with your entire release process, be sure to assign them to the appropriate roles as specified in the following table.

For example, deployment paths use logic and workflows from multiple process apps. To ensure your users have the proper privileges to work with deployment paths in turnovers, you must assign the users to the appropriate roles in Turnover, Deployment Path, Environments, Environment Schedule, and Path Elements projects. Users must also have all privileges for the Deployment Log table within the Turnover process app. Refer to Setting Privileges for the Deployment Log for more information.

Role Name	Applications Prefaced with RLM	Notes
Approvers	Approvals
Developers	Sample Development Task (if used) Environment Turnover	For environments, Environment Schedule project only For turnovers, grant role for Turnover and Deployment Path projects
Product Owner	Approvals Release Train Application Release Sample Business Request (If used) Sample Development Task (if used) Environment Turnover	For environments, grant role for Environments and Environment Schedules projects. For turnovers, grant role for Turnover and Deployment Path projects
Release Engineer	Approvals Release Train Application Release Environment Manual Deployment Task (if used) Runbook Turnovers	For environments, grant role for Environments and Environment Schedules projects. For turnovers, grant role for Turnover and Deployment Path projects
Release Manager	All RLM applications and projects

Along with roles specific to release participants, each process app contains these roles:

RLM Administrator
Intended for users who will administer the process apps, this role is assigned all application-based privileges. Users assigned to this role can also delete release elements, such as release trains and application releases.
RLM User
All RLM users should be assigned to this role. Users who have specific responsibilities, such as release engineers, need additional role assignments, as explained in the preceding table.

In addition, you can assign this role only to stakeholders who need visibility into your release process but do not actively work on release elements, this role is assigned view-only privileges.

Users and groups are assigned to roles in SBM Application Administrator.

Use the following general steps for establishing user accounts:

Determine the types of user accounts you need.
To better manage sets of users, log in to Application Administrator, and then create groups, such as "Release Engineers" and "Service Technicians."
Add accounts for each active user.
Assign users to the applicable groups you created. This will ease the process of assigning users to roles.
Assign groups to roles in each process app.

For guidance on each of these steps, refer to the Application Administrator online help or the SBM Application Administrator Guide located on the Documentation Center.

Note: For best results, non-administrative users should be assigned Regular User access.