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

# Connecting Slack

The Slack app is the primary interface for your team to interact with Notara. This guide covers installing it, verifying it works, and common troubleshooting scenarios.

## Installing the Slack App

### If you signed up via Slack OAuth

You're done — the Slack app was installed as part of your account creation. The Notara bot will have sent you a welcome DM in Slack. Skip to [Verifying the Installation](#verifying-the-installation).

### If you signed up with email + password

1. In the Notara dashboard, navigate to **Settings → Workspace**.
2. Find the **Slack Integration** section and click **Connect Slack Workspace**.
3. You'll be redirected to Slack's OAuth authorization page.
4. Select the workspace you want to connect from the top-right dropdown.
5. Review the permissions Notara requests (detailed below) and click **Allow**.
6. Slack redirects you back to the Notara dashboard with a success confirmation.

## Permissions Notara Requests

During the OAuth flow, Notara requests the following Slack scopes:

| Scope               | Purpose                                           |
| ------------------- | ------------------------------------------------- |
| `app_mentions:read` | Detect when users tag `@Notara`                   |
| `channels:history`  | Read messages in public channels (where invited)  |
| `channels:read`     | List channels for configuration                   |
| `chat:write`        | Post messages and replies                         |
| `groups:history`    | Read messages in private channels (where invited) |
| `im:history`        | Read direct messages with the bot                 |
| `im:write`          | Send DMs (for approval notifications)             |
| `users:read`        | Look up user profiles                             |
| `users:read.email`  | Match Slack accounts to Notara accounts           |
| `reactions:write`   | Add emoji reactions (for acknowledgment signals)  |

These are the minimum scopes required. Notara never reads messages in channels it hasn't been explicitly invited to.

## Verifying the Installation

Once installed, verify the bot is active:

1. In Slack, find the **Apps** section in your sidebar. You should see **Notara** (or your configured bot name) listed.
2. Click on the app to open a DM. You should see a welcome message from the bot.
3. Type `hello` and press Enter. The bot should respond within a few seconds.

If the bot doesn't respond within 30 seconds, check the [Troubleshooting](#troubleshooting) section below.

## Customizing the Bot

By default, the bot appears as **Notara** with the Notara logo. To customize:

1. In the Notara dashboard, go to **Settings → Workspace**.
2. Under **Slack Bot**, update the **Display Name** to anything you prefer (e.g., your company name, "AI Assistant", "Sage").
3. Optionally upload a custom avatar image.
4. Click **Save**. Changes take effect in Slack within a few minutes.

> **Note:** The bot's Slack username (the `@handle`) is fixed at installation time and cannot be changed after the fact. Only the display name and avatar are customizable.

## Inviting the Bot to Channels

The bot can only read and respond in channels it has been explicitly invited to. There are two ways to invite it:

**Via Slack:** In the channel, type `/invite @Notara` (or your bot's display name) and press Enter.

**Via Dashboard:** Go to **Connect → Channels**, click **+ Add Channel**, select the channel from the list, and configure it.

See [Inviting the Bot to Channels](/notara-docs/getting-started/channels.md) for the full configuration walkthrough.

## Troubleshooting

### Bot is not responding

1. Check that the bot has been invited to the channel: type `/invite @Notara` and see if it says "already a member" or actually adds it.
2. Verify your BYOK key is still valid: go to **Settings → BYOK** and run the verification check.
3. Check your credit balance: if you've exhausted your monthly credits, the agent won't respond. Go to **Settings → Billing**.
4. Check the Notara status page or contact <support@notara.ai> if the issue persists.

### Bot installed in the wrong workspace

If you authorized the wrong Slack workspace:

1. In the Notara dashboard, go to **Settings → Workspace → Slack Integration**.
2. Click **Disconnect** to revoke the current connection.
3. Click **Connect Slack Workspace** again and select the correct workspace.

Note: disconnecting Slack does not delete any configured channels or libraries — only the Slack integration itself is removed.

### "Already installed" error

If Slack shows an error saying the app is already installed, it means another Notara account is already connected to that workspace. Each Slack workspace can only connect to one Notara workspace. Contact <support@notara.ai> if you believe this is in error.

### Bot stopped responding after a period of inactivity

Slack OAuth tokens can expire if not refreshed. Try reconnecting: **Settings → Workspace → Slack Integration → Reconnect**.


---

# 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://notara.gitbook.io/notara-docs/getting-started/slack-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.
