> 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/balkanid-for-slack.md).

# BalkanID for Slack

## BalkanID for Slack

BalkanID for Slack brings access requests, review tasks, and risk alerts into Slack.

### Set up BalkanID for Slack

You must be a BalkanID administrator and Slack workspace administrator. Each BalkanID tenant connects to one Slack workspace.

1. Sign in to [BalkanID](https://app.balkan.id/) and select the tenant.
2. Go to **Configure → System Notifications**.

   <div data-with-frame="true"><figure><img src="/files/cH1CdM7ahltSsoPKouk9" alt=""><figcaption></figcaption></figure></div>
3. Under **Notification Channels**, select **Install BalkanID for Slack**. This will take you to the Slack page for installing a new app.&#x20;
4. Select your workspace and select **Allow**.

   <div data-with-frame="true"><figure><img src="/files/LApAPHnC2IXEeUyNHLwc" alt=""><figcaption></figcaption></figure></div>

You can find BalkanID for Slack under **Apps** in your Slack workspace after installation.

{% hint style="info" %}
BalkanID matches each Slack user to a BalkanID user by email address. The email addresses must match exactly — i.e., the user's primary slack email should match their user's employee email on BalkanID.
{% endhint %}

### Commands

Run `/help` in Slack to view all available commands.

* `/request-access` creates an access request. You can use this command to open an access request for yourself, or on behalf of another user. See [Access requests with BalkanID for Slack](/lifecycle-management/access-requests-with-balkanid-for-slack.md) and [Access requests](/lifecycle-management/access-requests.md) for more information.
* `/access-requests` lists access requests. Search, filter, and open request details.
* `/my-tasks` lists work awaiting your action. Filter by **Access requests & consent**, **Campaign reviews**, **Finding rules**, or **Unresolved comments**.
* `/purposes` lists purposes available in your tenant.
* `/my-purposes` lists purposes assigned to you.

`/access-requests` and `/my-tasks` are searchable and filterable across multiple dimensions such as requester, assignee, involved apps, etc. `/access-requests` shows your requests by default. Administrators, risk managers, and reviewers with broader visibility can view organization-wide requests. Each request shows the subject, requester, reason, duration, and requested date. `/my-tasks` always shows only tasks that are assigned to you.

### Home tab

Open the app’s **Home** tab in Slack to view your BalkanID identity and roles. The tab also links to the app’s **Messages** tab and the BalkanID web app.

It includes two personal widgets:

* **Your Access Request Tasks** shows up to five pending items.
* **Your Recent Access Requests** shows up to five requests you created.

### Notifications and actioning

Reviewers receive direct messages when their approval tier becomes active. Consent subjects receive direct messages when a request needs their decision. Notifications appear in the app’s **Messages** tab in Slack.

For access requests, reviewers can approve or deny individual line items. They can select **Approve All**, **Deny All**, or **Reassign**. Notifications identify the active tier for multi-tier reviews.

<div data-with-frame="true"><figure><img src="/files/T0wZcd12LsJpLmyrY7N8" alt=""><figcaption></figcaption></figure></div>

If enabled for your tenant, the request subject must grant consent before review begins. Denying consent closes the request permanently. Consent is skipped for self-requests.

Requesters and subjects receive a completion notification after a classic request is approved or denied.

You can use the `/my-tasks` command to go through older requests or campaigns that you've already actioned on, or to action on an older, incomplete review.

See [access requests with BalkanID for Slack](/lifecycle-management/access-requests-with-balkanid-for-slack.md) for the request flow. See [access review campaign notifications and reminders](/user-access-reviews/access-review-management/access-review-campaign-notifications-and-reminders.md) for campaign notifications. See [Findings daily alerts](/iam-risk-analyzer/findings/findings-daily-alerts-with-balkanid-for-slack.md) for risk alerts.


---

# 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/balkanid-for-slack.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.