Home
Setup guide
Install and connect your Security Center SaaS application.
System automation
Threat level scenario: Gunman
A scenario for creating threat levels is in case of a gunman.

Pre-deployment guide
Review requirements, order, and activate your Security Center SaaS system.
Setup guide
Install and connect your Security Center SaaS application.
- Getting started
- User management
- Device management
- System automation
  - What is system automation?
    System automation in Security Center SaaS is a workflow to trigger actions based on schedules or events. It helps administrators manage repeatable tasks with less effort, so they can focus on higher‑value work.
  - Overview of automation entities
    To trigger a series of actions manually, on a schedule, or based on events in your system, you can set up automation entities.
  - Examples of system automation
    Administrators can use system automation to reduce effort when handling repeatable tasks in Security Center SaaS. These tasks include responding to device and security issues and performing routine system maintenance.
  - About events
    An event is a record of an activity or incident that occurred in the system. Security personnel can monitor events in real time and investigate them later. Events can also trigger automations in the system.
  - About schedules
    A schedule is an entity that defines a set of time constraints that can be applied to a multitude of situations in the system. Each time constraint is defined by a date coverage (daily, weekly, ordinal, or specific) and a time coverage (all day, fixed range, daytime, and nighttime).
  - Creating schedules
    To define a set of time constraints for a multitude of situations, such as when a user can log on to the system or when video from a surveillance camera can be recorded, you can create schedules and then apply them to specific entities.
  - Adding audio files
    You can add new audio files that can be played when users receive an alarm in Security Center SaaS, or used with the Play a sound action.
  - About automation entities
    An automation entity is a repeatable process in Security Center SaaS. It consists of two parts: a trigger that defines what starts the automation, and a response that defines the actions that follow.
  - Creating an automation entity
    Before setting up an automation, you must create it as an entity in Configuration desktop.
  - Configuring automation triggers
    When configuring an automation, you must first define what triggers it.
  - Configuring automation responses
    After you define the triggers, define the actions that run when the automation is triggered.
  - Advanced settings for automation entities
    Configure the automation’s scope, activation periods, and other advanced options on the Advanced settings page.
  - Adding automations to maps
    To allow Security Center SaaS operators to manually trigger automations directly from the maps, you can add automations to maps as map objects.
  - Event data
    Event data is the contextual information that accompanies every event. Event data can be used to add conditions to automation triggers and to contextualize automation responses.
  - Contextualized actions
    For event‑based automations, you can use data from the triggering event to contextualize the response actions. With contextualized actions, a single automation can handle multiple automation scenarios.
  - About threat levels
    A threat level is a predefined scenario that you activate for a specific area or the entire system to manage special situations, such as a business event or emergency evacuation. Activating a threat level triggers a series of actions tailored to the scenario. Deactivating the threat level returns the system to regular operation.
  - Defining threat levels
    To help your security personnel respond quickly to a specific scenario, you can define a threat level.
  - Threat level scenario: Fire
    A scenario for creating threat levels is in case of a fire.
  - Threat level scenario: Gunman
    A scenario for creating threat levels is in case of a gunman.
  - Converting event-to-actions to automations
    You can convert legacy event-to-actions to automations using the Automation task.
  - Converting scheduled tasks to automations
    You can convert legacy scheduled tasks to automations using the Automation task.
- Map design
User guide
Perform daily operations and monitor your facilities in the Security Center SaaS application.
Genetec ClearID
Set up and use ClearID in Security Center SaaS.
Federation
Set up and use Federation in Security Center SaaS.
Appliances
Install, configure, and use your cloud-managed appliances.
Troubleshooting
Get quick and easy access to troubleshooting content for Security Center SaaS.
Supported devices
Review the supported devices list.
Supported features
Review the supported features list.
Technical support
Learn how and where to find support to help you solve technical issues.
Glossary

Threat level scenario: Gunman

2026-02-13

A scenario for creating threat levels is in case of a gunman.

If a gunman or shooter is spotted, some actions that you want the system to respond with are the following:

Block access to where the gunman or shooter is from innocent bystanders.
Trigger an alarm.
Trigger a physical alarm on an intrusion detection area.
Add a bookmark to a camera recording.

A threat level for responding to a gunman or shooter could be configured as follows:

Threat level scenario for gunman in Security Center SaaS.

When an operator sets this threat level, the following actions are executed by the system:

A minimum security clearance is set. This reduces the mobility of the gunman, assuming the credential he holds has a security clearance lower than 3 (between 4-5).
Note:
This configuration assumes that only armed security personnel have a clearance level higher than 3 (between 0-3), and that security operators continue to monitor all doors so they can open them when necessary to allow innocent people to hide in secured areas that the gunman cannot access.
A bookmark called Gunman Suspected Onsite is added to a camera recording.
An alarm set to Gunman Alert is triggered.
A physical alarm set to Panic Alarm is triggered on an intrusion detection area.

When an operator clears this threat level, the following actions are executed by the system:

Normal access is restored to all cardholders by setting the security clearance to 7 (the lowest level).
A bookmark called Gunman Threat Level Ended is added to a camera recording.
The Panic Alarm on the selected intrusion detection area is silenced and the siren on the intrusion panel stops beeping. Depending on your intrusion panel and the type of alarm, this action might also acknowledge the alarm.