> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integration/slack-application-integration-setup.md).

# Slack Application Integration Setup

### Getting started <a href="#getting-started" id="getting-started"></a>

BalkanID recommends creating a separate service account for the purposes of this integration, instead of using personal or employee named accounts.&#x20;

Slack can be integrated to BalkanID directly from the UI via **oauth**. To configure Slack, you will need to be an administrator on the organization Slack account.&#x20;

### Configure Slack with your BalkanID tenant <a href="#steps-to-add-the-integration" id="steps-to-add-the-integration"></a>

1. Login to the BalkanID application and switch to the tenant you would like to add your integration to.
2. Head to *Integrations* > **Add Integration**, select **Slack.**<br>

   <figure><img src="/files/R76MG37Tyz4fWPCkLixD" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/4QnSgGdGfZxd0pmJRhr3" alt=""><figcaption></figcaption></figure>
3. Set up the *Primary Application owner (mandatory)* and the *Description*, if any. Set up Secondary Application Owner(s), if any. <br>

   Under **Direct Configuration**, you will see two options:

   1. **Bot Token:** Use this option if your Slack workspace is on a Free, Pro, or Business+ plan.
   2. **User Token:** Use this option if your Slack workspace is on an Enterprise Grid plan and you want to enable [Slack credential discovery](/getting-started/entitlement-data-discovery/credentials-discovery/slack-credentials.md). Clicking on this option will populate both Bot and User OAuth tokens.

   <figure><img src="/files/942qyKxGZ1wCmYRDx2gU" alt="" width="558"><figcaption></figcaption></figure>
4. This will redirect you to a page asking you if you want to install the application into your workspace. If there are multiple available workspaces, select the desired one from the drop-down and click on Install.
5. Click on next to move onto *Optional Configuration.*
6. Fill **Optional configuration,** if required. &#x20;

   <figure><img src="/files/YjfdaBpJtLkRllP9v3s0" alt="" width="563"><figcaption></figcaption></figure>
7. Once you filled in the information, click **Save**. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the *Integrations* page. When data is available, the integration Status will read **Connected** and the integration Message will read **Data available**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integration/slack-application-integration-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.