> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting/notification-channels.md).

# Notification Channels

Understand the main channels of alerting including Slack, Teams, PagerDuty, Email, and Webhooks.

Pharos integrates with the communication tools your teams already use, delivering context-rich notifications exactly where they're needed. Each channel below has its own dedicated guide covering setup, capabilities, and configuration examples.

{% hint style="info" %}
**Meet Teams Where They Work**

The best notification is one that's actually seen. By integrating with your existing communication tools, Pharos ensures error awareness without adding yet another system to monitor.
{% endhint %}

Pharos supports five notification channels:

| Channel             | Primary Use Case                       | Setup Effort | Integration Type |
| ------------------- | -------------------------------------- | ------------ | ---------------- |
| **Slack**           | Real-time team collaboration           | Low          | OAuth            |
| **Microsoft Teams** | Microsoft ecosystem teams              | Low          | OAuth            |
| **PagerDuty**       | On-call escalation for critical issues | Low          | API Key          |
| **Email**           | Fallback, digest mode, non-urgent      | Minimal      | Native SMTP      |
| **Webhooks**        | Custom integrations, third-party tools | Medium       | HTTP POST        |

## In This Section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>💬 Slack Notifications</strong></td><td>Configure Slack notifications and understand supported capabilities.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting/notification-channels/slack.md">Slack</a></td></tr><tr><td><strong>👥 Microsoft Teams Notifications</strong></td><td>Configure Microsoft Teams notifications and understand supported capabilities.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting/notification-channels/teams.md">Teams</a></td></tr><tr><td><strong>🚨 PagerDuty Notifications</strong></td><td>Configure PagerDuty integration for incident management and on-call escalation.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting/notification-channels/pagerduty.md">PagerDuty</a></td></tr><tr><td><strong>📧 Email Notifications</strong></td><td>Configure email notifications with caution about their limitations for observability.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting/notification-channels/email.md">Email</a></td></tr><tr><td><strong>🔗 Webhook Notifications</strong></td><td>Configure webhook notifications for integration with third-party observability tools.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting/notification-channels/webhooks.md">Webhooks</a></td></tr></tbody></table>

{% hint style="success" %}
**Choosing a Starting Point**

Most teams start with Slack for real-time awareness, add PagerDuty once critical scenarios are well understood, and use Email for digests or non-technical stakeholders. See [Alerting](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/alerting.md) for channel strategy and rule design best practices.
{% endhint %}
