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

# Notifications

> Configure Slack notification rules and channels for deployment updates

Configure which Slack channels receive notifications for deployments and service updates in each environment.

Access this page from **Settings > Notifications** in the sidebar.

## Notification Rules

<Frame>
  <img src="https://mintcdn.com/koalaops/OKZlYchqd368KXSH/settings/img/notification-rules.png?fit=max&auto=format&n=OKZlYchqd368KXSH&q=85&s=65f7cb15d49ca72b984fc28e3681a987" alt="Notification rules showing environment-based routing to Slack channels" width="2104" height="854" data-path="settings/img/notification-rules.png" />
</Frame>

Route deployment notifications to different Slack channels based on environment.

### Environment-Based Routing

Configure which channels receive notifications for specific environments:

* `dev` environment → `#engineering` channel
* `staging` environment → `#qa-team` channel
* `prod` environment → `#alerts` channel
* `All Environments` → `#general` channel

### How It Works

1. **Add an environment rule** specifying the environment name or "All Environments"
2. **Select Slack channels** to receive notifications for that environment
3. **Deployments trigger notifications** to the specified channels when they occur

### Managing Rules

* **Edit**: Change the environment or channels for an existing rule
* **Delete**: Remove a rule to stop sending notifications
* **Add Environment Rule**: Create a new routing rule

<Tip>
  Use environment-specific channels to reduce noise. For example, send dev deployments to `#engineering`, but production deployments to `#alerts` for higher visibility.
</Tip>

## Notification Channels

<Frame>
  <img src="https://mintcdn.com/koalaops/OKZlYchqd368KXSH/settings/img/slack-channels.png?fit=max&auto=format&n=OKZlYchqd368KXSH&q=85&s=06a300f773340bb5e431a2a35e34d6eb" alt="Slack integration showing connected channels and direct messages" width="2104" height="1042" data-path="settings/img/slack-channels.png" />
</Frame>

### Slack Integration

Connect Slack channels to receive notifications about deployments and service updates.

**Connected channels show**:

* **Channel name**: e.g., `#general`, `#alerts`, `@username`
* **Channel ID**: e.g., `C04SCMG9CAD` (Slack's internal identifier)
* **Channel types**: Public channels (`#channel-name`) or direct messages (`@username`)

### Adding Slack Channels

1. Click **Add Slack Channel**
2. Authorize Skyhook to access your Slack workspace (if not already connected)
3. Select the channel to connect
4. Use the channel in notification rules

<Tip>
  You can send notifications to both public channels (`#channel-name`) and direct messages (`@username`) for important alerts or individual updates.
</Tip>

### Managing Channels

* **Delete**: Remove a channel from Skyhook (stops all notifications to that channel)
* **Add Slack Channel**: Connect additional channels as needed

<Info>
  Channels must be added to Slack Integration before they can be used in Notification Rules.
</Info>

## Use Cases

### Development Team Notifications

Route dev and staging deployments to your team's working channel:

* Environment: `dev`
* Channel: `#engineering`

### Production Alerts

Send production deployments to a dedicated alerts channel with higher visibility:

* Environment: `prod`
* Channels: `#alerts`, `#on-call`

### Individual Notifications

Send notifications to specific team members for their services:

* Environment: `All Environments`
* Channel: `@developer-name`

### Catch-All Notifications

Ensure all deployments are logged in a central channel:

* Environment: `All Environments`
* Channel: `#deployments`

<Warning>
  Notification rules are processed in order. More specific rules (like individual environments) take precedence over general rules (like "All Environments").
</Warning>

## Related Documentation

* [Service Deployment](/application/services/deploy) - How deployments work
* [Environments](/application/environments/overview) - Understanding environments
* [CI/CD](/application/cicd/overview) - CI/CD pipeline configuration