> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Omni for Slack

> Use the Omni Slack Agent to ask data questions and get work done in Slack, and deliver Omni content to Slack channels and DMs.

Omni's Slack app brings your data to where your team already works. Ask questions and get work done with the Omni Slack Agent without leaving Slack, or send Omni content to Slack from the Omni app. One app and one connection power it all.

## What you can do with Slack and Omni

After your [Slack workspace is connected to Omni](#connect), you can:

* [Schedule sending Omni content](https://docs.omni.co/share/deliveries/slack.md) to public and private channels and direct messages
* [Use the Omni Agent in Slack](https://docs.omni.co/integrations/slack/questions-commands.md) to ask data questions, work with routines, run skills, and more. You'll need to [link your Slack account with Omni](https://docs.omni.co/integrations/slack/connect.md#your-account) first.

> [!NOTE]
>
> Omni's AI responses can be inaccurate. Double-check your results before making any major decisions.

## Connecting Slack

To use Omni in Slack:

1. [**Connect your Omni organization to your Slack workspace**](https://docs.omni.co/integrations/slack/connect.md#organization). An Omni **Organization Admin** only needs to do this once.
2. [**Configure the Omni Slack Agent's settings**](https://docs.omni.co/integrations/slack/settings.md). Set the agent's default model and control whether its channel responses are private before you start using it.
3. [**Tell your teammates to connect their Slack accounts to Omni**](https://docs.omni.co/integrations/slack/connect.md#your-account). This allows them to interact with the agent by asking questions and using slash commands.

## Security and data access

The Omni Slack app has two layers of access:

* [**Slack scopes**](#scopes) control what Omni can do in your Slack workspace, such as read messages or send files
* [**Omni permissions**](#omni-permissions) control the data and content each user can get from the agent

This section explains both layers and how Omni handles your data.

### Slack scopes

When connecting Omni to your Slack workspace, your can deselect any of the optional scopes at Slack's authorization screen to install Omni with a reduced permission footprint. Required scopes can't be deselected — opting out of them prevents the integration from working.

Omni's Slack integration is installed as a single app, so this scope selection applies to everything Omni does in Slack.

> [tab] Required scopes
>
> The following scopes are **required** for the integration to function.
>
> | Permission | How Omni uses it |
> | - | - |
> | [`app_mentions:read`](https://docs.slack.dev/reference/scopes/app_mentions.read/) | Receives `@Omni` mention events |
> | [`channels:read`](https://docs.slack.dev/reference/scopes/channels.read/) | Lists public channels so you can pick one as a delivery destination |
> | [`chat:write`](https://docs.slack.dev/reference/scopes/chat.write/) | Sends messages to Slack |
> | [`commands`](https://docs.slack.dev/reference/scopes/commands/) | Registers and handles [`/omni` slash commands](https://docs.omni.co/integrations/slack/questions-commands#slash-commands) |
> | [`groups:read`](https://docs.slack.dev/reference/scopes/groups.read/) | Reads private channel metadata (only channels Omni is a member of) |
> | [`im:write`](https://docs.slack.dev/reference/scopes/im.write/) | Opens DM channels with users |
> | [`team:read`](https://docs.slack.dev/reference/scopes/team.read/) | Reads workspace metadata to identify the workspace and display its name in Omni settings |
> | [`users:read`](https://docs.slack.dev/reference/scopes/users.read/) | Lists workspace members by name and photo so you can pick delivery recipients |
> | [`users:read.email`](https://docs.slack.dev/reference/scopes/users.read.email/) | Matches an email address to a Slack user when you ask Omni to tag or notify someone |

> [tab] Optional scopes
>
> The following scopes are **optional** and can be deselected on Slack's authorization screen.
>
> > [!NOTE]
> >
> > Omni recommends keeping all scopes enabled for the best experience, but the **Impact if removed** column describes what changes if you opt out.
>
> | Permission | How Omni uses it | Impact if removed |
> | - | - | - |
> | [`channels:join`](https://docs.slack.dev/reference/scopes/channels.join/) | Auto-joins public channels so workspace members don't need to add Omni manually. Also used when [`/omni ask`](https://docs.omni.co/integrations/slack/questions-commands#omni-ask) is used in a public channel that Omni is not a member of. | **Scheduled deliveries to channels Omni isn't a member of will fail** until a workspace member adds Omni to the destination channel. |
> | [`files:read`](https://docs.slack.dev/reference/scopes/files.read/) | Lets Omni include a chart in an answer only the asker can see. | Private answers don't include the chart. |
> | [`files:write`](https://docs.slack.dev/reference/scopes/files.write/) | Uploads charts in AI answers, and dashboard images, PDFs, and CSVs in scheduled deliveries. | Scheduled deliveries in a file format (PDF, PNG, XLSX, CSV) are sent as a secure, expiring link (7 days) instead of a file attachment. Agent responses cannot include image or file attachments; users click **Open in Omni** to view visualizations or the full conversation. |
> | [`mpim:write`](https://docs.slack.dev/reference/scopes/mpim.write/) | Opens a shared group direct message when a routine or delivery messages several Slack users at once | Only one Slack user can be selected as a message recipient; selecting several people at once is unavailable. |
> | [`channels:history`](https://docs.slack.dev/reference/scopes/channels.history/), [`groups:history`](https://docs.slack.dev/reference/scopes/groups.history/), [`mpim:history`](https://docs.slack.dev/reference/scopes/mpim.history/) | Reads Slack message history so the agent can use thread and conversation context when answering | The agent answers only from the prompting message and cannot pull context from earlier messages in channels, threads, or group DMs. Omni recommends building robust context directly in your semantic model rather than relying on conversational history. |
> | [`im:history`](https://docs.slack.dev/reference/scopes/im.history/) | Reads Slack message history so the agent can use conversation context when answering, and lets Slack deliver direct messages to the agent at all | **Without this scope, Slack never delivers regular DM messages or thread replies within a DM to the agent.** Users must use [`/omni ask`](https://docs.omni.co/integrations/slack/questions-commands#omni-ask) for private queries. |

### Omni permissions

The Omni Slack Agent enforces the same [permissions](https://docs.omni.co/administration/users/permissions.md) and model-level access controls as the rest of Omni. Each user's access in Slack mirrors their access in the Omni app, meaning the agent can access the same data and content as the user. For example, if the user doesn't have permission to access a model or the ability to create routines, the Omni Slack Agent won't either.

The topics the Omni Slack Agent can use are controlled by the [`ai_chat_topics`](https://docs.omni.co/modeling/models/ai-chat-topics) model parameter, which is also honored by the [Omni Agent](https://docs.omni.co/ai/chat.md) and [embedded chat instances](https://docs.omni.co/embed/customization/ai-chat.md).

### Privacy and data handling

See the following for information about how Omni handles your data:

* [**Omni's privacy policy**](https://omni.co/privacy) - How Omni collects, uses, and protects your data
* [**AI data security**](https://docs.omni.co/ai/security.md) - How Omni's AI features, including the Omni Slack Agent, handle your data, which LLM providers Omni uses, and what data Omni shares with them. Omni doesn't use any data sent to LLMs for training.

## Getting help

Need help? Reach out to [Omni support](mailto:support@omni.co).
