Scenarios
Scenarios allow you to map possible events or deployment scenarios. You can combine units according to an AAO or a hazard catalogue, for example.
Configuration
→ Scenarios
.The overview page for scenarios provides a list of all scenarios created so far. By default, you will see the ID of the scenario, the name and description, and which units are stored in the scenario. You can also access additional functions via the three dots next to a scenario. Furthermore, scenarios that have been locked for deletion are marked with a red padlock.
You can add or hide additional columns via the three lines above the list of scenarios. Additional columns available are checklists and incoming and outgoing tags.
To create a new scenario, select CREATE SCENARIO
.
1️⃣ For clear identification and later overview, you can add a name and a meaningful description to the scenario.
2️⃣ Using the Send assigned label to participant
function, your participants will automatically be notified of the assigned label by email. When alerting via the GroupAlarm App, this is also visible in the app.
3️⃣ You can assign a checklist to the scenario using the selection field for the checklists. These can then be processed in the event of an alarm. Details on the checklists can be found here.
4️⃣ In order to alert emergency services in a scenario, your participants must first be assigned units using labels. You can then organise these units in a scenario and alert them accordingly.
5️⃣ In the field for Incoming tags
, you can specify tags that should trigger this scenario. This means that if the specified tag is triggered in the parent organisation, the scenario in the suborganisation is automatically triggered.
In the Outgoing Tags field, on the other hand, you can define tags that should be triggered in other suborganisations when this scenario is triggered.
The use of an outgoing tag requires that you set the tag as an incoming tag in a scenario in your suborganisation or use the Tag triggered in a flow.
Further information on tags can be found here.
To get a theoretical overview of what an alarm would look like with the scenario, you can also call up a preview for each scenario. GroupAlarm then simulates a corresponding alarm and lists the participants who are eligible for the positions. This allows you to determine, for example, whether there are enough participants with the required qualifications before you trigger the scenario for the first time.
Updated on: 10/10/2025
Thank you!