---
title: "Connect Slack"
description: "Connect your organization's Slack workspace, then verify delivery from a Judgment workflow."
sidebar:
  label: "Connect Slack"
seo:
  title: "Connect Slack | Judgment How-to"
  description: "Set up an organization-level Slack connection for automations, production issues, and scheduled Background Agent results."
---

Connect Slack once for your Judgment organization, then choose destination
channels in the project workflows that should send messages. Connecting a
workspace alone does not enable an alert or schedule.

## Prerequisites

- Admin or owner access to the Judgment organization
- Permission to authorize the Judgment app in the intended Slack workspace
- A project workflow whose delivery you can verify

## Connect the workspace

1. Select the intended organization and open **Settings > Connections**.
2. In the **Slack** section, select **Connect**.
3. Complete the Slack authorization flow for the intended workspace. Follow
   any workspace approval requirements shown there.
4. Return to **Connections**. Confirm the **Connected** badge and the workspace
   name and domain, when displayed.

This connection belongs to the organization. Projects in that organization
use it when selecting Slack destinations; switching projects does not create
a separate workspace connection.

## Enable and verify delivery

Choose the workflow that should send a message:

| Workflow | Configure next |
| --- | --- |
| [Automation](/documentation/monitoring/automations-and-alerts) | Add **Notify on Slack**, choose channels, and configure the condition, frequency, and cooldown. |
| [Production issues](/documentation/monitoring/production-issues) | Configure Slack delivery in issue detection settings. |
| [Background Agent](/documentation/background-agents#deliver-scheduled-results-to-slack) | Enable a scheduled trigger, then **Send output to Slack** and choose channels. |

Save that workflow's settings. Verify an eligible event or scheduled run in
Judgment, then check the selected Slack channel for its message. For a
Background Agent, delivery contains the scheduled run's final assistant
message; a manual run does not verify scheduled delivery.

The **Connected** badge verifies the workspace connection, not delivery from
every workflow. Check the trigger and its execution as well as the channel.

## Disconnect or change workspaces

An organization admin or owner can select **Disconnect** in the Slack section.
This removes the organization's connection and affects workflows across its
projects that use it. Review those workflows before disconnecting.

To use a different workspace, disconnect, select **Connect**, and authorize
the intended workspace. Revisit workflow destinations and verify delivery;
do not assume channel selections from the old workspace are valid in the new
one.

## Troubleshooting

- If authorization fails, confirm your Judgment role and the Slack workspace's
  app-installation requirements.
- If a channel is missing, confirm the connected workspace and the app's
  access to that channel. Select from the available channels in the workflow.
- If no message arrives, check whether the workflow actually ran, whether its
  conditions matched, and whether cooldown or frequency settings suppressed
  delivery.
- If a Background Agent's Slack controls are disabled, enable its scheduled
  trigger first.

## Next step

[Configure an automation](/documentation/monitoring/automations-and-alerts) to
notify your team when a known condition occurs.