This documentation supports the 20.02 version of Remedy Change Management.

To view an earlier version, select the version from the Product version menu.

Task Management System permissions

While working on tasks, it is important to identify the task sub-component permissions that are required for working with the tasks.

Related topic

User roles and permissions for task management Open link

Task sub-component permissions

The Task Management System is a sub-component that is installed with the BMC Incident Management, BMC Problem Management, BMC Change Management, and BMC Service Request Management applications. The Task component is used with the other applications (for example, Incident, Change, and so on) to create a task that must be completed as a step in an overall process.

Permissions

Description

Application user license type

Task Administrator

Users with Task Administrator permissions can perform functions that span the following three settings areas.

  • Assignment settings
    - Configure Task Assignment mappings.
  • Integration settings
    - Configure applications that integrate with Task Management System.
    - Configure phase management functionality for those applications that integrate with Task Management System.
    - Configure Task Status and Status Reason values for application return codes.
  • Task Configuration settings
    - Configure Task Group Templates
    - Configure Task Templates
    - Configure Variable Templates

Best Practice: We recommend that you grant these permissions to Application Administrators.
The following three permissions groups grant some level of administration privileges similar to the Task Administrator permission:
- Infrastructure Change Config
- Release Config
- Work Order Config

Users with one of these three permissions might not need the Task Administrator permission.
The Activity Config permission grants the same level of administrative privileges. A user with this permissions does not need the Task Administrator permission.

None

Task Application Config

Users with Task Application Config permission can perform the following functions that span the following two components.

  • Foundation component
    - Register applications that use Command Automation Interface (CAI) (advanced feature)
    - Define commands, command parameters, and command parameter mappings for the CAI (advanced feature)
  • Task Management component (Integration settings):
    - Configure applications that integrate with Task Management System.
    - Configure phase management functionality for those applications that integrate with Task Management System.
    - Configure Task Status and Status Reason values for application return codes.

The Infrastructure Change Config, SRM Administrator, and the Command Event Master permissions also grant access to the CAI functions mentioned above.

Best Practices:

  • Typically, users only need the Task Application Config permission if they are extending or customizing the CAI plug-in, or if they are integrating another application to the Task Management system.
  • Users with Infrastructure Change Config, SRM Administrator, and the Command Event Master permissions do not need the Task Application Config permissions unless they also need access to the Task Management functions.
  • The Release Config, Activity Config, and Task Administrator permissions also grant access to the Task Management functions mentioned above. Users with these permissions do not need the Task Application Config permission unless they also need access to the CAI.

None

Task Manager

Users with Task Manager permissions have access to updated records.
The following permissions automatically inherit the Task Manager permissions:

  • Task Administrator
  • Infrastructure Change Master
  • Infrastructure Change User Incident Master
  • Problem Master

Best Practice: Users with any of these permissions do not need Task Manager permissions to use tasks.

None

Task Process Config

Users with Task Process Config permissions can perform these functions that span the following two components.

  • Foundationcomponent
    - Register applications that will use CAI (advanced feature)
    - Define commands, command parameters and command parameter mappings for the CAI (advanced feature)
  • Task Management components
    • Assignment settings:
      - Configure Task Assignment mappings
    • Task Configuration settings:
      - Configure Task Group Templates
      - Configure Task Templates
      - Configure Variable Templates

Typically, the Task Process Config permission is granted to users that need some of the functions given by Task Administrator permission. Review the Task Administrator function list to note differences between the two permission groups.

Best Practice: The Task Process Config permissions have similar access to the Task Management System as the Task Administrator permissions. Grant the Task Process Config permissions to Application Administrators.

None

Task User

Users with Task User permissions have access to updated records.

The following permissions automatically inherit the Task User permission rights:

  • Task Administrator
  • Infrastructure Change Submit
  • Infrastructure Change User
  • Infrastructure Change Master
  • Release Master, Release User
  • Activity User
  • Incident User
  • Problem User

Best Practice: Users with any of these permissions do not need the Task User permissions to access Tasks. Give the Task User permission to anyone who needs access to the Task System to update Tasks but who does not have any of the previously mentioned permissions.

None

Application based permissions

You must have the permissions described in the table below to view, create, or modify a task related to change request. You can open the task either from the parent request or your IT home page. Depending upon the permissions given to you by your administrator, you can perform these operations on a task.

User roles and permissionsOperations on the task
ViewCreateUpdate

Change manager, change coordinator or a member of the change manager or change coordinator support group with either of the following permissions:

  • Infrastructure Change Master
  • Infrastructure Change User

Important:

  • The assigned change coordinator or manager can modify the task information in a change request until the request reaches the Closed stage. However, if you are not the assigned change coordinator or manager, but a member of the change coordinator or manager group, the information can be modified only until the change request reaches the Planning in Progress stage.
  • If you have a user role other than a change coordinator or manager and if you have the Change Master permission, you can perform all the operations on a task.
YesYesYes
Change management user with Infrastructure Change Submitter permission.YesYesNo
Change management user with Infrastructure Change Viewer permission.NoNoNo

Was this page helpful? Yes No Submitting... Thank you

Comments