> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/integrations/output-integrations/notifications/notifications.md).

# Notifications

Notifications in Reo.Dev enable you to **receive email or slack alerts** for activities across your accounts, developers or segments.

#### **Step 1: Configure Channel Preferences**

| **Channel**         | **Delivery Method**                   |
| ------------------- | ------------------------------------- |
| **Email**           | Receive notifications via email       |
| **Slack (DM)**      | Receive direct messages on Slack      |
| **Slack (Channel)** | Send notifications to a Slack channel |

* Turn on the toggle for Email to receive alerts on your email
* Turn on the toggle for Slack to receive alerts on slack DM or on a channel

{% hint style="info" %}
Note: To enable Slack notifications, you need to connect the Reo.Dev app to your Slack workspace if you haven’t already. [<mark style="color:$primary;">Here’s a guide on how you can setup Reo <> Slack Integration.</mark> ](https://docs.reo.dev/integrations/input-sources/owned-communities/slack)
{% endhint %}

To set up notifications on a slack channel, click on the slack icon near Send to Slack Channel Option.

<figure><img src="/files/47wyZ7vbysOtg7c0jASM" alt=""><figcaption></figcaption></figure>

Then, from the drop-down menu, **select the specific channel** on which you’d like to receive the notifications and click on **Share to Slack.**

<figure><img src="/files/tZbylC9AowIXEiFyNt21" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Important Note:**

* **Private channels are not supported** due to Slack’s restrictions on unapproved apps.
* Notifications can only be sent to **public channels** displayed in the dropdown menu.&#x20;
  {% endhint %}

#### **Step 2: Configure Activity Preferences**

Select the account activities for which you’d like to trigger notifications

<figure><img src="/files/YdKy6M3ChEbumRdzs13o" alt=""><figcaption></figcaption></figure>

Here’s a list of all activities you can receive alerts for:

| **Activity Type**          | **Options**                                           |
| -------------------------- | ----------------------------------------------------- |
| **GitHub Activity**        | Stars, Fork, Issues Created, Comments                 |
| **Documentation Activity** | Docs Review, Installation Initiated, Command Executed |
| **Website Activity**       | Page Visits, Key Page Visits                          |
| **Product Activity**       | Product Login                                         |

Once you’ve configured the channel and activities, click on ‘Save’ to turn on notifications.

<figure><img src="/files/odRsk060Qh2MV7rZBhmj" alt=""><figcaption></figcaption></figure>

#### **Set Up Alerts for Accounts, Developers, or Segments**

Once notifications are set up, you can turn on notifications to get alerts for specific accounts, developers, or segments.

**For Accounts:**

1. Click an **account name** from the list
2. Click **Enable Alerts** in the top-right corner

<figure><img src="/files/buBrVsRFx2V81bz7pIf4" alt=""><figcaption></figcaption></figure>

**For Developers:**

1. Click on any developer profile from the active developers tab within the account or the developers section
2. Next, click on **Enable Alerts**

<figure><img src="/files/RBvMVG0nNNUJJI2sZDdg" alt=""><figcaption></figcaption></figure>

**For Segments:**

Click on the bell icon to turn on segment notifications

<figure><img src="/files/aHMkFwkdBj37K3FNzVZy" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.reo.dev/integrations/output-integrations/notifications/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.