# Alerts By default, BugBug is sending email notifications about [scheduled runs](https://docs.bugbug.io/running-tests/schedules) to all members of your [organization](https://docs.bugbug.io/collaboration/organization-settings). This makes sure that as soon as your app is not working as it should you will get an email alert. You can change this rule on the Alerts page: * when people get notifications * who will receive them You can also send additional notifications to email addresses who are not members of your organization, for example, clients or colleagues. {% hint style="info" %} Alerts are configured **per project**, each project has independent settings. {% endhint %}

## Adding a new alert to your project By clicking on the "**New alert**" button you can set up alerts related to a specific project.

### Choose when the alerts should be sent You can easily select when the alerts should be triggered by clicking and expanding the drop-down list in the "*When*" section. Available options: * Test started * Test finished * Suite started * Suite finished * Schedule started * Schedule finished

#### Along with other conditions, such as: * **Which suites/tests/schedules** - allows you to select various suites, tests, or schedules. * **Results -** "*Passed*" and "*Failed*" are selected by default, but you can also choose a third option - "*BugBug internal erro*r" that will send an alert when, for example, some technical issues occur on BugBug's side that could impact the test run results. * **Methods *****-*** contains "*Local browser*" and "*Cloud*" options to be selected, but this is dependent on your subscription plan settings. * **Profile** *- a* profile that was used in selected runs. * **Run by** *-* define what causes the run. Select between: "*Manually by a use*r", "*API*", or "*Automatically by scheduler*". * **Frequency** *-* define when you want to get an alert. Select between: * "*Every time*" - get an alert always when the trigger with the given parameters occurs. * "*Only once when the result changes*" - reduce the noise. Don't get alerts if the result is the same as the previous one. For example, if the result is failed 5 times in a row, you will only get an alert the first time. {% hint style="info" %} Remember that these fields will change based on what type of event you will select in the "When" section from the listed options. {% endhint %} ### Set what type of action should be executed\*

Currently you can choose one of those options: * [Send email notification](https://docs.bugbug.io/collaboration/alerts/sending-email-notification) * [Send webhook](https://docs.bugbug.io/collaboration/alerts/sending-webhook) * [Send Slack message](https://docs.bugbug.io/collaboration/alerts/sending-slack-message) * [Send Teams message](https://docs.bugbug.io/collaboration/alerts/sending-teams-message) {% hint style="info" %} **\*Note:** More will come soon, such as: creating a Jira ticket and sending a notification to other team communicators like Discord, etc. {% endhint %} *** ## Alerts list and management Having all the data filled you can add your alert by clicking on the "**Create alert**" button to see it on the list.

### Manage your existing alerts From this level, you can easily manage your listed alerts. From enabling or disabling to duplication them with a few clicks. Editing is also possible - just simply click on a listed alert's box.

{% hint style="info" %} Click on the toggle button to enable/disable each alert. {% endhint %} Click on the "**...**" to display the drop-down menu and select between available options: * Edit * Duplicate * Delete

If some alerts aren't needed anymore and you want to tidy your list, just simply delete the selected item.