> ## Documentation Index
> Fetch the complete documentation index at: https://doc.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Ask Ellie in Slack

> Connect Slack, map users, add the Entelligence bot to channels, ask a grounded question, and verify delivery.

Use Ellie in Slack when the question starts in a team conversation or when a result should be delivered to a channel or manager.

## Set up Slack

<Steps>
  <Step title="Connect the workspace">
    Open **Settings → Slack Notification** and connect the approved Slack workspace.
  </Step>

  <Step title="Add destinations">
    Add the Entelligence bot to every channel where it must read or post. Private channels require explicit membership.
  </Step>

  <Step title="Map users">
    Open the Slack mapping under **Settings → Team** and map Slack users to the correct Entelligence members.
  </Step>

  <Step title="Configure notifications">
    Choose the delivery scope and channel mapping required for the pilot. Avoid enabling every notification type at once.
  </Step>
</Steps>

## Ask a first question

In a pilot channel, ask a scoped question:

> For OWNER/REPO during the last 7 days, summarize merged pull requests and include source links. Do not create or update anything.

Verify the response against the Git provider.

## Slack commands and notifications

Workspace settings expose these notification families:

| Notification                        | In-app command label |
| ----------------------------------- | -------------------- |
| Pull-request summaries              | `/subscribe`         |
| Sprint reports                      | `/sprint`            |
| Leaderboard updates                 | `/leaderboard`       |
| Security pull-request notifications | `/security`          |
| Daily incident digest               | `/eku`               |

Use the command help presented by the installed Slack app for exact syntax and availability.

## Permissions and boundaries

* The Slack app can access only the workspace and channels authorized for it.
* Entelligence permissions and source permissions still limit the answer.
* Direct-message delivery depends on correct user mapping.
* A Reactor can listen to a channel and may initiate external work. Review its instructions and filters separately.
* Do not paste secrets, access tokens, or private source into a channel with broader membership.

## Verify

* The bot responds in the intended channel.
* A private channel is unavailable until the bot is added.
* Source links point to authorized systems.
* A direct report reaches the mapped user.
* Disconnecting or removing the bot stops future access or delivery as expected.

## Troubleshoot

| Symptom                           | Check                                                             |
| --------------------------------- | ----------------------------------------------------------------- |
| Bot does not respond              | Workspace connection, bot channel membership, and app permissions |
| Wrong person receives a DM        | Slack-to-Entelligence user mapping                                |
| Answer lacks source data          | Connector health and repository/project permissions               |
| Notifications reach wrong channel | Channel mapping and delivery selector                             |
| Duplicate messages                | Pulse, Reactor, and notification configuration overlap            |

## Next step

Create a scheduled [Pulse](/automations/pulse) or review [Ellie permissions](/ask-ellie/permissions).