Administering users, roles, and access permissions

Users are the base-level entity in BMC Release Process Management. Users access the system by logging on. The administrator creates users.

Users have one or many roles, such as Deployer or Coordinator. Users can also be part of teams and groups.

After you have created users, you can create groups to represent the functional groups in your organization, such as  “Quality Assurance” or “Database Admins.” A group is a logical management unit that is used mostly for reporting purposes. Groups can have up to two resource managers. A user with Site Administrator privileges can be a resource manager for a group. You can select groups while creating a step, request, or plan. If you set email notifications for requests, the email address that you provide while creating a group is used for notifications to users in that group. 

You can create a team that contains users, groups, or both. Different from groups, teams are collections of users (including users forming a group) with assigned roles and responsibilities. Teams have an interest in applications, and team members have different roles in different applications. The users forming a team can have access permissions for various applications. Users can also be assigned different roles for environments associated with these applications. Teams can have individual users as well as users forming a group (for example, Database Administrators, Developers) to allow access to particular applications or environments.

Users can have one or many roles, such as Deployer or Coordinator. For all users, the application access permissions are granted based on the user role. After you create a user, you can assign applications to that user. You can also assign different roles to the particular environments associated with these applications. Further, users have both a default role and a role for an application environment:

• The default role defines the access permissions for the tabs and the actions that can be performed on those tabs, such as viewing, creating, and updating entities on various tabs or pages. 
• The role for the application environment defines how the user can work with requests for these applications and environments.
• If the application role allows more access than the default user role, the default user role permissions are applied for this application.
• If the default user role allows more access than the application role, the application role permissions are applied for the application.

You can set the default user role for all accessible portfolio items when you add a new user. The following figure lists the available roles that you can assign.

Roles that you can assign to a user

The attached spreadsheet explains the permission levels available for the roles of a Coordinator, Deployer, Requestor, User, and Executor. The permissions available for these roles can be categorized into the following 3 levels:

• Tab access permissions define access permissions available for tabs for that particular role. In the spreadsheet, available access permissions are marked by an x. 
• Content access permissions define the permissions available for accessing the content related to requests, plans, calendars, projects, and so on. These permissions are defined according to the permission level assigned for the application and for the environment. Thus, by defining the application and environment for a particular role, you can restrict that role to viewing or performing actions on different tabs according to the application or environment for which that role has permissions. In the spreadsheet, access permissions are marked for every function. Available permissions are marked by the words By app/env, which means by application or environment. If permissions available depend on the default role, then you might find the words Assigned to. Availability of complete access permissions is marked by the word All.

• Permissions for actions define the actions that you can perform, including viewing, creating, or updating entities on various tabs or pages. In the spreadsheet, the actions are explicitly defined (for example, create request, or create server, or create application, and so on.

Related topics

Managing users

Managing teams

Managing groups