[comment]: # ({94201481-1b8c35fe})
# 1 Actions

[comment]: # ({/94201481-1b8c35fe})

[comment]: # ({aaee0901-a3e9781e})
#### Overview

In the *Alerts → Actions* section users can configure and
maintain actions.

The actions displayed are actions assigned to the selected event source
(trigger, services, discovery, autoregistration, internal actions).

To switch to a different event source, click on *Actions* in the *Alerts*
menu section. It is also possible to switch between sources by using
the title dropdown in the upper-left corner.

![](../../../../../assets/en/manual/web_interface/actions.png){width="600"}

Displayed data:

|Column|Description|
|--|--------|
|*Name*|Name of the action. Clicking on the action name opens the action [configuration form](/manual/config/notifications/action#configuring-an-action).|
|*Conditions*|Action conditions are displayed.|
|*[Operations](/manual/config/notifications/action/operation#configuring-an-operation)*|Action operations are displayed.<br>The operation list also displays the media type (email, SMS or script) used for notification as well as the name and surname (in parentheses after the username) of a notification recipient.<br>Action operation can both be a [notification](/manual/config/notifications/action/operation/message) or a [remote command](/manual/config/notifications/action/operation/remote_command) depending on the selected type of operation.|
|*Status*|Action status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.<br>See the [Escalations](/manual/config/notifications/action/escalations) section for more details as to what happens if an action is disabled during an escalation in progress.|
|*Info*|If everything is working correctly, no icon is displayed in this column. In case of errors, such as missing action operations or conditions after upgrade/low-level discovery, a warning icon is displayed. Hover over the icon to see a tooltip with the error description.|

To configure a new action, click on the *Create action* button in the
upper-right corner.

For users without Super admin rights actions are displayed according to
the permission settings. That means in some cases a user without Super admin
rights isn't able to view the complete action list because of certain
permission restrictions. An action is displayed to the user without
Super admin rights if the following conditions are fulfilled:

-   The user has read-write access to host groups, hosts, templates, and
    triggers in action conditions
-   The user has read-write access to host groups, hosts, and templates
    in action operations, recovery operations, and update operations
-   The user has read access to user groups and users in action
    operations, recovery operations, and update operations

[comment]: # ({/aaee0901-a3e9781e})

[comment]: # ({c252a236-c252a236})
##### Mass editing options

Buttons below the list offer some mass-editing options:

-   *Enable* - change the action status to *Enabled*
-   *Disable* - change the action status to *Disabled*
-   *Delete* - delete the actions

To use these options, mark the checkboxes before the respective actions,
then click on the required button.

[comment]: # ({/c252a236-c252a236})

[comment]: # ({1e414677-1e414677})
##### Using filter

You can use the filter to display only the actions you are interested
in. For better search performance, data is searched with macros
unresolved.

The *Filter* link is available above the list of actions. If you click
on it, a filter becomes available where you can filter actions by name
and status.

![](../../../../../assets/en/manual/web_interface/action_filter.png){width="600"}

[comment]: # ({/1e414677-1e414677})