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

# Use Slack with Aixy

> Connect your Slack account to AI agents with organization-controlled tool access.

Aixy's Slack connection gives AI clients access to authorized Slack tools through the official
Slack MCP server. Administrators choose the connection's audience and allowed actions. Each member
authorizes their own Slack account and workspace.

## Before you connect

* Have an [Aixy account](https://dash.aixy-gateway.com/) and ask an organization administrator to
  configure the Slack connection.
* Use a Slack application authorized for the intended workspace. Slack permits MCP access for
  internal apps and Marketplace-published apps; enabling public distribution alone does not meet
  that requirement. Workspace app approval policies also apply.
* Choose the Slack permissions and Aixy tools needed for your work. The default Slack scope,
  `search:read.public`, provides public-channel search. Other actions need their corresponding
  [Slack user scopes](https://docs.slack.dev/ai/slack-mcp-server/#oauth-scopes-needed-on-user-token-for-different-tools)
  as well as permission in Aixy.

## Configure the connection

1. Open **Agent tools → Manage available tools**. Find **Slack**, then select **Enable tool**,
   or **Manage** for an existing connection.
2. Choose organization-wide or project access and configure the authentication method shown in
   the editor. Follow its **Slack setup guide** for application registration and credential details.
3. Under **Organization tool permissions**, review the reference catalog and select the actions
   agents may use. The reference is partial and can omit actions such as public search. Actual tool
   availability depends on each account's Slack permissions.
4. Select **Save organization setup**, or **Save changes** for an existing connection.

For an action missing from the reference, verify its exact name against Slack's current tool
documentation or the Slack MCP server's authenticated tool catalog. Enter that name under
**Exact tool names (one per line)**, select **Add tools for review**, choose **Allowed** for the
reviewed action, and save the connection. Names must match Slack's tools exactly. The reference
catalog can be reviewed without connecting an account; it does not discover or authorize missing
tools for you.

For public-channel search, Slack's
[official search tool guide](https://github.com/slackapi/slack-skills-plugin/blob/main/skills/slack-search/SKILL.md)
documents `slack_search_public`. Add this exact name for review when using `search:read.public`,
then confirm that the authenticated Slack MCP catalog exposes it for your app and account before
allowing and testing it. The documented name alone does not establish runtime availability.

Organization setup and personal account authorization are separate. Selecting **Allow all current
and future tools** permits tools added later, so enable it only when that policy is intended.

## Connect your account

1. Open the Slack connection in **Agent tools** and select **Connect account**.
2. In Slack, choose the intended workspace, review the requested access, and authorize the app.
3. Return to Aixy and confirm that your account is connected.

Your grant is isolated by Aixy organization, connection, and user. Other members connect their own
accounts. An administrator's account does not supply access to other members, and an Aixy tool
permission cannot grant a Slack permission your account lacks.

## Verify the result

Connect an [external agent](https://docs.aixy-gateway.com/agent-tools/connect-agent.md), or use [Playground tools](https://docs.aixy-gateway.com/agent-tools/playground.md).
Discover the permitted Slack search action, search for a known test message in a public channel your
account can access, and verify the result against Slack. In Playground, review and approve the
proposed external action before it runs.

Inspect the action in [Activity](https://docs.aixy-gateway.com/observe/activity.md) to confirm its connection, status, and duration.
MCP call records exclude tool arguments, results, and credentials. Separately enabled model content
capture can include Slack content already sent to a model. A connected account or a reference
catalog alone does not establish that a permitted Slack action succeeds.

If Slack asks for administrator approval, complete that workspace's app approval process. If an
action is unavailable, check both **Organization tool permissions** in Aixy and the app's user
scopes and account permissions in Slack. Changes to authentication require members to reconnect.

## Disconnect and data use

Use **Manage** on your account connection to disconnect it. Administrators can pause the connection
with **Enabled for the organization**, or remove it and its saved accounts. Review the app's
authorization in Slack when removing upstream access as well.

Slack receives action arguments, and your AI client may send returned Slack content to its selected
model. Choose accounts, tools, and model destinations appropriate for the data. See Aixy's
[Privacy notice](https://aixy-gateway.com/privacy/) and
[data-processing settings](https://docs.aixy-gateway.com/administration/data-processing.md).

## Support

For connection help, email [hello@aixy-gateway.com](mailto:hello@aixy-gateway.com). Include the action's
request ID and a description of the problem; keep credentials and Slack message content out of
support requests. Privacy requests go to
[compliance@aixy-gateway.com](mailto:compliance@aixy-gateway.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.