> For the complete documentation index, see [llms.txt](https://help.radiantsecurity.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.radiantsecurity.ai/radiant-connectors/communication-tools.md).

# Communication Tools

Use Radiant Security’s communication tools to send notifications and messages to users through collaboration platforms such as Microsoft Teams or Slack. Notifications can be interactive approval requests for remediation and containment actions or global informational messages. These notifications help users stay informed and respond quickly to events triggered during a workflow.

### **Prerequisites**

* [ ] **Microsoft Teams** and **Slack** connectors (optional): If you’d like workflow notifications routed to these platforms, complete the respective onboarding steps:
  * Set up [Microsoft Teams notifications](/radiant-connectors/communication-tools/microsoft-teams.md)
  * Set up [Slack notifications](/radiant-connectors/communication-tools/slack.md)

{% hint style="info" %}
**Note:** By default, **email notifications** are enabled for all workflows and users. No additional set up is required for email notifications.
{% endhint %}

### **Configure notifications in a workflow**

To configure notifications after creating or editing a workflow in Radiant:

1. From the navigation menu, click **Workflows.**<br>

   <figure><img src="/files/T1JNGh6GufSifokqTSpw" alt=""><figcaption></figcaption></figure>
2. Choose an existing workflow or click **Create Workflow** to create a new one.
3. Once you've clicked into a workflow, you’ll see the workflow's **Trigger** and a list of **Steps**, which may include:
   1. **Interactive Tasks:** Include remediation and containment actions, such as resetting a password or disabling a user account. When a workflow runs, these tasks appear as approval buttons. By default, they require manual approval by a user. To enable automatic execution, select **Auto Execute** in the task's **Advanced Settings**.o
   2. **Direct Notifications**: Automatically sent to users each time the workflow is triggered. These notifications are generated from a predefined template and delivered via email, Microsoft Teams, or Slack.

### Configure notifications for an interactive task

To configure how approval requests are delivered for an interactive task:

1. Click any **Interactive Task** step to open its **Advanced Settings**.&#x20;
2. Enable **Requires approval** to send a manual approval request.\
   &#x20;![](/files/cpEbVSXBn6wSF6p6wsi2)
3. For **Wait For**, enter how long to wait for a response. When that period ends with no response, select whether the workflow should **Execute** or **Stop**.
4. For **Notification Type**, select a notification channel: Email, Slack, or Microsoft Teams.&#x20;
5. For **Template**, select the notification template.
6. Under **Recipient**, select the recipient to receive the notification.
7. Click **Save** and toggle **Active** on to enable the workflow.

### Configure a global notification

Global notifications are informational messages sent each time the workflow is triggered. They do not require any action from the recipient's.\
\
To configure a global notification:

1. In a workflow, click + **Add Step** > **Send Notification**.\
   &#x20;![](/files/XKI0N7Fktup8ZAvIRWy8)
2. For **Notification Type**, select a notification channel: Email, Slack, or Microsoft Teams.&#x20;
3. For **Template**, select the notification template.
4. Under **Recipient**, select the recipient to receive the notification.
5. Click **Save** and toggle **Active** on to enable the workflow.


---

# 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://help.radiantsecurity.ai/radiant-connectors/communication-tools.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.
