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

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces.

# Connect Slack

> Connect your personal Slack tools and your organization's authorized Atlan link previews.

Slack has two separate connections in Atlan. Your personal connection supplies Slack tools through MCP Gateway. Your organization's workspace connection enables authorized Atlan previews in public Slack channels.

## Before you begin

Slack must be configured for your Atlan deployment. You can connect your own Slack account. An Atlan organization administrator must connect or change the shared workspace connection, and Slack may require workspace approval.

## Connect personal tools

1. Open the **Slack** app from Atlan's **Store**.
2. Under **Your Slack tools**, select **Connect your account**.
3. Finish the Slack authorization and return to Atlan.
4. Select **Refresh status** and confirm the connection is **Connected**.
5. Select **Open Slack tools**. In an MCP client, refresh the tool list and make a read-only Slack call.

Atlan registers the personal MCP server for this connection. Its tools depend on the current Slack catalog and the permissions you authorized. An organization workspace connection does not connect your personal tools.

## Enable workspace previews

1. As an organization administrator, open **Slack → Connections**.
2. Under **Share Atlan previews in Slack**, select **Connect workspace**. A framed app can offer **Manage workspace in browser** to complete this with organization management access.
3. Authorize the workspace and return to Atlan.
4. Select **Refresh status**. If **Preview permissions missing** or **Reconnect required** appears, reconnect and grant the required permissions.
5. Share a test link to an Atlan artifact you are permitted to share in a public Slack channel. Confirm the expected preview appears.

Preview creation still checks Atlan access. Eligible output files may be copied into Slack when file permissions are authorized. Slack retains those copies after Atlan access changes.

## Reconnect and disconnect

Use **Reconnect** when the app says authorization must be renewed. Disconnecting your personal account revokes its connection and removes its registered MCP server. Disconnecting the workspace stops Atlan previews; files already copied to Slack remain there.

For missing tools or refused calls after a successful connection, see [MCP Gateway errors](/gateway/mcp/troubleshooting).


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