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

# Messaging destinations and connection health

> Control Slack and Teams destinations for automated posts, test delivery, and manage installation health.

Messaging destinations define where Sofie automations may post in Slack or Microsoft Teams. You manage them in **Organization Settings** > **Integrations**, under **Messaging destinations**.

Connect [Slack](/admin/integrations/slack) or [Microsoft Teams](/admin/integrations/microsoft-teams) first. You need permission to edit integrations to change destination settings or run connection tests.

## Understand the three controls

| Control | What it allows |
| - | - |
| Organization installation | Connects the Sofie bot to a Slack workspace or Teams tenant. |
| Personal account link | Attributes a person's messages to their Sofie account. Slack also requires personal authorization for research and sending as that person. |
| Approved outbound destination | Allows automated bot posts to a specific conversation, subject to the actor's grant and approval policy. |

Mentioning Sofie discovers a destination. New destinations start inactive for automation. Turning on a destination does not connect a person's account or approve messages sent as their Slack identity.

## Activate a destination

<Steps>
  <Step title="Discover the conversation">
    Install or add Sofie to the intended channel or chat. Have a linked user mention Sofie there. Return to **Approved outbound destinations** in Sofie.
  </Step>

  <Step title="Enable the intended destination">
    Check the destination's provider and conversation identifier. Turn on the destination's switch only for conversations where automated updates should appear.
  </Step>

  <Step title="Allow your automations">
    Click **Allow my automations**. This grants your Sofie account access to use that destination for automated posts. It does not grant access to every user.
  </Step>

  <Step title="Choose the approval policy">
    The grant starts with **Approval each message** on. Keep it on when you want to review each automated message in Sofie.

    Turn it off only when you intend to allow posts under this grant without per-message approval.
  </Step>

  <Step title="Send a test">
    Click **Send test** and confirm that the test message appears in the intended conversation. This button posts a real message to the destination.
  </Step>
</Steps>

For Slack, you can also select **Choose installation**, enter a **Destination label** and Slack channel ID, then click **Add**. Use conversation discovery for Teams so Sofie has the correct destination information.

<Warning>
  Automated updates are visible to destination participants. Review the audience and content before allowing unattended posts. An approval policy for bot posts does not replace the user's approval for Slack messages sent as them.
</Warning>

## Check connection health

Under **Workspace and tenant connections**, each installation shows its health, linked-account count, discovered destinations, and available activity timestamps.

| Status | Next step |
| - | - |
| **Healthy** | Test a real conversation and any required outbound delivery before rollout. |
| **Not tested** | Run **Test connection** and send a user request. |
| **Needs attention** | Review the displayed error, repair the configuration, and test again. |
| **Reauthorization required** | For Slack, update app permissions if needed and use **Reauthorize Slack**. |
| **Disconnected** | Restore the provider installation before attempting delivery. |

**Test connection** checks provider authorization. It does not prove that every channel can receive messages. Use **Send test** on an active destination to check delivery to that conversation.

The overall **Connected** badge means at least one provider is usable. Check the individual Slack or Teams installation you intend to use. If **Setup incomplete** lists a shared chat connection issue, contact your Sofie administrator or TransferAI support.

## Stop automated posts

Turn off the destination's switch to stop automated delivery there.

To disconnect the whole Slack workspace or Teams tenant, click **Disconnect** on its installation. Complete the passkey confirmation if prompted.

<Warning>
  Disconnecting an organization installation affects all linked users. Sofie disables its outbound destinations and automation grants, removes personal links, and cancels pending Slack send requests. Reconnecting requires users to link again and admins to review destination permissions again.
</Warning>

Removing Sofie from a Teams conversation disables outbound access for that destination. A Slack app uninstall or bot authorization revocation disables the Slack installation. Manage the provider app separately if you also want to remove it from Slack or Teams.

## Troubleshooting

<Accordion title="A conversation is missing from the destination list">
  Confirm that Sofie is installed or added there. Mention Sofie once, then reopen the integration settings. For Teams, use discovery instead of entering a raw channel ID manually.
</Accordion>

<Accordion title="Send test is unavailable or fails">
  The destination must be active. Check the installation health, confirm that Sofie is still in the conversation, and verify that the destination belongs to the intended workspace or tenant.
</Accordion>

<Accordion title="An automation cannot post to an active destination">
  Activation alone is not enough. Confirm that the account running the automation has a grant for the destination. If per-message approval is required, complete it in Sofie.
</Accordion>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.