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

# Slack

> Real-time notifications, AI chatbot, and scheduled reports in your Slack workspace

Connect Chamber to your Slack workspace and never miss a beat — get real-time workload notifications, capacity alerts, AI-powered answers, and scheduled utilization reports delivered straight to the channels your team already uses.

## Why Slack?

* **Instant awareness** — Know the moment a workload fails, gets preempted, or completes without watching the dashboard
* **Smart channel routing** — Route different notification types to different channels so the right people see the right alerts
* **Personal control** — Every team member decides what they get and how (channel post or DM)
* **AI chatbot** — Ask Chamber questions in plain English right from Slack and get answers about workloads, GPUs, capacity, and costs
* **Automated reports** — Daily or weekly utilization digests posted to any channel, on your schedule

## Connect Your Workspace

<Info>Connecting Slack requires **Org Admin** permissions.</Info>

<Steps>
  <Step title="Open Integrations">
    Navigate to **Settings → Integrations** in the Chamber dashboard.
  </Step>

  <Step title="Click Connect Slack">
    Click the **Connect Slack** button. You'll be redirected to Slack's authorization page.
  </Step>

  <Step title="Authorize Chamber">
    Review the requested permissions and click **Allow**. Chamber needs access to read channels, post messages, and look up users.
  </Step>

  <Step title="Select a Default Channel">
    Pick a default channel for notifications. You can override this per notification category later.
  </Step>

  <Step title="Verify the Connection">
    Click **Send Test Message** to confirm everything works. You should see a test notification in your selected channel.
  </Step>
</Steps>

## Notification Types

Org Admins control which notification types are active at the organization level. Here's everything Chamber can alert you about.

### Workload Notifications

| Event                       | Description                                               | Default |
| --------------------------- | --------------------------------------------------------- | ------- |
| **Workload Status Updates** | Notifies when workloads start, complete, or are cancelled | On      |
| **Workload Failures**       | Alerts when a workload fails with error details           | On      |
| **Preemption Alerts**       | Notifies when elastic workloads are preempted             | On      |
| **Queue Position Updates**  | Updates when a queued workload's position changes         | Off     |

### Capacity Alerts

| Event                      | Description                                         | Default |
| -------------------------- | --------------------------------------------------- | ------- |
| **Utilization Alerts**     | Warns when GPU utilization is unusually low or high | On      |
| **Reservation Expiration** | Notifies before a capacity reservation expires      | On      |
| **Pool Capacity Warnings** | Alerts when a capacity pool is running low          | On      |
| **Clawback Opportunities** | Flags reclaimable underutilized reserved capacity   | Off     |

### Reports

| Event                        | Description                          | Default |
| ---------------------------- | ------------------------------------ | ------- |
| **Daily Utilization Report** | Daily summary of GPU usage and costs | Off     |
| **Weekly Cost Report**       | Weekly cost breakdown with trends    | Off     |

## Channel Routing

By default, all notifications go to the channel you selected during setup. Override this per category to make sure alerts reach the right audience.

**Available categories:**

* **Workload Notifications** — Workload events (started, completed, failed, preempted, queue changes)
* **Capacity Alerts** — Utilization warnings, reservation expirations, pool capacity, clawback
* **Reports** — Daily and weekly scheduled digests

<Steps>
  <Step title="Go to Slack settings">
    Navigate to **Settings → Integrations → Slack → Channel Overrides**.
  </Step>

  <Step title="Set a channel override">
    Select a notification category and pick the target channel from the dropdown. Chamber lists all public and private channels it has access to.
  </Step>

  <Step title="Remove an override">
    Click the remove button next to any override to revert that category back to the default channel.
  </Step>
</Steps>

<Tip>
  A common setup: route **Capacity Alerts** to `#infra-alerts` for platform engineers, and **Workload Notifications** to `#ml-workloads` for ML engineers.
</Tip>

## User Linking

Chamber automatically maps your team members to Slack users by matching email addresses. This powers @mention notifications so individuals get pinged directly when their workloads complete or fail.

To trigger a sync:

1. Go to **Settings → Integrations → Slack**
2. Click **Sync Users**
3. Chamber matches emails between your Chamber organization and Slack workspace

After syncing, you'll see a count of linked users. Anyone without a matching email can be linked manually by an admin.

## Personal Notification Preferences

Every team member can customize their own Slack notifications without affecting anyone else.

Navigate to **Settings → Integrations → Slack → My Preferences** to configure:

