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

# Bot for Slack

Boza Bot delivers notifications and interactive approval actions directly in Slack, so application owners and IT administrators can act on access requests, onboarding and offboarding tasks, and renewal reminders without leaving Slack.

{% hint style="info" %}
Slack is the collaboration channel for organizations whose identity provider is **Google Workspace**. Organizations on **Microsoft Entra ID** use [Microsoft Teams](/docs/integrations/bot-teams.md). The available channel is determined by the workspace identity provider and whether the corresponding bot is connected and deployed.
{% endhint %}

## What the Bot Does

* **Notifications** — automatic alerts for access requests, workflow tasks (onboarding and offboarding), and subscription renewals.
* **Quick approval and denial** — act on a task directly from Slack with one click.
* **Announcements** — when Slack is selected as a delivery channel for an [announcement](/docs/platform/announcements.md), it is sent to recipients in Slack.

Messages are sent as private 1:1 direct messages from the Boza Bot — never posted publicly in channels.

## Connecting Slack

1. Open **Integrations** from the main navigation.
2. Select **Slack** and click **Connect**.
3. Authorize Boza on the Slack screen and choose the workspace to connect.

Once connected, the Boza Bot is added to your workspace and begins delivering notifications.

{% hint style="info" %}
The app's **Super Admin** receives owner tasks (grant or revoke access, renewals); broader alerts go to administrators. Recipients get a direct message from the Boza Bot.
{% endhint %}

## Responding to a Task

When a task is assigned to you, the bot sends a direct message titled **"New Task"** that describes the action — for example, granting a user access to an application — and asks *"Would you like to complete this task?"*

1. Optionally type a **message** in the input field.
2. Click **Done** to complete the task, or **Deny** to decline it.
3. The bot replaces the message with a confirmation: *"Thank you for completing this task."*

Acting in Slack updates the request in Boza automatically — for example, moving an access request to **Accepted**.

## What You'll Be Notified About

* **Access requests** — when IT accepts a request, the app's Super Admin is asked to grant access.
* **Onboarding / offboarding** — each app owner is asked to grant or revoke access for the employee.
* **Renewals** — reminders ahead of a subscription's renewal date.

A task can also be **re-sent as a reminder** if it hasn't been actioned, prefixed accordingly.

## Troubleshooting

**Not receiving messages.** Confirm Slack is connected under **Integrations**, and that your Boza email matches your Slack account. Reconnect if the integration shows a connection warning.

**Done/Deny does nothing.** The task may already have been completed by someone else, or your session expired. Refresh Slack and try again, or check the request's status in Boza.

## Need Help?

If you have questions or run into issues, contact us at **<support@getboza.io>**.


---

# 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://boza.gitbook.io/docs/integrations/bot-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.