Slack integration overview

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

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.

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.