| Setting                    | Options                           | Default |
| -------------------------- | --------------------------------- | ------- |
| **Enabled**                | On / Off                          | On      |
| **Delivery Method**        | Channel post / Direct message     | Channel |
| **Mention Me**             | Include @mention in channel posts | On      |
| **Workload Failed**        | Notify on failures                | On      |
| **Workload Preempted**     | Notify on preemptions             | On      |
| **Workload Started**       | Notify on starts                  | Off     |
| **Workload Completed**     | Notify on completions             | Off     |
| **Workload Submitted**     | Notify on submissions             | Off     |
| **Workload Queued**        | Notify on queue entry             | Off     |
| **Queue Position Changes** | Notify when position changes      | Off     |

<Info>
  Personal preferences only apply to **your own workloads**. Org-level notifications like capacity alerts and reports are controlled by admins.
</Info>

## AI Chatbot

The Chamber Slack chatbot lets your team talk to Chamber directly from Slack. Ask questions in natural language and get instant answers about workloads, utilization, capacity, costs, and more.

<Warning>
  The AI chatbot must be enabled by an Org Admin. Go to **Settings → Integrations → Slack** and toggle **AI Chat** on.
</Warning>

### How to Use

* **Mention the app** in any channel: `@Chamber what's the GPU utilization for the training team?`
* **Send a DM** to the Chamber app for private queries
* **Reply in threads** to continue a conversation with full context

### Example Queries

* "What workloads are currently running?"
* "Show me GPU utilization for the last 24 hours"
* "Which team has the highest GPU spend this week?"
* "What's the queue depth for the research cluster?"
* "Why did workload `train-resnet-42` fail?"

### What the Chatbot Can Do

* Look up workload status, history, and failure details
* Report on GPU utilization and capacity across clusters
* Surface team and user activity
* Provide cost and spend breakdowns
* Draft and send emails on your behalf (with preview before sending)
* Link you directly to the relevant dashboard page

<Tip>
  Thread replies maintain full conversation context — ask follow-ups like "and what about last week?" without repeating yourself.
</Tip>

## Scheduled Team Reports

Set up automated utilization reports for specific teams, posted to any Slack channel on a daily or weekly cadence.

### Create a Report

<Steps>
  <Step title="Navigate to Team Reports">
    Go to **Settings → Integrations → Slack → Team Reports**.
  </Step>

  <Step title="Click Create Report">
    Select the team you want to report on.
  </Step>

  <Step title="Configure the schedule">
    Choose **Daily** or **Weekly**, set the delivery time, and for weekly reports, pick the day of the week.
  </Step>

  <Step title="Select a channel">
    Choose which Slack channel receives the report.
  </Step>

  <Step title="Choose metrics">
    Toggle which metrics to include in each report.
  </Step>
</Steps>

### Available Report Metrics

| Metric                    | Description                                 |
| ------------------------- | ------------------------------------------- |
| **GPU Utilization**       | Team GPU usage percentage and trends        |
| **Workload Success Rate** | Ratio of completed vs. failed workloads     |
| **Cost Breakdown**        | GPU spend by type, cluster, and user        |
| **Top Users**             | Most active team members by GPU usage       |
| **Queue Wait Times**      | Average and peak queue wait durations       |
| **Capacity Trends**       | Allocation and usage over the report period |

## Troubleshooting

<Accordion title="Notifications aren't appearing">
  1. Verify the integration status shows **Connected** in Settings → Integrations
  2. Check that the notification type is enabled at the org level
  3. Ensure Chamber has been invited to the target channel (for private channels)
  4. Click **Send Test Message** to verify the connection
</Accordion>

<Accordion title="Users aren't getting @mentioned">
  1. Run **Sync Users** to refresh email matching
  2. Verify the user's Chamber email matches their Slack email
  3. Check the user's personal preferences — **Mention Me** must be enabled
</Accordion>

<Accordion title="AI chatbot isn't responding">
  1. Confirm **AI Chat** is toggled on in the Slack integration settings
  2. Ensure the user has been linked via email sync
  3. The user must be a member of your Chamber organization
  4. Check that you're mentioning the app correctly (`@Chamber`) or DMing it directly
</Accordion>

<Accordion title="Reports aren't being delivered">
  1. Check the report status in **Team Reports** for error messages
  2. Verify the target channel still exists and Chamber has access
  3. Ensure the report is toggled **Enabled**
  4. Reports run at the configured UTC time — double-check your timezone settings
</Accordion>