> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/channels/set-up-slack.md).

# Set up Slack

Install the Lleverage Agent in a Slack workspace and connect the workspace to your Lleverage organisation.

Slack is the simpler Agent-channel installation path. You authorize the Lleverage app through Slack rather than uploading an app manifest manually.

## Before you start

You need permission to configure Channels in Lleverage. Your Slack workspace may also require an administrator to approve new apps.

## Install the Agent

1. In Lleverage, open **Control → Channels**.
2. Choose **Slack** and start the connection.
3. Continue to Slack when prompted.
4. Select the Slack workspace you want to connect.
5. Review the requested permissions and authorize the Lleverage app. If your workspace requires app approval, complete that approval with a Slack administrator.
6. Return to Lleverage and confirm that the Slack workspace shows as connected.

There is no Teams-style manifest upload for the normal Slack setup.

## Configure where conversations run

After the workspace is connected, review its routing in **Control → Channels**.

![Connected Slack workspaces in Control → Channels, with controls to manage connections and route a channel to the current Project.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-4c87680ae32412ecd14bad65eb38d7463bf504ff%2Fslack-channels-admin-surface.png?alt=media)

By default, an organisation-level channel can resolve work from each person's own Lleverage access. You can pin a conversation to a particular project when the Agent should consistently use that project's context, Skills or Connections.

The Channels surface shows which Slack workspaces are connected and whether channels are currently routed to the Project. Use **Route a channel** when a shared Slack channel should consistently resolve to that Project; use **Manage connections** for the organisation-level workspace connection itself.

## Check the installation

Open Slack and find the Lleverage app. Start with a small, non-sensitive task in a direct message. If you use the Agent from a shared channel, mention or address the app in the conversation as appropriate for that Slack context.

If the Agent can respond but cannot use a project-specific capability, check the person's Lleverage project access and the channel routing before reconnecting the Slack workspace.

For day-to-day use, see [Agent in Slack](/run-operations/agent/agent-in-slack.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lleverage.ai/administer-and-govern/control/channels/set-up-slack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.