> 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/getting-started/connect-slack.md).

# Connect Slack

Connect Slack so employees submit requests in chat and admins work from threads and the Siit inbox. Covers prerequisites, the permission scopes Slack requests, and Enterprise Grid

Goal: connect Slack so employees can submit requests in chat and admins can work from threads and the Siit inbox.

### Prerequisites

* Slack workspace admin privileges, or approval from an org admin if your directory requires it
* Siit admin access
* If your Slack is Enterprise Grid: know which workspaces need the app enabled

### Step-by-step

1. **Start the install**

* In Siit: [Settings → Workspace → Integration library](https://app.siit.io/settings/integrations/apps) → Slack → Connect
* You’ll be redirected to Slack’s permission screen<br>

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FwZ1hiUhPbUs6juEroTQg%2Fimage.png?alt=media&amp;token=fc22d5d7-9bce-4fd6-aa68-8d62149196bb" alt=""><figcaption></figcaption></figure>

2. **Approve permissions**

* Review and click *Allow*. Scopes shown by Slack may include:
  * commands (slash and global shortcuts)
  * chat:write (post updates to threads)
  * users:read, users.profile:read (map Slack users to Siit People)
  * channels:read, groups:read (list public/private channels you add the bot to)
  * im:write (bot DMs)

Note: exact scopes depend on features you enable; Slack displays the current list before install.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FtPehyuUM4GssPE6ssU1y%2Fimage.png?alt=media&amp;token=398fcc19-8435-4aad-ae70-160420600111" alt=""><figcaption></figcaption></figure>

3. **Enable request creation**

* Siit App : App Home: Open the Siit app in Slack → “New request”
* Message action: From any message, “More actions …” → “Create a Siit request”
* Optional channel:
  * Create or choose a channel (e.g., #ask-it)
  * Invite the bot: /invite @Siit
  * Pin a message with “Start a request via the Siit shortcut” so employees know how to submit

4. **Test your first request**

* Use the siit App → pick the service “App Access” → Submit
* You’ll see a thread in Slack; the request appears in the Siit inbox
* Reply in thread.

### **Post-install recommended setup**

* Rename the App
* Create a #siit-test channel for internal dry runs
* Share a short announcement with the shortcut link and when to use Siit vs ad-hoc DMs<br>

{% hint style="info" %}
Enterprise Grid notes

* Install to each workspace that should submit requests
* If your org restricts apps, ask a Slack Org Admin to approve Siit in the App Directory, then repeat the install per workspace
  {% endhint %}


---

# 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/getting-started/connect-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.
