This article is also available in:

Tags

Within a complex organisational structure, tags can be used to trigger an alarm in some or all sub-organisations that was triggered in the parent organisation. All alarm data, such as text and coordinates, is retained.

Tags can be used across organisations in Scenarios, Alarm templates and Flows as part of the Tag Triggered trigger. In scenarios, tags can be defined as outgoing tags and incoming tags. In this context, incoming means that triggering the tag automatically triggers the scenario. Outgoing means that the scenario triggers the tag. This allows, for example, two scenarios from a parent and child organisation to be linked. If you set the tag as outgoing in the scenario of the parent organisation and as incoming in the sub-organisation, triggering the scenario in the parent organisation will automatically trigger the scenario in the sub-organisation. Alarm templates and the flow trigger cannot trigger a tag themselves. Alarm templates can only be triggered by a tag itself, and in the flow there is a separate element for triggering a tag called Trigger Tag.

In addition to being used in scenarios as outgoing tags, tags can also be addressed directly. This can be done via the GroupAlarm API interface, Flows in GroupAlarm, and manually from the tag overview and the Trigger Tag function. All manual triggers can be tracked in the Manual triggers area.

💡 Tags in GroupAlarm are an optional extension and can be added under Admin⁣ → Extension of your organisation. The extension is called Alerting of Sub-organisations.

❗️ If a tag is triggered multiple times within 24 hours in the same sub-organisation and with the same event name and alert text, all further triggers after the first trigger are discarded as duplicates.

Create tag

You can create a new tag under Configuration → Tags → Create Tag.

1️⃣ When creating a tag, you first have the option of specifying a name, description and colour for the tag for unique identification.

2️⃣ The Protect tag from use function prevents your connected sub-organisations from using the tag independently as an incoming tag. Instead, a request is sent to the parent organisation where the tag was created. You can then accept or reject this request under Configuration → Tags → Access requests. Once approved, the incoming tag is immediately assigned to the sub-organisation's scenario. When subsequently editing the scenario in the sub-organisation, no new access request is necessary as long as the incoming tag is not removed. Rejected requests can be resubmitted at any time by assigning the incoming tag again.

💡 To keep the parent and sub-organisations informed about these processes, emails are sent to the administrators when a request is made or a decision is made about a request.

3️⃣ The Restrict usage input field allows you to further restrict the use of the tag. The tag is then only available to the organisations selected here. If you do not enter an organisation, the tag is automatically available to all organisations.

Updated on: 06/03/2026

Was this article helpful?

Thank you!