Configuring the Incident Manager role - 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

If you need to add custom incident priorities and states, or change the incident state transition rules in your system, you can do so by configuring the Incident Manager role settings in Genetec Mission Control™.

What you should know

The Incident Manager is the central role that recognizes situational patterns, and triggers incidents in a Genetec Mission Control™ system. This role manages the automation workflows and keeps track of all user activities that are related to incidents.

The Incident Manager role is automatically created when you upgrade your Security Center system to Genetec Mission Control™, and is hosted by default on your main server. There can be only one instance of this role on your system.


  1. From the Config Tool home page, open the System task and click the Roles view.
  2. Select the Incident Manager role, and click the Resources tab.
  3. (Optional) Add secondary servers to the Incident Manager role to support failover.
    For more information, see Setting up role failover.
  4. Configure the Incident Manager database.
    The default database name is IncidentManagement. This database is used to store the configurations for the incident types and categories, and the incident activity trails.
    NOTE: The settings and incident icons of the Incident Manager role are stored in the Directory database.
  5. Click the Properties tab, and configure the general incident management settings:
    Retention period
    Specify how long you want to keep incidents in the system after they are closed. This value can be individually defined for each incident type.
    You can add custom values to the predefined incident priorities: Low, Medium, High, and Critical. Use the arrow buttons to change the order of the priorities. You cannot rename or delete the predefined priorities.
    Auto-assign mode
    Enable this option to let the system automatically assign incident management profiles to users when they log on.
    Document management
    You must configure the document location before you can add support documents for Genetec Mission Control™.
    Document API port
    Port (default=8083) used by the role to upload and download web documents.
    Document location
    Path to the Genetec Mission Control™ document library folder (\MCLibrary) on the server hosting the Incident Manager role. If you are setting up role failover, you must enter a network path that is accessible from all servers assigned to the role.
    Tip: If you use a shared network drive for documents related to incidents, when you copy incident configurations to a new system or restore the Genetec Mission Control™ database you need not recreate the document library.
    Open document trash folder
    The Trash folder () button is enabled only if you have deleted documents from your library. For auditing purposes, the system never deletes your documents. Documents that you replace or delete from the library are moved to the trash folder (\MCLibrary\Trash). If the document library uses a local folder on the Incident Manager server, you can only open the trash folder if you are running Config Tool on that server.
    Export settings
    You can configure the export settings for your incident.
    Branding image
    By default, the incident exports include the Genetec Mission Control™ logo. You can choose one of the following options to appear on your incident exports:
    No branding logo.
    Genetec Mission Control™ logo
    The default Genetec Mission Control™ logo.
    Custom logo
    Your own logo. You can click the folder icon and choose an image with 256 x 256 pixels or above in size. The image is resized to 300 x 300 pixels with the same aspect ratio.
    Location for exporting incident on close
    Set the folder path to save incidents exported automatically by the system when they are closed.
    NOTE: Default folder path: C:\ProgramData\Genetec Security Center <version>\
    Format for exporting incident on close
    Set one of the following file formats for incidents exported automatically by the system when they are closed:
    • PDF (default)
    • XML
    • HTML
    Trigger incident settings
    Choose one of the following time stamp options for incidents triggered manually in the Incident monitoring task:
    When incident is triggered
    When you click Trigger in the Trigger incident dialog box (default).
    When manual incident trigger dialog box opens
    When the Trigger incident dialog box opens after you click Trigger incident.
    NOTE: If you have users logged in to Security Desk, they must log off and log on again for the changes to take effect.
    Additional fields
    You can add additional fields to incident properties. Every additional field you add creates a corresponding custom column that can be enabled in the incident listing view in the Incident monitoring task in Security Desk.
    You can use these additional fields in the following ways:
    • Enable the system to automatically select a dynamic SOP step option.
    • As a parameter in the Conditional activities automation workflow activity.
    • As a filter criteria in the Incident report task.
    NOTE: Each additional field's name must be unique. If you delete an additional field, the corresponding custom column will also be deleted.
    Custom columns
    You can choose additional information you want to display in the Incident report task and the incident list view in the Incident monitoring task:
    Alarm context
    Display the context of a triggered alarm related to an active incident. This option is not selected by default.
    Tip: The alarm context field is populated only when an alarm is triggered using a macro or SDK.
    NOTE: Any additions to the Additional fields section would also be available as a custom column.
  6. Click the RabbitMQ tab, and configure the RabbitMQ settings:
    RabbitMQ is the message broker software used by Genetec Mission Control™ and other Security Center components.
    Your RabbitMQ web interface logon username.
    The password for your RabbitMQ web interface logon.
    The RabbitMQ server runs on your main server by default. If your RabbitMQ server runs on a different server, change it here. If you have set up a RabbitMQ cluster, add the IP address of all your RabbitMQ servers here.
    By default, RabbitMQ uses port 5671 for SSL communication.
    HTTPS API port
    By default, the web management SSL port is15671.
    NOTE: If you want to change the default port numbers used by Genetec Mission Control™, you must either change it during the installation process or change the port in the RabbitMQ.conf file. After modifying the RabbitMQ.conf, you must update the details here to match.
    NOTE: If RabbitMQ is not installed on the same server as the Incident Manager role, copy the RabbitMQ certificates to the Incident Manager server.
  7. Click the States tab, configure the incident states.
  8. Click the Events tab, specify the Security Center event types that will be processed by Genetec Mission Control™.


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.