This documentation applies to the 8.1 version of Service Desk, which is in "End of Version Support." You will not be able to leave comments.

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

Incident Management permissions

The following permissions are used in the Incident Management application.

Permissions

Description

Application user license type

Incident Master

Users with Incident Master permissions can perform the following functions:

  • Create incidents
  • Modify all incidents independently of any functional roles or support group affiliations
  • View Incident templates

    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.

      Recommendation: Limit the use of these permissions to individuals playing a Service Desk Analyst role who require full access to all Incidents.

      Users with these permissions must also belong to a Support Group before they can open the Incident form.

Fixed or Floating

Incident User

Users with 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

    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.

    Recommendation: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

      Users with these permissions must also belong to a Support Group to open the Incident form.

Fixed or Floating

Incident Submitter

Users with Incident Submitter permission can create and query all incidents. They cannot modify incidents.

Recommendation: 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

Users with Incident Viewer permission can:

  • 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: 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 (can create and modify all templates regardless of Authoring group affiliation)
  • Foundation component, for KPIs, configure:
    • Flashboard parameters
    • KPI titles (and register, this is an advanced option)
  • Requestor component:
    • Create and update Summary Definitions

      Recommendation: 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

Related topic

Adding a support staff person

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Laurent Matheo

    Hi (smile)

    I have a doubt about this sentence in "incident viewer":

    ////////////////////

    Users with these permissions must also belong to a Support Group to open the Incident form.

    ///////////////////

    I just tried for this thread (https://communities.bmc.com/communities/thread/81240?tstart=0) to access the incident form in ITSM 8.1 and I successfully accessed the incident form, and the people isn't in any support group.

    Apr 02, 2013 02:53
    1. Bruce Cane

      Hi Laurent, thanks for letting us know about this. I'll double-check the issue with our permissions expert and update the documentation accordingly.

      Apr 09, 2013 12:05
    1. Bruce Cane

      Again, thanks Laurent. I removed the statement about incident viewers needing to belong to a support group.

      Apr 09, 2013 03:31
  2. Laurent Matheo

    Cool, thanks a lot for the check ^_^

    Apr 10, 2013 01:07
  3. Sander Rijzewijk

    Hi,

    Similar to the problem mentioned in the earlier comment - the application permission "Incident Submitter" mentions the same:

    "Users with these permissions must also belong to a Support Group to open the Incident form".

    However, in both 8.1 and 8.1 SP1, I can open the Incident form and submit incidents for a (non-support-staff) Incident Submitter user that has no Support Group association without problems. So it may need to be reviewed if that condition needs to be removed from the documentation for 'Incident Submitter' as well.

    I also got feedback from a developer that any requirements listed for 'Incident User' permissions would come in addition to any requirements that may be listed for a 'lower' permission like 'Incident Submitter'. So should a user have both 'Incident Submitter' and 'Incident User' permissions assigned, at that point they will have to be a member of a Support Group to submit incidents (i.e. they can no longer submit Incidents without Support Group association as they would have been able to do if they only had 'Incident Submitter' permissions). It would be great if that could be reviewed (and if required documented) as well.

    Thanks,
    Sander


     

     

    Jun 17, 2014 04:21
    1. Bruce Cane

      Thanks for the comment, Sander. I'll see what I can find out for you. In the meantime, have you considered posting your question to BMC Communities?

      Jun 25, 2014 08:57