Skip to main content
Sentry sends notifications through multiple channels and for different types of events. You can configure notifications at the organization level, the project level, and as personal preferences.

Notification types

Issue alerts

Triggered by alert rules. Notifies you when a new issue is created, a regression occurs, or frequency thresholds are crossed.

Workflow

Activity on issues you are subscribed to — comments, assignment changes, status changes, and regressions.

Deploy

Sent when a release is deployed to an environment. You can receive notifications for all deploys or only releases that contain your commits.

Spike protection

Warns you when inbound event volume spikes significantly above your baseline, which could indicate an incident or runaway error.

Quota

Alerts when your organization approaches or reaches its event quota (errors, transactions, replays, spans, and so on).

Weekly reports

A weekly summary of your top issues, error volume trends, and performance stats.

Notification channels

Sentry delivers notifications through the following channels:
The default channel. Sentry sends HTML emails for issue alerts, workflow notifications, and digests. You can configure your email address under User Settings → Account.Digest emails bundle multiple issue alert notifications into a single email, reducing inbox noise. The digest is sent at most once per the configured interval (default: 5 minutes).

Personal notification settings

Each user can override organization defaults in User Settings → Notifications. Settings are organized by notification type:
TypeAvailable options
Issue alertsAlways, Never
WorkflowAlways, Only on issues I subscribe to, Never
DeployAlways, Only on my commits, Never
QuotaAlways, Never
Weekly reportsAlways, Never
Spike protectionAlways, Never
You can also configure per-project overrides when you want different behavior for specific projects.

Organization-level defaults

Organization owners and managers can set default notification preferences for all members under Organization Settings → Notifications. Members can override these defaults in their personal settings.

Configuring notification actions in alert rules

When creating or editing an alert rule, the Actions section lets you add one or more notification targets. Each target specifies:
  1. Channel — email, Slack, PagerDuty, MSTeams, Discord, or webhook
  2. Target — a specific user, team, channel, or service
  3. Trigger level — warning or critical (metric alerts only)
Example Slack action configuration in an alert rule:
  • Send a Slack message to #backend-alerts in My Workspace

Issue subscriptions

You are automatically subscribed to an issue when you:
  • Comment on it
  • Are assigned to it
  • Bookmark it
  • Change its status
  • Are @mentioned in a comment
  • Are a member of a @mentioned team
You can manually subscribe or unsubscribe from any issue using the Subscribe button on the issue details page. Workflow notifications are only sent for issues you are subscribed to (if you chose the “subscribe only” option).

Build docs developers (and LLMs) love