# Slack

Connect your organization's Slack workspace and match members to their accounts.

The Slack integration connects a workspace to your organization so withHuman can send reviewers direct messages. **Integrations** manages the shared connection; [Slack notifications](/docs/web-app/slack-notifications) covers each person's account and notification preferences.

## Workspace connection

Connecting requires permission to manage integrations in withHuman and authorization to install the app in Slack. The authorization happens in Slack, where the workspace and requested access are shown.

The app requests access to find workspace members by email, open direct messages and send messages. Approval notifications currently use personal DMs, and decisions happen in withHuman.

An organization has one connected Slack workspace. A workspace can only be connected to one withHuman organization at a time. If you have already removed the app in Slack but still cannot connect, wait a moment and try again. A workspace that is still connected to another organization needs to be disconnected there first.

**Connected** shows the workspace name and when it was connected. **Disconnected** means Slack notifications have stopped; use **Reconnect** to restore the connection. **Not enabled** means the person running your withHuman service needs to enable Slack first. If authorization is declined or expires, start a new connection attempt.

## Member matching

When the workspace connects, withHuman attempts to match active members using their account email and other confirmed email addresses. Matched accounts become linked Slack channels.

**Sync members** repeats that matching for active members, including people who joined or confirmed an address after the connection was made. **Linked members** shows how many active members have a link. A sync does not invite people to Slack or change their withHuman permissions.

Members can also link their own account under Notifications without waiting for a sync. If no match is found, the address they use in Slack needs to be added and confirmed as an [email channel](/docs/web-app/email-notifications). One Slack account cannot be linked to two members in the same organization.

### Example: A reviewer uses a different email

We'll connect our Payments workspace. One reviewer signs in to withHuman with a personal address but uses a work address in Slack. Confirming that work address in Notifications lets withHuman find the right Slack account. The reviewer can then use Slack in their personal rules.

## Notification rules

The connection makes Slack available to linked members. Their [personal rules](/docs/web-app/notifications#standard-requests-and-interrupts) choose when it is used. Saved rules are not rewritten by connecting the workspace or syncing members.

A member can remove Slack from their rules while the organization's connection stays in place. Syncing accounts does not select reviewers or change escalation paths.

## Disconnection

Disconnecting in withHuman, or removing the withHuman app from Slack, stops Slack notifications for everyone in the organization. **Integrations** shows **Disconnected**, and members' Slack channels show **Unavailable** in Notifications. The status may take a short time to update after the app is removed in Slack.

Members' saved notification rules are kept. Other channels continue at their usual times, and account email is used temporarily when Slack was the only way to be notified before a request expires. See [Disconnected Slack](/docs/web-app/notifications#disconnected-slack) for what to expect.

An administrator can use **Reconnect** to restore the workspace connection. withHuman looks for members' Slack accounts again, and their saved rules resume when their channels show **Linked**. Anyone still marked **Unavailable** should check the [email address used for Slack](/docs/web-app/slack-notifications#account-linking). Messages missed during the disconnection are not sent later.

Connection changes remain in [Audit log](/docs/web-app/audit-log). The [Integrations overview](/docs/web-app/integrations#permissions-and-history) covers who can view and manage them.