This feature has not been released yet!
Actively monitoring cameras and keeping on top of their conditions quickly gets tedious if you have a lot of them. This is where alarms come in. They allow automating triggering certain actions when certain conditions are met. Both the actions and the conditions are highly customizable to give you the flexibility required to produce actually helpful results, and not just a mess of automated noise that nobody wants to look at.
...
One particularly useful aspect of actions is that their configuration can be extended for specific cameras, by users down to poweruser level. That is, lower tier users can add their own configuration to an action to suit their own needs, which will be executed in addition to the default configuration in the alarm. In other words, to take an email notification as an example, they can add their own email addresses to the list, and define their own subject and message text, but they cannot remove any recipients that are configured in the alarm itself, nor change the configuration of the message these recipients receive.
To learn more about the specific conditions, actions and their configuration, go here
General Configuration
The general configuration allows the adjustment of several parameters that are intrinsic to this alarm. This is a name and a description, which mostly serve that users can identify alarms quickly and determine what they are without having to look at the exact configuration. And then there’s a host of parameters that allow configuring when exactly the configured actions of the alarm should be executed, which takes a bit more explanation.
...