Slack integration overview

Last updated: August 5, 2026

Mutiny connects with Slack via a shared Slack integration, letting Mutiny send messages, respond in Slack, and help your team create and edit assets directly from Slack.

Choosing the right Slack workspace

Installing Mutiny in a Slack Enterprise Grid organization

Mutiny installs into one Slack workspace. If your company uses Slack Enterprise Grid, install Mutiny into the specific workspace where your team will use it. Mutiny declines an organization-wide install and asks an admin to install it into a single workspace instead.

You may still see Mutiny listed among your organization-level apps. That reflects how Slack lets the app be managed, not what it can access. Slack's own documentation is the best reference here:

  • Managing organization-ready apps

    Slack confirms these apps "do not have any additional privileges compared to an app installed at the workspace level alone", and are not added to any workspace automatically.

Mutiny only ever connects to the one workspace an admin connects from Mutiny. Other workspaces in your organization are not connected to Mutiny, and Mutiny receives nothing from them.

When you connect Mutiny to Slack, you'll choose the Slack workspace where you want Mutiny to be available. Mutiny is designed to be installed into a single Slack workspace, not across an entire Slack organization.

In Slack environments with multiple workspaces, make sure you select the specific workspace where your team will use Mutiny.

Shared vs Personal Slack integration

The shared Slack integration adds Mutiny to Slack as a bot. Once connected, anyone in your workspace can interact with the Mutiny bot directly in channels or direct messages. A Slack admin must approve the integration before it becomes active.

You can also install Slack as a personal integration via MCP, but this only allows one-way messaging from Mutiny to Slack. The bot will not be able to respond to questions or requests. For the full experience, use the shared integration.

How permissions work in Slack channels vs. Slack DMs

Mutiny handles permissions differently depending on where the conversation happens.

Slack Channels

Mutiny only has access to shared tools and shared assets. Private or user-specific assets are not available, so the bot will not expose private data when working in a shared channel.

Slack DMs

Mutiny can access the full set of tools and assets available to the person chatting with it, based on their Mutiny permissions. DMs are better suited for personal work, private assets, or tasks that require user-specific access.

How Mutiny Accesses Slack

Most of what this integration does runs through the Mutiny Slack app. A few capabilities work differently. Searching Slack, reading channel history, and browsing files all run using the Slack access of the person who connected the integration, because Slack only permits those actions through an individual account rather than a bot app.

That access is bounded in two ways. It applies only to the workspace that was connected, and it can never reach anything the connecting person cannot already see in Slack themselves. Channels they are not a member of and conversations they are not part of stay out of reach.

Creating and editing assets from Slack

Mutiny supports asset creation and editing from Slack as a shared capability.

Assets created from Slack are shared assets by default, making them available to the relevant team rather than staying private to a single user. Any asset created will be tied to the creator's identity. If the user is only a Slack user and not in the Mutiny instance, that will be shown under the account name in Mutiny.

Recommended setup

For the best experience:

  • Install Mutiny in the specific Slack workspace where your team will use it.

  • Connect the shared Slack integration so teammates can interact with the Mutiny bot.

  • Have a Slack admin approve the integration.

  • Use channels for shared team workflows.

  • Use DMs for personal or permission-specific work.

Limiting or removing Mutiny's access

An admin on your Mutiny account can adjust or remove Mutiny's Slack access at any time from Integrations → Slack.

Restrict who the agent replies to

Turn on Restrict to Mutiny users so Mutiny only responds to people who already have a Mutiny account. Everyone else gets a short note asking them to request access.

Limit what the agent can do

Under Tool permissions, set each Slack tool to Allowed, Needs approval (Mutiny asks you to approve each use), or Denied (Mutiny cannot see or use the tool at all).

Remove Mutiny from a channel

Remove the app from a channel in Slack, and it stops receiving messages there until someone invites or @-mentions it again.

Disconnect Slack entirely

Disconnect Slack from Integrations → Slack, or remove the app in Slack. Either way, the link between that Slack workspace and your Mutiny account is removed, and the agent stops responding.

These settings apply to the whole team, so they can only be changed by an admin. If you don't see them, contact an admin on your Mutiny account.

Need Help?

If you have questions or need help, the Mutiny Support team is here for you! You can submit a support ticket using the Submit a ticket button at the top of this page, or reach us at support@mutinyhq.com.