> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/chatops/slack.md).

# Slack

Connect a Slack workspace to ilert, then receive alerts, raise them, and look up who is on call from your channels.

With the integration for Slack you receive alerts in Slack channels and act on them there, raise new alerts from a channel, and check who is on call — without opening ilert.

Connecting a workspace is a one-time step by an **Admin** or **Account owner**. After that, each capability below is configured on its own, and anyone who may create alert actions can use the connection.

## Connect your Slack workspace <a href="#in_ilert" id="in_ilert"></a>

{% hint style="info" %}
**Admin permission required**

Only an **Admin** or an **Account owner** can connect a workspace. Other roles do not see **Connectors** in the sidebar.
{% endhint %}

{% stepper %}
{% step %}

## Open the Connectors page

In the sidebar, go to **Settings** → **Connectors**. Under **ChatOps**, find the **Slack** card.
{% endstep %}

{% step %}

## Connect

Click **Connect**. ilert forwards you to Slack, which lists the permissions the ilert app asks for. Pick the workspace and confirm.
{% endstep %}

{% step %}

## Check the card

Slack returns you to the Connectors page. The **Slack** card now reads **Connected** and shows your workspace name underneath.

ilert shows no other confirmation, and a failed connection shows no message either — if the card still offers **Connect**, the connection did not happen. Start again, and see [what can go wrong](#what-can-go-wrong) below.
{% endstep %}

{% step %}

## Invite the bot to private channels

The ilert bot can post to any **public** channel without being a member. For a **private** channel, invite it first: mention `@ilert` in the channel and send the message, then click **Add Them**.

Invite the bot to public channels too if you want thread replies to become alert comments. Slack delivers message events only for channels an app has been added to, so posting alone does not give ilert the replies.
{% endstep %}
{% endstepper %}

## What ilert asks Slack for

Slack shows the permissions at the moment you connect. What ilert uses them for:

| Permission                             | Used for                                                                                                                                                            |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `chat:write`, `chat:write.public`      | Posting alerts and updating them in place, including in public channels the bot has not joined                                                                      |
| `commands`                             | The `/il-alert`, `/il-oncall`, and `/il-help` slash commands                                                                                                        |
| `users:read`, `users:read.email`       | Matching a Slack user to an ilert user by email address                                                                                                             |
| `channels:read`, `groups:read`         | Listing the channels you can pick in an alert action                                                                                                                |
| `channels:history`, `groups:history`   | Reading thread replies, which become [alert comments](/chatops/slack/post-alerts-to-a-slack-channel.md#comments-from-slack) — in channels the bot has been added to |
| `channels:manage`, `groups:write`      | Creating an [incident channel](/incidents-and-status-pages/incidents/incident-channels.md) and inviting responders to it                                            |
| `team:read`, `pins:read`, `pins:write` | Workspace details, and pinned messages in incident channels                                                                                                         |

## Keep the connection working

<details>

<summary>Update the bot when ilert asks for new permissions</summary>

When a new ilert feature needs a permission your workspace has not granted, the **Slack** card replaces **Connected** with an **Update** button and a warning icon. Click it and confirm in Slack. Alerts keep flowing while you do.

</details>

<details>

<summary>Re-connect after changing something in Slack</summary>

On the **Slack** card, open the **⋯** menu and choose **Re-connect**. Use this after the app was removed in Slack, or when the bot stops responding.

The same menu has **View alert actions using this connector**, which lists every alert action that posts to this workspace, and **Go to&#x20;*****your workspace*****&#x20;workspace**, which opens Slack.

</details>

{% hint style="danger" %}
**Disconnecting deletes your Slack alert actions.**

**⋯** → **Disconnect** removes the workspace connection and **every Slack alert action in the account**, immediately and without asking for confirmation. Alert actions that use a [Slack webhook](/chatops/slack/incoming-webhook.md) survive, because they do not use the connection. Alert sources keep working; they simply stop publishing to Slack. Recreate the alert actions after connecting again.
{% endhint %}

## Select your use case <a href="#in_slack" id="in_slack"></a>

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Post alerts to a Slack channel</strong></td><td>Publish alerts to a channel and accept, reroute, and resolve them there.</td><td><a href="/chatops/slack/post-alerts-to-a-slack-channel.md">Post alerts to a Slack channel</a></td></tr><tr><td><strong>Create alerts in Slack</strong></td><td>Let people raise an alert from a channel with <code>/il-alert</code>, with or without an ilert account.</td><td><a href="/chatops/slack/create-alerts-in-slack.md">Create alerts in Slack</a></td></tr><tr><td><strong>Look up who is on call</strong></td><td>Answer "who do I page?" in the channel with <code>/il-oncall</code>.</td><td><a href="/chatops/slack/lookup-who-is-on-call.md">Look up who is on call in Slack</a></td></tr><tr><td><strong>Post alerts with a webhook</strong></td><td>The fallback where you cannot install the ilert app: plain messages, no buttons.</td><td><a href="/chatops/slack/incoming-webhook.md">Post alerts with a Slack webhook</a></td></tr></tbody></table>

## What can go wrong <a href="#what-can-go-wrong" id="what-can-go-wrong"></a>

**One workspace, one account.** An ilert account can be connected to one Slack workspace, and a Slack workspace to one ilert account. Connecting a second one fails silently: you return to the Connectors page and the card is unchanged. Disconnect the existing pairing first.

**The connection was canceled in Slack.** Denying the permissions returns you to the Connectors page with the card unchanged, again without a message.

**The app was removed in Slack.** Alert actions remain in ilert but stop being delivered. Use **Re-connect**.

## FAQ <a href="#faq" id="faq"></a>

**Can I link multiple Slack workspaces to one ilert account?**

No, only one Slack workspace can be linked to an ilert account.

**Can multiple ilert accounts be linked to the same Slack workspace?**

No, a Slack workspace can only be linked to one ilert account at a time.

**Does everyone in Slack need an ilert account?**

No. Anyone in a channel can accept and resolve the alerts posted there. Every other button, and the restricted mode of `/il-alert` and `/il-oncall`, needs an ilert user whose username or email address matches the email address on the Slack account.


---

# 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.ilert.com/chatops/slack.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.