# Notifications

> Send important workspace events to Slack channels or webhook endpoints before teams miss them.

Source: https://0.0.0.0:8080/docs/notifications

Notifications help a workspace route operational events to the people and systems that need to react. Use them for failed executions, usage limits, billing issues, and team-access changes.

<ProductScreenshot
  src="/images/docs/notifications-settings.png"
  alt="PromptRails notification settings showing webhook configuration, event selection, channels, deliveries, and health"
  caption="Settings > Notifications lets a workspace create Slack or webhook destinations, choose which event families each destination receives, test delivery, and inspect recent send attempts."
  height={560}
/>

## When To Use Notifications

Set up notifications when a human or downstream system should know about a workspace event without checking PromptRails manually.

- **Execution health** -- notify an owner when an agent execution fails.
- **Usage limits** -- warn the team when the workspace reaches usage thresholds.
- **Billing events** -- route failed payments to the person who can fix them.
- **Team access** -- keep admins aware when members join or leave.

## Channels

A notification channel is one destination for one environment or team. For example, you might create:

- A production Slack channel for failed executions.
- A billing webhook for payment failures.
- An internal operations endpoint for usage-limit events.

Leave the event selection empty when the channel should receive every event. Select specific event families when a destination should only receive part of the stream.

## Delivery Health

After creating a channel, use **Test** to verify the endpoint. PromptRails keeps recent delivery attempts visible so failures can be debugged from the workspace instead of guessing whether a webhook or Slack destination received the event.

## Common Routing Examples

Start with a small number of channels. A typical production workspace might use:

| Destination         | Events                                      | Why it helps                                         |
| ------------------- | ------------------------------------------- | ---------------------------------------------------- |
| Operations Slack    | Execution failed, usage 80%, usage limit    | Keeps run health and capacity issues visible         |
| Billing owner       | Payment failed                              | Sends money-related issues to the person who can act |
| Admin audit webhook | Member joined, member removed               | Mirrors access changes into an internal audit system |
| Review queue        | Approval or execution events from workflows | Keeps human-in-the-loop work from getting stuck      |

Webhook channels can include an optional signing secret. Use it when the receiving service needs to verify that the request came from PromptRails.

Delivery attempts are scoped to the workspace. Disabled channels keep their configuration, but they do not receive new events until they are enabled again.

## Related Topics

- [Approvals](/docs/approvals) -- Notify reviewers when work is waiting for human review
- [Executions](/docs/executions) -- Execution states that can produce operational events
- [Billing and Plans](/docs/billing-and-plans) -- Usage limits, plan limits, and billing events
- [Workspace Management](/docs/workspace-management) -- Workspace-level settings and isolation