Configuring incident states for Genetec Mission Control™ - Genetec Mission Control™

Genetec Mission Control™ Administrator Guide

Applies to
Genetec Mission Control™
Last updated
Content type
Guides > Administrator guides
Genetec Mission Control™
Administrator guides

You can modify the transition rules for the predefined states for incidents and add custom states to suit your specific needs, but you cannot rename or delete the predefined states.

What you should know

You can modify how the transition rules for incident states operate by changing the Accepted incoming states for each state. There is only one rule that you cannot change: the Closed state must be the final state. This means that it cannot be the incoming state of another state.


  1. On the Incident Manager role's configuration page, click the States tab.
  2. Do one of the following:
    • Click Add an item ().
    • Double-click an existing state.
    The State properties dialog box opens.

  3. (Custom state only) In the State name field, enter the name of the state.
    Predefined states cannot be renamed.
    The predefined incident states are:
    The incident has just been triggered and no activity is recorded. If using the default settings, you can change a new incident to In progress or Closed.
    In progress
    Actions are being taken for this incident. If using the default settings, you can change an incident from In progress to any other state.
    On hold
    The incident is paused. For example, you might do this if higher priority incident requires your attention, or if you are waiting for external information before moving forward with the procedure. If using the default settings, you can change an incident from On hold to any other state.
    The situation is resolved and ready to be closed. If using the default settings, you must complete all the steps in the standard operating procedure (SOP) before you can set an incident to Resolved. You can change the incident from Resolved to any other state.

    You need the Forcibly resolve incidents with incomplete SOPs privilege to resolve incidents without completing all the steps in the SOP.

    Everything that needs to be done for this incident has been done. If using the default settings, you must resolve an incident before you can close it. After an incident is closed, you can no longer make any changes to it. Closed incidents are removed from the Incident monitoring task, but all information remains available in the system for auditing, investigation, and analysis.

    You need the Forcibly close unresolved incidents privilege to close unresolved incidents.

  4. In the Allowed users list, choose the recipients that are allowed to set incidents to this state:
    • Specific list of users and user groups
    • Everyone
    If you leave this list empty, all users can set incidents to this state.
  5. Under Accepted incoming states, select one of the following options:
    Any state
    An incident in any state can transition to this state, except from Closed.
    Specific state
    From the list of existing states, select the ones this state can transition from.
    IMPORTANT: If you defined custom states, make sure you add them to the accepted incoming states of at least one other state. Otherwise, when an incident transitions to your custom state, it will not be able to transition out to another state.
  6. Click Save.


Watch this video to learn more. Click the Captions icon (CC) to turn on video captions in one of the available languages.

NOTE: Although we do our best to keep our videos current, the information presented in this video might become outdated with each new release. If you find anything wrong with this video, feel free to contact us.