> ## 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 Slack Agent settings

> Turn the Omni Slack Agent on or off, set its default model and response privacy, and reconnect or disconnect your Slack integration.

> [!NOTE]
>
> **Organization Admin** permissions are required to modify integration settings in Omni.

From the **Slack** tab in **Settings > Integrations**, you can turn the [Omni Slack Agent](https://docs.omni.co/integrations/slack.md) on or off, pick the model it uses by default, decide if agent responses are always private, and keep your Slack connection healthy.

## Enable the Omni Slack Agent

Turns the Omni Slack Agent on or off for your workspace. When the agent is off:

* `@Omni` mentions, DMs, and most `/omni` slash commands get a short reply that the agent is turned off, instead of an answer
* [`/omni disconnect`](https://docs.omni.co/integrations/slack/questions-commands#omni-disconnect) and [`/omni` or `/omni help`](https://docs.omni.co/integrations/slack/questions-commands#omni-omni-help) continue working
* Scheduled [Slack deliveries](https://docs.omni.co/share/deliveries/slack.md) and [routines](https://docs.omni.co/ai/routines.md) continue working

## Default model

Defines the default model the Omni Slack Agent uses when [answering questions](https://docs.omni.co/integrations/slack/questions-commands.md#ask-questions). Users can use other models they have access to and set their own default with [`/omni model`](https://docs.omni.co/integrations/slack/questions-commands#omni-model).

## Channel response privacy

Restricts how the agent's responses are shared within Slack channels and group direct messages. The **Require private responses** setting controls the default:

* **Disabled** (default) — Responses post to channel threads unless the prompting user has [private channel responses configured](https://docs.omni.co/integrations/slack/questions-commands.md#omni-privacy) (`/omni privacy`)
* **Enabled** — Users always receive a private response and can choose to share it with the thread

## Reconnecting Slack

If there are additional scopes to request or Omni's access token is invalid, a **Reconnect** button displays in the **OAuth scopes** section on the right side of the page. Click it to start a new authorization flow against the existing installation.

Use this to:

* Refresh an invalidated token
* Upgrade the app to support new features
* Grant previously skipped optional scopes

Unlike [disconnecting](#disconnect), scheduled deliveries, routines, and per-user account links aren't affected.

![Highlighted Reconnect button in the OAuth scopes section of the Slack settings page in Omni](https://docs.omni.co/integrations/images/slack-reconnect.png)

### Changing scopes after installation

[Reconnecting Slack](#reconnect) can grant additional scopes, but it can't remove them. Slack doesn't allow removing previously granted scopes from an existing installation.

To remove scopes, a user with the required permissions in both Slack and Omni must:

1. **Uninstall the Omni app from the Slack admin console.** This invalidates Omni's stored access token without deleting any deliveries, account links, or other resources in Omni.
2. **Reconnect the integration in Omni:**
   1. In Omni, navigate to **Settings > Integrations** and open the **Slack** tab. Because the token is no longer valid, you'll see an error.
   2. Click **Reconnect** to start a new OAuth flow.
   3. Select only the scopes you want on Slack's authorization screen.

On confirmation, Omni stores the new token. Your scheduled deliveries, per-user account links, and other Omni resources from the previous installation are preserved.

## Disconnecting Slack

> [!WARNING]
>
> **Don't disconnect Slack if you want to refresh the access token or change scopes.** Instead, [reconnect](#reconnect) or use the [scope-change procedure](#change-scopes).

Disconnecting doesn't uninstall the Omni app from your Slack workspace. To remove the app from Slack itself, a user with the required permissions must uninstall it from the Slack admin console.

**Disconnecting Slack is destructive.** This will:

* Delete [all Slack deliveries](https://docs.omni.co/share/deliveries/slack.md). To run them again, [restore them from the trash](https://docs.omni.co/share/deliveries.md#restore).
* Prevent selecting Slack as a [delivery destination](https://docs.omni.co/share/deliveries.md#destinations)
* Delete [all routines](https://docs.omni.co/ai/routines.md) configured to deliver to Slack
* Clear the links between users' Omni and Slack accounts. Users will need to [reconnect their accounts](https://docs.omni.co/integrations/slack/connect.md#your-account) before they can interact with the agent again.
* Stop the agent from responding to `@Omni` mentions, DMs, and `/omni` slash commands in your workspace

To disconnect, click **Disconnect** on the right side of the page. Confirm when prompted.

> [!TIP]
>
> Users can disconnect their individual Slack accounts with the [`/omni disconnect`](https://docs.omni.co/integrations/slack/questions-commands#omni-disconnect) slash command or on their [**Your account** page](https://docs.omni.co/administration/users/your-account.md#connected-services) in Omni.

## Next steps

* [Connecting Omni to Slack](https://docs.omni.co/integrations/slack/connect.md) - Connect your Slack workspace to Omni
* [Interacting with the Omni Slack Agent](https://docs.omni.co/integrations/slack/questions-commands.md) - Ask questions and use Slack slash commands to interact with Omni from Slack
* [Delivering content to Slack](https://docs.omni.co/share/deliveries/slack.md) - Schedule automated dashboard deliveries to Slack channels
* [Skills](https://docs.omni.co/ai/skills.md) - Build reusable, AI-powered processes that your team can trigger by name
