Skip to content
GuidesNotifications

Notifications

How-to
On this page
  1. Where notifications appear
  2. What events generate notifications
  3. Configure your own notifications
  4. Email preferences
  5. Quiet hours
  6. Mark notifications as read
  7. Filter the feed
  8. Org-wide Slack integration
  9. Outbound webhooks (for advanced integrations)
  10. Notification retention
  11. Troubleshooting
  12. Not receiving email notifications
  13. Slack notifications stopped working
  14. Webhook deliveries failing
  15. See also

The orchestrator generates notifications for events that need attention: long-running deployments completing, approvals waiting on you, cloud account issues, plan-limit warnings.

Where notifications appear

  • In-app bell (top-right of every page) — shows the 20 most recent, with an unread badge
  • Full notification feed at /notifications — full history with filters by domain (sessions, deployments, orgs, clouds) and read/unread status
  • Email — for events you opt into (off by default for most events)
  • Slack (org-wide) — if your org configures a Slack webhook

What events generate notifications

EventDefault in-appDefault email
Deployment finished✓—
Deployment failed✓✓
Approval needed (you’re the approver)✓✓
Approval decided (on your request)✓—
Cloud account verified / errored✓—
Plan limit at 80% / 100% (org)✓✓ (admins)
Org member invited / joined / removed✓ (admins)—
Org role changed (yours)✓✓

Configure your own notifications

/settings → Notifications (each user controls their own).

Email preferences

For each event type, choose:

  • Off — no email
  • Immediate — email per occurrence
  • Digest — one email per N minutes (you pick N; default 15) containing all events since the last digest

Recommended:

  • Approval needed: Immediate (you’re a bottleneck if you’re slow)
  • Deployment failed: Immediate
  • Other events: Digest or Off

Quiet hours

Optionally suppress email between specific hours (per your timezone). In-app notifications still accumulate; emails just don’t go out during quiet hours.

Useful if you’re on-call but don’t want your phone buzzing at 3am for plan-limit warnings.

Mark notifications as read

  • Click any notification in the bell / feed — opens the relevant page and marks it read
  • Click “Mark all read” at the top of the feed
  • Specific notification → right-click → “Mark unread” if you accidentally read it

Filter the feed

/notifications has chip filters:

  • All / Unread — read status
  • All / Sessions / Deployments / Orgs / Clouds — domain

Combine: “Unread Deployments” shows only unread deployment events.

The feed groups by relative time: Today / Yesterday / Earlier this week / Earlier. Recent events show their timestamp; old ones group into the broader bucket.

Org-wide Slack integration

Owners can configure a Slack webhook for org-wide notifications. /settings → Integrations → Slack.

  1. Create an Incoming Webhook in Slack pointing at your team’s #ops or #deploys channel
  2. Paste the webhook URL into the orchestrator
  3. Pick which events to forward (typically: deployment failed, approval needed, cloud account errored, plan limit reached)

Slack notifications go to the org Slack channel — not per-user DMs. Useful for team visibility.

Outbound webhooks (for advanced integrations)

If you want notifications to land somewhere other than email / Slack — e.g., PagerDuty, Opsgenie, your own webhook receiver — use the outbound webhook feature.

/settings → Integrations → Webhooks (Admins only).

  1. Click Add webhook
  2. Enter the URL of your webhook receiver
  3. Pick which events to forward
  4. Optionally set a signing secret (we’ll HMAC-sign payloads with it so you can verify origin)

Payload format:

json
{
  "event_id": "audit-evt-abc123",
  "event_type": "deployment.failed",
  "timestamp": "2026-05-13T14:00:00Z",
  "org_id": "o-f6bb2d865d8c",
  "actor": { "type": "user", "id": "u-...", "email": "engineer@acme.com" },
  "target": { "type": "deployment", "id": "deploy-456" },
  "payload": {
    "agent": "postgres",
    "stage": "Gate 6",
    "error_summary": "RDS quota exceeded in us-east-1"
  }
}

We retry failed webhook deliveries with exponential backoff up to 24 hours. After that, the event lands in a dead-letter view in the UI for manual replay.

Notification retention

By default, in-app notifications are retained 90 days. After that they’re auto-purged (the audit log keeps the underlying event for longer per plan tier).

Configurable per-org in /settings → Notifications → Retention.

Troubleshooting

Not receiving email notifications

  1. Check your email preferences in /settings → Notifications (might be set to Off or Digest)
  2. Check spam — no-reply@hivedeploy.in is the sender
  3. If your org uses Google Workspace or M365 with strict spam filters, ask IT to allowlist the sender
  4. Check /settings → Account → Email — is the email correct and verified?

Slack notifications stopped working

The webhook URL may have been rotated by Slack (incoming webhooks can be revoked). Re-create the webhook in Slack, update the URL in the orchestrator.

Webhook deliveries failing

Check /settings → Integrations → Webhooks → click webhook → Deliveries. Each delivery shows the request, response, and any retry attempts.

See also

Was this page helpful?