# Connect Slack for Your Partners

Connect your Slack workspace and map a channel to each partner, so Suger knows where to post co-sell activity, internal notes, and broadcasts.

---

## Overview

Most partner conversations already happen in Slack. Connecting Slack to Suger lets you keep them there: each partner gets a Slack channel, and Suger posts to that channel instead of asking your team to copy updates across by hand.

This page is the prerequisite for [Broadcasts](/prm/broadcasts/). A partner with no mapped channel is silently excluded from every broadcast audience — including **All partners** — so if a partner tells you they never received an announcement, check their channel mapping here first.

:::info
Changing these settings needs an Admin or Editor role. A read-only role still sees the controls, but the save is rejected. See [Account](/get-started/account/).
:::

:::warning
This page is for the selling organization. **Partner-side organizations** see a **Contact Sales** panel here instead of the configuration below — Slack channel setup is something the seller does for the partnership, not something the partner configures.
:::

## Connect Your Workspace

1. Go to **Suger Console**, then **Settings**.
2. Click **Partner**, then **Slack**.
3. If no workspace is connected yet, the page reads **Slack not connected.** with a **Connect Slack in Settings → Integrations** link. Follow it to authorize the Suger app in your Slack workspace, then come back here.

Once connected, the page header shows the connected workspace name.

![Settings → Partner → Slack — the connected workspace, the internal notifications channel with its Change button, and the partner channel table](images/43-slack-settings.png)

## Set the Internal Notifications Channel

The **internal notifications channel** is your own team's channel. Internal notes posted on co-sells are mirrored here — **never to a partner channel** — so your team can discuss a deal without the partner seeing it.

1. Find the internal channel card near the top of the page.
2. Click **Change**.
3. Search for a channel by name, or paste a Slack channel ID directly (for example `C0123ABCD`) if the channel doesn't appear in search.
4. Confirm your choice.

## Map a Channel to Each Partner

Below the internal channel card is a table of your partners and their Slack channels.

1. Use **Search partners…** to find a partner, or tick the connected-only filter to see just the partners that already have a channel.
2. On the partner's row, assign or edit its channel. The channel picker works the same way as the internal channel picker — search by name, or paste a channel ID.
3. To disconnect a partner, remove its channel mapping from the same dialog.

The table paginates with **Previous** / **Next** and shows the page you're on. Search and filtering happen in your browser, so they apply across every partner at once, not just the visible page.

:::info
The table loads at most **2,000 partners**. Past that it shows *"Showing the first 2,000 partners. The list is capped — use search to refine and find the partner you're looking for."* Search is the way through it.
:::

![The partner channel table — a search box and connected-only filter above rows showing the three channel states: Connected, Add bot to channel, and No channel](images/43-slack-settings.png)

### Channel Status

Each row carries one of three statuses:

| Status | What it means | What to do |
|--------|---------------|------------|
| **Connected** | Suger can post to the channel. | Nothing. |
| **Add bot to channel** | The channel is mapped, but the Suger bot is not a member of it, so posts will not land. | Invite the Suger app to that channel in Slack. |
| **No channel** | No channel is mapped to this partner. | Assign one, or accept that this partner is excluded from broadcasts. |

:::tip
**Add bot to channel** is the status worth watching. The mapping looks correct in Suger, and nothing errors — the messages simply never appear in Slack. Inviting the app to the channel fixes it.
:::

## What a Mapped Channel Unlocks

```d2
direction: right

slack: "Your Slack workspace\n(connected once)" { shape: rectangle }

internal: "Internal notifications channel" { shape: rectangle }

check: "Partner has a\nmapped channel?" { shape: diamond }

channel: "Partner's Slack channel" { shape: rectangle }
excluded: "Excluded — receives nothing" { shape: rectangle; style.stroke-dash: 3 }

uses: "Broadcasts\nCo-sell activity" { shape: rectangle }
notes: "Internal notes on co-sells" { shape: rectangle }

slack -> check: "for each partner"
check -> channel: "yes"
check -> excluded: "no"
uses -> channel: "posted to"
notes -> internal: "mirrored to your team only"
```

- **[Broadcasts](/prm/broadcasts/)** — one message sent to every mapped partner channel at once.
- **Co-sell activity** — posted to the partner's channel as it happens.
- **Internal notes on co-sells** — mirrored to your internal notifications channel only, never to the partner's.

## Scope and Limits

- **Slack only.** There is no Microsoft Teams equivalent for partner channels today.
- **One channel per partner.** Suger posts to the partner's mapped channel, not to individual partner contacts.
- **The bot must be in the channel.** Mapping a channel is not enough on its own — see the status table above.
- **Seller-side only.** Partner-side organizations see a Contact Sales panel here instead of the configuration.
- **The partner list is capped at 2,000.** Use search beyond that.