This documentation supports the 9.1 version of Remedy IT Service Management Suite.

To view the latest version, select the version from the Product version menu.

Incident Management permissions


Permissions

Description

Application user license type

Incident Master

On the System Settings form, if the Application permission model is set to Support group and company, a user with the Incident Master permission can perform the following functions:


  • Create incidents
  • Modify all incidents to which the Incident Master has access.
  • View Incident templates

However, if the Application permission model is set to Support group, a user must belong to a Support Group to perform the functions. For more information on the application permission model, see System Settings

Note: To create and modify templates, you need the Support Group Admin Functional role. With this role, the modification of templates is restricted to those for which the user is a member of the Authoring Group.

    • Configure:
    • Cost Category
    • Cost Center information
    • Cost Rate templates
    • Financial rules
    • Chargeback periods

      Note: Chargeback is a function of the costing sub-system and is given automatically with the other costing features, for example, access to the Product Catalog console.

      Use of the Master permissions groups should be limited to key personnel who either own a process or require full control of all Incidents.

Best Practice

We recommend that you limit the use of these permissions to individuals playing a Service Desk Analyst role who require full access to all Incidents.

Fixed or Floating

Incident User

On the System Settings form, if the Application permission model is set to Support group and company, a user with the Incident User permission can perform the following functions:

  • Create incidents
  • Modify incidents based on functional roles and support group affiliations (that is you must be a member or either the Assigned or Owner Group to have modify access to the Incidents with this permission)
  • View Incident templates

However, if the Application permission model is set to Support group, a user must belong to a Support Group to perform the functions. For more information on the application permission model, see System Settings .

Note: You must grant the Support Group Admin functional role to create and modify templates. With this role, template modification is restricted to templates for which the user is a member of the authoring group.

Best Practice

We recommend that you limit the use of these permissions to individuals playing one of the following Service Desk roles:

    • Group Coordinator
    • On-Duty Manager
    • Operations Manager
    • Operator and Specialist
    • Problem Coordinator,
    • Change and Release Coordinator
    • Service Level Manager
    • Service Owner

Fixed or Floating

Incident Submitter

On the System Settings form, if the Application permission model is set to Support group and company, a user with the Incident Submitter permission can perform the following functions:

  • Create incidents
  • Query incidents

However, if the Application permission model is set to Support group, a user must belong to a Support Group to perform the functions. Also, this user cannot modify incidents. For more information on the application permission model, see System Settings .

Best Practice

We recommend that you grant these permissions to individuals who need to submit and view incidents. Typically, these permissions are given to any who fulfills one of the roles mentioned under the Incident User permissions. User-type permissions are required if the person needs modification access.

None

Incident Viewer

User with the Incident Viewer permission can perform the following functions:

  • Query all incident requests
  • Add Work Info records
  • Update Work Info records

Users with Incident Viewer permissions cannot:

  • Submit incident requests 
  • Modify incident requests

Recommendation:

Best Practice

We recommend that you grant these permissions to individuals who need only read access to incidents. Typically, these permissions are given to most BMC Remedy ITSM applications users (that is, users who do not already have the Master, User, or Submitter permission) for them to access incident information.

None

Incident Config

Users with Incident Config permission can perform functions that span the following components:

  • Incident Management component, configure:
    • Management application settings
    • Incident Impact values
    • Incident Urgency values
    • Incident Priority weight ranges
    • Incident Prioritization
    • Incident rules (general field enforcement and assignment rules)
    • Work Info Inbound and Outbound communications counters
    • Decision Trees
    • Scripts
    • Incident Templates
      Note: The user can create templates regardless of Authoring group affiliation. However, a user can modify the template only if the user is a member of the authoring group or the support group for which the template is created.
  • Foundation component, for KPIs, configure:
    • Flashboard parameters
    • KPI titles (and register, this is an advanced option)
  • Requestor component:
    • Create and update Summary Definitions

Best Practice

We recommend that you grant these permissions to individuals who configure the component functions in the preceding list. Typically, people who fulfill this role are Application Administrators.

Fixed or Floating

Notes

  • Users with the Incident User permission and Support Group admin functional role can create or modify incident templates of the Support Group.
  • For information about data access in a multitenant environment and application permission model, see Data access in a multitenant environment .


Related topic

Adding a support staff person

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

Comments