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

# Configure Slack or Teams for partner activity

> Map internal channels to keep your team informed, choose which partner events post, and open shared channels with each partner for collaboration.

export const provider_0 = "Slack and Microsoft Teams"

A connected Slack or Microsoft Teams workspace does nothing until you tell Introw where partner activity should go. This guide turns the connection into a working notification and collaboration setup: an internal channel (or several) so your team hears about partner activity, the specific event types that should post, and a shared channel per partner so you and that partner can collaborate in chat. Do this once and the right people see the right partner updates without anyone checking Introw. The setup is identical for Slack and Teams; only the workspace differs.

## What you'll achieve

Internal channels that surface the partner events you choose, and shared partner channels where you and each partner collaborate, so partner activity reaches your team and your partners in the chat tool they already use.

## Before you start

<Steps>
  <Step title="Connect Slack or Teams">
    The chat integration must be connected first. See [Connect Slack](./connect-slack) or [Connect Microsoft Teams](./connect-microsoft-teams).
  </Step>

  <Step title="Confirm your Introw permission">
    You need permission to manage integrations in Introw to edit channel mappings and notification settings.
  </Step>

  <Step title="Create the channels you need">
    Create the internal and shared channels in Slack or Teams first. For a shared partner channel, invite the partner in your chat tool so the channel exists before you map it.
  </Step>
</Steps>

## Steps

### Inform your team with internal channels

<Steps>
  <Step title="Open the connected integration">
    Go to [Integrations](https://app.introw.io/settings/integrations?category=communication), then open the connected **Slack** or **Microsoft Teams** tile to reach its configuration page. The header shows **Connected by** and a green status when healthy.
  </Step>

  <Step title="Add an internal channel">
    Under **Internal channels**, map a channel that should receive notifications about your partners. Each row pairs a partner scope with a channel:

    * **Partner scope** - choose **All partners** to post every partner's activity to this channel, or pick one or more specific partners to keep a channel focused on just them. Use all partners for a general partnerships channel and specific partners for a high-touch account.
    * **Channel** - the internal Slack or Teams channel the activity posts to. Only non-shared (internal) channels appear here. If a private channel is missing, add the Introw app to that channel in your chat tool first, then reopen the list.

    Select **Add channel** to map more than one, for example a broad channel for all partners plus a dedicated channel for a strategic partner.
  </Step>

  <Step title="Choose which events post">
    On the right, **Notification Settings** controls which internal notifications are sent to your chat tool. Toggle the event types your team cares about, grouped by the kind of activity:

    * **Pipeline and deal updates** - turn on to post when a partner-linked deal changes stage or value, so your team sees movement in real time.
    * **Form submissions** - turn on to post when a partner submits a form, such as a deal or lead registration, so submissions are actioned quickly.
    * **Tasks** - turn on to post when partner tasks are created or change, so nothing is dropped.
    * **Other partner activity** - additional event types appear here based on your CRM object setup; enable the ones worth a notification and leave the rest off to avoid noise.

    Changes save automatically as you toggle them, and Introw confirms with a success message. These toggles control your team's internal notifications only; what posts in shared partner channels is managed in [Partner notifications](/features/partners/notifications).
  </Step>
</Steps>

### Open shared channels with partners

<Steps>
  <Step title="Add a partner channel">
    Under **Partner channels**, map a shared channel for collaboration and shared notifications with a specific partner. Each row pairs a partner with a shared channel:

    * **Partner** - the partner this channel belongs to. Pick the partner you collaborate with there.
    * **Shared channel** - the shared Slack or Teams channel that connects you and the partner. The partner must already be in the channel in your chat tool. This is where shared updates and partner-facing actions post for that partner.

    Select **Add channel** to map a shared channel for each partner you collaborate with in chat.
  </Step>

  <Step title="Confirm the mappings saved">
    Mappings save automatically as you set them, with a success message on each change. Review the **Internal channels** and **Partner channels** lists to confirm each row has both a partner (or scope) and a channel selected, since rows without a channel are ignored.
  </Step>
</Steps>

## Ask Introw in {provider_0}

Introw runs two AI agents inside {provider_0}, so partners and your team get answers
and take action without leaving chat. Both read live from your CRM source of truth
and act only within each person's own access - partners stay scoped to their portal,
your team stays scoped to theirs.

<CardGroup cols={2}>
  <Card title="Partner support agent - shared channels" icon="robot" href="/features/ai/partner-support">
    In a shared partner channel, partners just **@-mention Introw** to ask the same questions they could in the portal - deal status, commissions, tiers, content, or even registering a deal - and get an instant, scoped answer.
  </Card>

  <Card title="Internal agent - internal channels" icon="chart-line" href="/headless/agentic-use-cases/ecosystem-performance">
    In your internal channels, your team **@-mentions Introw** to get insight on the partner ecosystem and act on it - handle open form submissions, surface best-performing partners, check pipeline, and update partner records.
  </Card>
</CardGroup>

### Partners self-serve in shared channels

@-mention Introw in a shared partner channel and the [partner support agent](/features/ai/partner-support)
answers from your knowledge base and live portal data, scoped to that partner. It is the
same agent partners use in the portal, now in {provider_0}: it can answer questions in any
language and take action on the partner's behalf - register a deal, update a record, or
surface the right asset - without anyone on your team being pulled in.

### Your team gets ecosystem insight in internal channels

@-mention Introw in an internal channel and the internal agent answers questions about
your whole program and acts on it, scoped to your access - no portal hunt and no RevOps
ticket. For example:

* **Handle open work** - "Show me open form submissions," then approve, reject, or follow up on [deal and lead registrations](/features/forms/submissions-approvals) right from chat.
* **Spot what's working** - "Who are my best-performing partners this quarter?" to pull [ecosystem performance](/headless/agentic-use-cases/ecosystem-performance) on demand.
* **Update partners** - "Move Acme to Gold" or "add a note to this partner" to change partner records on the fly.
* **Check the numbers** - "What's this partner's pipeline and commission status?" for a live readout.

<Note>
  Both agents depend on the [partner support agent](/features/ai/partner-support) being
  enabled. Each agent only ever sees and does what the person talking to it is allowed to -
  partners are scoped to their own portal data, your team to your program.
</Note>

## Verify it worked

Trigger a partner event that matches an enabled notification, for example move a partner-linked deal to a new stage, and confirm the message posts to the mapped internal channel. For a partner channel, post or take a shared action and confirm it lands in the shared channel with that partner. The configuration page keeps your channel rows and event toggles as you left them.

## Related

<CardGroup cols={2}>
  <Card title="Connect Slack" icon="book-open" href="./connect-slack">
    Connect Slack before configuring it.
  </Card>

  <Card title="Connect Microsoft Teams" icon="book-open" href="./connect-microsoft-teams">
    Connect Teams before configuring it.
  </Card>

  <Card title="Partner notifications" icon="bell" href="/features/partners/notifications">
    Choose what partners receive in shared channels.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full configuration options.
  </Card>
</CardGroup>