> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-communication/set-up-slack.md).

# Set up Slack

Connect Slack to Siit from the Integration library, authorize the right workspace, understand the permissions Siit requests, and ask a Slack admin for approval if needed

### Connecting Siit to Slack

We will start the process in Siit, so **log in to your Siit account first.** Then head to **Settings → Workspace → Integration library**.

This will bring you to an overview of available integrations, where you start the Slack authorization process by selecting **Connect** in the Slack App.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-258ead03fe54079ef2834a0cfda71ef1d7695985%2Fimage-png-Sep-24-2026-01-33-35-8537-PM.png?alt=media" alt=""><figcaption></figcaption></figure>

### Authorizing Siit for Slack

💁🏻‍♀️ Before you proceed, you need to be logged into the **right Slack workspace**!

* If you are not logged in at all and you see the Slack **login screen**, [**log in to Slack first**](https://slack.com/help/articles/212681477-Sign-in-to-Slack) **and then start the process from Siit again**.
* If you're logged in to multiple Slack workspaces you can always **switch using the button in the top right corner.**

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-1f38841d4a32d60b1d29914c61c75591a17b879c%2FCleanShot-2025-10-14-at-09-42-22-png.png?alt=media" alt=""><figcaption></figcaption></figure>

The overview above shows you all the permissions the Siit application is requesting. Let us explain why we need all of that...

### Why do we need these things to view?

* We need to know **content and info about you** and about **your workspace** to know who you are and associate your Slack account to your Siit organization.
* By giving us access to **info about your workspace**, we can keep Siit in sync with your organization, and recognize all the employees both on Slack and on e-mail.
* Similarly, we use the **information about the channels** to allow you to associate specific channels to teams in Siit to make submitting requests even easier

### Why do we need these things to do?

We need to be able to perform actions in **channels** and **conversations** to:

* **Install our @Siit App** and let it **receive messages in channels and direct conversations**
* **Send messages** to keep employees updated about the status of their requests
* Mark your replies as received with ✔️emoji reaction
* All threaded messages related to employee requests will be visible in the admin console
* Install **Slack** **actions** to make your life easier

💁🏻‍♀️ All of our communication is always done directly from our App. Siit will then post on behalf of the user in Slack

### Finishing installation

After authorizing the installation you will be redirected back to Siit, and you're all set. We will also **send you a message on Slack directly** to introduce ourselves and help you get started creating requests through Siit.

If you run into any issues, feel free to **reach out** and we'll make sure to sort it out for you.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-2ac1a53ff98f1bc1588183fe450860102d84ec3b%2F8767ecbb-Untitled.png?alt=media" alt=""><figcaption></figcaption></figure>

### Finding Siit

You can always find the Siit assistant in the **Apps section** of the Slack app. If it's not visible directly in the sidebar you can find it by clicking on the Apps heading and searching for Siit. Feel free to invite it to the relevant channels to make it easier for your employees to submit questions and requests.

💁🏻‍♀️ If you want to quickly switch to the **Siit App** just press `Cmd + K` (Mac) **or** `Ctrl + K` (Win) and type **"Siit"**

### Requesting permission to install

In case you are not allowed to install the Siit application into your Slack workspace, you will be prompted to submit a request to your workspace administrators.

​**Why is that?**

Some organizations allow all of their Slack users to install new Slack applications, while others don't and require the administrator to explicitly approve each application prior to installing it.\
​

**What should I do?**

Simply submit the **request to install** the Siit application to the administrators. It helps to provide a comment about what Siit is and why you need it.

Then, click on **Submit** and your administrators will receive your request.

​**What next?**

Once your request is approved, you will be notified on Slack by the Slackbot.

Then, **start the connection** **process** again from Siit and this time it will go through without a hitch!


---

# 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.siit.io/guides/integrations/integrations-communication/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.