Help Centre

Appearance

Notification Settings ​

Overview ​

SignalBreak's notification system keeps you informed about AI governance events across your organization. Configure how and when you receive alerts about new signals, critical incidents, and activity summaries to stay on top of your AI compliance without notification overload.

Location: Settings → Customisation → Notification Preferences

Key Features:

  • Real-time email alerts for new signals
  • Severity filtering (critical/high only)
  • Daily or weekly digest summaries
  • Organization-wide settings (applies to all team members)

Notification Types ​

1. New Signal Alerts ​

Purpose: Immediate email notification when SignalBreak detects a new signal in your AI ecosystem.

When triggered:

  • Provider status change (outage, degradation)
  • Model deprecation announcement
  • Security vulnerability disclosure
  • Policy or pricing change
  • Performance anomaly detected

Email contains:

  • Signal title and severity level
  • Affected provider/model
  • Impact summary
  • Link to full signal details in portal
  • Recommended actions (if applicable)

Configuration:

Settings → Customisation → New Signal Alerts (toggle)

Default: Enabled (recommended for all users)

2. Critical Signals Only Filter ​

Purpose: Reduce notification volume by only sending alerts for high-impact events.

Severity levels included:

  • 🔴 Critical: Service outages, security vulnerabilities, immediate action required
  • 🟠 High: Major incidents, deprecations with short timelines, policy changes affecting compliance

Severity levels excluded:

  • 🟡 Medium: Minor updates, performance degradation, informational changes
  • 🟢 Low: General announcements, planned maintenance, optional upgrades

Configuration:

Settings → Customisation → Critical Signals Only (toggle)
Requires: New Signal Alerts must be enabled

Use cases:

  • High-volume environments where every signal creates alert fatigue
  • Teams with dedicated monitoring staff who check the portal regularly
  • Organizations with established escalation procedures for critical events only

Trade-off: You may miss important medium-severity signals that could impact your workflows over time.

3. Email Digests ​

Purpose: Receive consolidated summaries of activity at your preferred frequency, reducing inbox clutter while maintaining visibility.

Digest options:

No Digest ​

  • Receive only real-time alerts (if enabled)
  • Best for: Teams who prefer portal-based monitoring

Daily Digest ​

  • Sent at 9:00 AM in your organization's timezone
  • Includes all activity from the previous 24 hours
  • Best for: Teams actively managing AI systems who need daily visibility

Daily digest contains:

  • New signals detected (grouped by severity)
  • Workflow impact summary
  • Provider status changes
  • Recommended actions
  • Quick link to full activity log

Weekly Digest ​

  • Sent every Monday at 9:00 AM in your organization's timezone
  • Includes all activity from the previous 7 days
  • Best for: Executive oversight or teams in stable, low-risk environments

Weekly digest contains:

  • Weekly signal summary (count by severity)
  • Top 5 most critical signals
  • Workflow availability statistics
  • Trend analysis (compared to previous week)
  • Recommended strategic actions
  • Link to full governance report

Configuration:

Settings → Customisation → Email Digest dropdown
Options: No digest, Daily digest, Weekly digest

Default: Daily digest

Note: Digests are independent of real-time alerts. You can receive both immediate notifications AND digests, or only digests.

Configuration Guide ​

Accessing Notification Settings ​

  1. Navigate to Settings in the main navigation
  2. Select Customisation from the settings menu
  3. Scroll to Notification Preferences card

Permission required: Any user can view preferences; only Admins can modify them.

Setting Up Notifications ​

✅ New Signal Alerts: Enabled
❌ Critical Signals Only: Disabled (receive all severities)
📅 Email Digest: Daily digest

Result: Real-time alerts for every signal + daily summary of all activity.

Best for: Small teams (1-5 workflows), high-risk industries, teams in early AI adoption phase.

✅ New Signal Alerts: Enabled
✅ Critical Signals Only: Enabled
📅 Email Digest: Weekly digest

Result: Only critical/high alerts in real-time + weekly summary of all activity.

Best for: Mature AI operations (10+ workflows), teams with dedicated monitoring staff, established incident response procedures.

Example 3: Digest-Only (Portal-First Workflow) ​

❌ New Signal Alerts: Disabled
📅 Email Digest: Daily digest

Result: No real-time email alerts; daily summary only. Team checks portal for details.

Best for: Teams with established portal check-in routines, low-risk use cases, avoiding alert fatigue.

❌ New Signal Alerts: Disabled
📅 Email Digest: No digest

Result: No email notifications. All monitoring must be done via portal.

⚠️ Warning: High risk of missing critical events. Only use if:

  • You have alternative monitoring systems in place
  • You check the portal multiple times daily
  • Your AI systems are non-critical (development/testing only)

Modifying Notification Preferences ​

Requirements:

  • Admin role required to change settings
  • Changes apply organization-wide (all team members)

Steps:

  1. Review current settings

    • Check existing toggle states and digest frequency
    • Consider your team's current alert volume and response patterns

  2. Adjust preferences

    • Toggle New Signal Alerts on/off
    • Toggle Critical Signals Only (only available if New Signal Alerts is enabled)
    • Select Email Digest frequency from dropdown

  3. Save changes

    • Click Save Preferences button
    • Wait for confirmation toast: "Preferences saved"
    • Changes take effect immediately

  4. Verify via test signal (optional)

    • Check your email for the next signal notification
    • Verify it matches your new preferences
    • Allow 24 hours for digest changes to take effect

⚠️ Important: Notification preferences apply to the entire organization, not individual users. All team members receive notifications according to these settings.

Email Format & Delivery ​

Real-Time Alert Email Structure ​

Subject: [SignalBreak Alert] OpenAI GPT-4 Outage Detected - Critical

┌──────────────────────────────────────────────────┐
│ 🔴 Critical Signal Detected                      │
└──────────────────────────────────────────────────┘

Signal: OpenAI GPT-4 Service Outage
Provider: OpenAI
Severity: Critical
Detected: 2026-01-26 14:32 GMT

IMPACT SUMMARY
--------------
3 workflows affected:
• Customer Support Summaries (Critical)
• Contract Review Assistant (High)
• Email Response Drafting (Medium)

Fallback configured: 2/3 workflows
Estimated recovery: 2-4 hours

RECOMMENDED ACTIONS
-------------------
1. Verify fallback providers are operational
2. Monitor affected workflows for errors
3. Notify stakeholders if customer-facing impact

[View Full Details in Portal →]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SignalBreak | AI Governance Platform
Unsubscribe | Notification Settings

Digest Email Structure (Daily) ​

Subject: SignalBreak Daily Digest - Monday, 26 Jan 2026

┌──────────────────────────────────────────────────┐
│ Daily Activity Summary                           │
│ 24 hours ending 09:00 GMT                        │
└──────────────────────────────────────────────────┘

SIGNALS DETECTED: 4 total
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔴 CRITICAL (1)
• OpenAI GPT-4 Service Outage
  Impact: 3 workflows | Detected: 14:32 GMT

🟠 HIGH (1)
• Anthropic Claude 3.5 Pricing Change
  Impact: 5 workflows | Detected: 08:15 GMT

🟡 MEDIUM (2)
• Azure OpenAI Rate Limit Update
• Google Gemini Pro Model Deprecation (6 months)

WORKFLOW HEALTH
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Availability: 94.2% (down from 99.8% yesterday)
Total Workflows: 12
Affected Today: 6

TOP ACTIONS NEEDED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Review OpenAI incident impact on customer-facing workflows
2. Update budget forecasts for Anthropic price increase
3. Plan migration for deprecated Gemini Pro workflows

[View Full Activity Log →]
[Download Governance Report →]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SignalBreak | AI Governance Platform
Notification Settings | Unsubscribe

Email Delivery Details ​

Sender: alerts@signalbreak.comReply-To: support@signalbreak.com

Delivery timing:

  • Real-time alerts: Within 5 minutes of signal detection
  • Daily digests: 9:00 AM organization timezone (set in Settings → Profile)
  • Weekly digests: Monday 9:00 AM organization timezone

Spam prevention:

  • SPF/DKIM/DMARC authentication
  • Rate limiting: Maximum 1 real-time alert per signal (no duplicates)
  • Digest de-duplication: Signals already notified in real-time are marked "Previously alerted"

Email reliability:

  • 99.9% delivery SLA
  • Retry logic: 3 attempts over 15 minutes
  • Failure notifications logged in audit trail

Notification Scope & Permissions ​

Who Receives Notifications? ​

All team members receive notifications according to the organization-wide settings, regardless of role:

  • ✅ Admins
  • ✅ Members
  • ✅ Viewers

Email address used:

  • The email address associated with each user's SignalBreak account
  • Managed via Settings → Profile → Email Address
  • Users cannot opt out individually (organization-wide policy)

Who Can Modify Notification Settings? ​

ActionAdminMemberViewer
View notification preferences✅✅✅
Modify notification settings✅❌❌
Change digest frequency✅❌❌
Enable/disable alerts✅❌❌

Permission denied error: Non-admin users who attempt to save changes will see:

❌ Save failed: Admin access required

Rationale: Organization-wide notification policy ensures consistent governance visibility and prevents individuals from missing critical events.

Per-User Customization (Not Currently Supported) ​

SignalBreak currently applies notification preferences organization-wide. Individual users cannot:

  • Opt out of specific notification types
  • Set personal digest frequency
  • Configure custom severity thresholds

Workaround for user-level control:

  1. Create email filters in your mail client (Gmail, Outlook, etc.)
  2. Use folder rules to sort SignalBreak notifications by severity
  3. Set up inbox rules to auto-archive digest emails if not needed

Feature Request: Per-user notification preferences are on the product roadmap. Request early access →

Best Practices ​

1. Start Conservative, Then Optimize ​

Initial setup (first 2 weeks):

✅ New Signal Alerts: Enabled
❌ Critical Signals Only: Disabled
📅 Email Digest: Daily

Why: Learn your baseline signal volume and severity distribution before filtering.

After 2 weeks: Review your signal history:

  • If receiving 10+ medium/low signals daily → Enable "Critical Signals Only"
  • If digests are redundant → Switch to weekly
  • If missing real-time alerts → Keep all notifications on

2. Align Digest Frequency with Review Cadence ​

Your Workflow Review CadenceRecommended Digest
Daily standup / check-inDaily digest
Weekly sprint reviewWeekly digest
Monthly governance meetings onlyWeekly digest (review 4 digests per month)
Ad-hoc / incident-drivenNo digest (portal + real-time alerts)

Team habit tip: Schedule a recurring calendar event to review digests. Example:

  • Monday 9:15 AM: "Review SignalBreak Weekly Digest" (15 min)
  • Daily 9:05 AM: "Check SignalBreak Alerts" (5 min)

3. Use Severity Filtering Strategically ​

Enable "Critical Signals Only" if:

  • ✅ Your team checks the portal daily (medium/low signals visible there)
  • ✅ You have 8+ workflows and expect high signal volume
  • ✅ Your workflows have robust fallback configurations
  • ✅ You operate in a stable environment (established providers, mature models)

Keep "Critical Signals Only" disabled if:

  • ❌ You're in early AI adoption phase (learning mode)
  • ❌ Your workflows lack fallback providers
  • ❌ You operate in a high-risk or highly regulated industry
  • ❌ Your team primarily relies on email (low portal engagement)

4. Coordinate with Team Communication Tools ​

Integrate SignalBreak alerts with your team's workflow:

Slack Integration (Coming Soon) ​

#ai-governance channel
SignalBreak Bot: 🔴 Critical Alert: OpenAI GPT-4 Outage
Affects 3 workflows | [View Details] [Acknowledge]

Current workaround:

  1. Create dedicated Slack channel: #signalbreak-alerts
  2. Forward alert emails to channel email address (e.g., alerts-abc123@yourorg.slack.com)
  3. Team members can discuss and acknowledge in thread

Microsoft Teams Integration (Coming Soon) ​

Similar flow as Slack integration above.

Current workaround: Use Teams email integration to forward alerts to a dedicated channel.

5. Test Your Notification Setup ​

After configuring preferences:

  1. Trigger a test signal (Admin only):

    Settings → Advanced → Send Test Notification

    (Feature planned for Q1 2026)

  2. Current testing method:

    • Wait for next natural signal (within 24-48 hours typical)
    • Check email inbox for alert
    • Verify severity filter works as expected
    • Confirm digest arrives at scheduled time

  3. Check spam folder:

    • If no alert received within 48 hours, check spam/junk
    • Whitelist @signalbreak.com domain
    • Add alerts@signalbreak.com to contacts

6. Document Your Notification Policy ​

For regulated industries or Enterprise plans, document your organization's notification configuration as part of your AI governance policy:

Example policy snippet:

Notification Policy - SignalBreak AI Governance Platform
Version: 1.0
Last Updated: 2026-01-26
Owner: Head of AI Operations

Settings:
- New Signal Alerts: Enabled
- Critical Signals Only: Enabled (to reduce alert fatigue)
- Email Digest: Weekly (reviewed in Monday AI Governance standup)

Escalation Procedure:
- Critical alerts: Acknowledged within 30 minutes (on-call rotation)
- High alerts: Reviewed within 4 business hours
- Weekly digest: Reviewed by AI Governance team lead every Monday 9:00 AM

Review Cadence:
- Notification policy reviewed quarterly
- Signal volume trends analyzed monthly
- Severity thresholds adjusted as needed

Benefits:

  • Compliance audit trail (ISO 42001, SOC 2)
  • Onboarding new team members
  • Incident post-mortem reference
  • Executive reporting on governance maturity

Troubleshooting ​

Problem: Not Receiving Email Notifications ​

Symptoms:

  • No real-time alerts arriving despite signals being visible in portal
  • Digests not arriving at scheduled time
  • Email inbox empty for SignalBreak notifications

Diagnosis steps:

  1. Check notification settings are enabled:

    • Go to Settings → Customisation → Notification Preferences
    • Verify "New Signal Alerts" toggle is ON
    • Verify "Email Digest" is not set to "No digest"

  2. Verify your email address:

    • Go to Settings → Profile
    • Confirm your email address is correct
    • Check for typos or outdated email addresses

  3. Check spam/junk folder:

    • Search for from:alerts@signalbreak.com in spam
    • If found, mark as "Not Spam" and whitelist sender

  4. Verify signal activity:

    • Go to Dashboard → Signals
    • Check if any signals were detected in the expected timeframe
    • If no signals, then no notifications is expected behavior

  5. Test email deliverability:

    • Try changing notification preferences and saving
    • You should receive a confirmation: "Preferences saved"
    • If save fails, check network connection or browser console for errors

Solutions:

CauseSolution
Notifications disabledEnable "New Signal Alerts" in settings
Wrong email addressUpdate email in Settings → Profile
Spam filter blockingWhitelist @signalbreak.com domain
No recent signal activityNormal - wait for next signal detection
Email provider issueCheck email service status, contact support@signalbreak.com

Still not working? Contact support with:

  • Your organization name and tenant ID (Settings → Advanced → Tenant Details)
  • Screenshots of notification settings
  • Approximate time you expected to receive notification
  • Email provider (Gmail, Outlook, corporate email, etc.)

Problem: Receiving Too Many Notifications (Alert Fatigue) ​

Symptoms:

  • Inbox flooded with SignalBreak alerts (10+ per day)
  • Team members ignoring or auto-archiving notifications
  • Important critical alerts being missed in noise

Diagnosis:

  1. Review signal volume:

    • Go to Dashboard → Signals → Filter by last 7 days
    • Count signals by severity
    • Identify high-volume, low-severity signals

  2. Check notification settings:

    • Settings → Customisation → Notification Preferences
    • Is "Critical Signals Only" enabled? (If not, you're getting all severities)

  3. Analyze signal sources:

    • Are most signals medium/low severity?
    • Are they from the same provider (e.g., frequent status page updates)?
    • Are they actionable or informational?

Solutions:

ScenarioRecommended Action
High volume of medium/low signalsEnable "Critical Signals Only" filter
Many signals, few actionableSwitch to daily or weekly digest only
Redundant provider status updatesConfigure provider filters (Enterprise feature)
Team ignoring emailsReduce notification frequency, increase portal engagement
Mix of critical and noiseKeep real-time alerts for critical only + weekly digest for full visibility

Optimal configuration for high-volume environments:

✅ New Signal Alerts: Enabled
✅ Critical Signals Only: Enabled
📅 Email Digest: Weekly digest

Result: Only critical/high alerts interrupt your workflow; full context available in weekly summary.

Problem: Digests Not Arriving on Schedule ​

Symptoms:

  • Daily digest set to 9:00 AM but arrives at different times
  • Weekly digest expected Monday morning but arrives Tuesday
  • Digests sometimes arrive, sometimes don't

Diagnosis:

  1. Verify organization timezone:

    • Settings → Profile → Timezone
    • Digest times are based on organization timezone, not individual user timezone
    • If timezone is wrong, digest will arrive at wrong local time

  2. Check for signals in digest period:

    • Daily digest: Were any signals detected in the past 24 hours?
    • Weekly digest: Were any signals detected in the past 7 days?
    • Empty digests are not sent (by design)

  3. Check spam folder:

    • Digests may be filtered differently than real-time alerts
    • Search for subject:SignalBreak Daily Digest or subject:SignalBreak Weekly Digest

  4. Verify digest frequency setting:

    • Settings → Customisation → Email Digest
    • Ensure it's set to "Daily digest" or "Weekly digest" (not "No digest")

Solutions:

CauseSolution
Wrong timezoneUpdate organization timezone in Settings → Profile
No activity in periodNormal - digests only sent when there's activity to report
Digests in spamWhitelist alerts@signalbreak.com
Digest disabledChange from "No digest" to desired frequency
Email provider delayAllow 15-30 min delivery window around scheduled time

Digest delivery SLA:

  • Daily: Between 9:00 AM - 9:30 AM organization timezone
  • Weekly: Between 9:00 AM Monday - 9:30 AM Monday organization timezone

If digests consistently arrive outside this window, contact support.

Problem: Cannot Save Notification Preferences ​

Symptoms:

  • "Save Preferences" button is disabled/grayed out
  • Clicking "Save Preferences" shows error: "Admin access required"
  • Changes to settings are not persisting

Diagnosis:

  1. Check your user role:

    • Settings → Team → Your user row
    • Look for your role badge (Admin / Member / Viewer)
    • Only Admin role can modify notification settings

  2. Check network connectivity:

    • Open browser console (F12)
    • Click "Save Preferences"
    • Look for HTTP errors (401 Unauthorized, 403 Forbidden, 500 Internal Server Error)

  3. Verify you're logged in:

    • Session may have expired
    • Try refreshing page and logging in again

Solutions:

CauseSolution
Non-admin userAsk an Admin to change settings, or request Admin role elevation
Session expiredLog out and log back in
Network errorCheck internet connection, try again
Browser cacheHard refresh (Ctrl+Shift+R / Cmd+Shift+R), clear cache
Account suspendedContact billing or support

Error messages explained:

ErrorMeaningSolution
"Admin access required"You don't have Admin roleAsk Admin to make change or promote you
"Unauthorized"Not logged in or session expiredLog in again
"Failed to save preferences"Server error or network issueTry again, contact support if persists
"Invalid digest frequency"Bug or tamperingRefresh page, try again

Problem: Notifications Going to Wrong Email Address ​

Symptoms:

  • Notifications sent to old email address
  • Notifications sent to shared mailbox instead of personal email
  • Some team members receiving, others not

Diagnosis:

  1. Verify account email:

    • Settings → Profile → Email Address
    • This is the email used for all SignalBreak notifications
    • Check if it matches your current work email

  2. Check for email forwarding:

    • Check your email provider settings
    • Are SignalBreak emails being auto-forwarded?

  3. Verify team member accounts:

    • Settings → Team
    • Check if all active team members have correct email addresses
    • Remove users who have left the organization

Solutions:

ScenarioSolution
Out-of-date emailUpdate email in Settings → Profile → Email Address
Former employee still receivingRemove user from Settings → Team
Shared mailbox setupUpdate individual user emails to personal addresses
Email forwarding interferingDisable forwarding rules for SignalBreak notifications

⚠️ Security note: Notifications may contain sensitive information about your AI systems. Ensure they're only sent to current employees and official work emails.

Problem: Duplicate Notifications ​

Symptoms:

  • Receiving the same alert email 2-3 times
  • Same signal appearing in both real-time alert and digest
  • Multiple digests received in one day

Diagnosis:

  1. Check for multiple accounts:

    • Do you have more than one SignalBreak account with the same email?
    • Are you part of multiple organizations?

  2. Verify no email forwarding loops:

    • Check if your email is being forwarded back to itself
    • Check for rules that copy SignalBreak emails

  3. Check digest settings:

    • Receiving signal in both real-time alert AND digest is expected behavior
    • Digests include all activity, even if previously alerted in real-time

Expected behavior:

  • Real-time alert: Immediate notification when signal detected (within 5 minutes)
  • Digest: Summary of ALL activity including previously-alerted signals
  • Digest marks previously-alerted signals with "✓ Previously alerted"

Not expected:

  • Receiving the same real-time alert twice
  • Receiving multiple daily digests on the same day

Solutions:

CauseSolution
Multiple organizationsNormal - each organization sends separate notifications
Email forwarding loopCheck email rules, remove forwarding
Real-time + digest overlapThis is expected - digest includes all activity
True duplicate alertsContact support (may indicate bug)

Problem: Critical Signals Only Not Working ​

Symptoms:

  • "Critical Signals Only" enabled but still receiving medium/low severity alerts
  • Toggle appears on but behavior doesn't match

Diagnosis:

  1. Verify setting is saved:

    • Settings → Customisation → Notification Preferences
    • Check "Critical Signals Only" toggle is ON
    • Check for green "Preferences saved" confirmation toast

  2. Check signal severity:

    • Dashboard → Signals → View recent signal
    • Verify the severity level assigned by SignalBreak
    • A signal you perceive as "low" may be classified as "high" by the system

  3. Verify "New Signal Alerts" is enabled:

    • "Critical Signals Only" requires "New Signal Alerts" to be ON
    • If "New Signal Alerts" is OFF, no notifications are sent regardless

Solutions:

CauseSolution
Setting not savedClick "Save Preferences" again, verify toast confirmation
Severity classification differenceReview signal in portal to see actual severity level
New Signal Alerts disabledEnable "New Signal Alerts" first, then "Critical Signals Only"
Cache issueClear browser cache, hard refresh (Ctrl+Shift+R)

Severity thresholds (reminder):

  • ✅ Sent with filter ON: Critical, High
  • ❌ Blocked with filter ON: Medium, Low

If you're receiving Medium/Low alerts despite filter being on, contact support with:

  • Screenshot of notification settings
  • Forward the unexpected alert email
  • Signal ID from portal

Signal Intelligence ​

Learn more about how signals are detected, classified, and prioritized:

Workflow Impact Analysis ​

Understand how SignalBreak determines which workflows are affected by each signal:

Governance Reporting ​

Generate comprehensive governance reports to share with stakeholders:

Audit Trail ​

All notification preference changes are logged in your audit trail:

Team Management ​

Control who has access to modify notification settings:

Frequently Asked Questions ​

Can individual users customize their notification preferences? ​

No, not currently. Notification preferences are set organization-wide and apply to all team members. Only Admins can modify these settings.

Workaround: Users can create email filters in their mail client (Gmail, Outlook, etc.) to sort or archive SignalBreak notifications based on severity or subject line.

Example Gmail filter:

From: alerts@signalbreak.com
Subject: [SignalBreak Alert]
Has the words: Medium
→ Skip Inbox (Archive)

Roadmap: Per-user notification preferences are planned for a future release. This will allow individual users to:

  • Set personal digest frequency
  • Configure severity thresholds
  • Opt out of specific notification types

Request early access to this feature →

What happens to notifications when a team member is removed? ​

When an Admin removes a team member from your organization:

  1. Immediate effect: User's email is removed from all future notifications
  2. Pending emails: Any emails already queued for delivery may still be sent (within 5 minutes)
  3. Digests: User will not receive the next scheduled digest
  4. Portal access revoked: User can no longer log in to view signals

Audit trail: Team member removal is logged in Settings → Audit Log with timestamp and Admin who performed the action.

Security note: Ensure removed employees no longer have access to their work email inbox, as previously-sent notifications remain accessible.

Can we integrate SignalBreak notifications with Slack or Microsoft Teams? ​

Not yet, but it's on the roadmap.

Planned integrations (Q1-Q2 2026):

  • Slack: Real-time alerts and digests posted to a channel
  • Microsoft Teams: Similar flow as Slack
  • PagerDuty: Critical alerts routed to on-call rotation
  • Webhook: POST signal data to your custom endpoint for integration with internal tools

Current workaround for Slack:

  1. Create a dedicated Slack channel: #signalbreak-alerts
  2. Forward alert emails to the channel's email address (found in Slack channel settings)
  3. Team members can react and discuss in threads

Current workaround for Microsoft Teams: Similar process - use Teams email integration to forward alerts to a channel.

Request early access to integrations →

How do notification preferences interact with plan tiers (Free/Starter/Pro/Enterprise)? ​

FeatureFreeStarterProfessionalEnterprise
Real-time email alerts✅✅✅✅
Daily digests✅✅✅✅
Weekly digests✅✅✅✅
Critical signals only filter✅✅✅✅
Slack integration❌❌RoadmapRoadmap
Microsoft Teams integration❌❌RoadmapRoadmap
Webhook notifications❌❌❌Roadmap
Per-user customization❌❌RoadmapRoadmap
Custom severity thresholds❌❌❌Roadmap
Provider-specific filters❌❌❌✅

All notification features are available across all plan tiers. Advanced integrations and customization options are planned for higher tiers.

Do notifications count toward my plan limits? ​

No. Email notifications and digests do not consume:

  • API rate limits
  • User seats
  • Workflow limits
  • Signal detection quotas

Email delivery is unlimited for all plan tiers. There are no additional charges for receiving notifications.

Rate limiting: SignalBreak implements internal rate limiting to prevent spam (e.g., maximum 1 alert per signal), but this does not affect your plan usage.

Can we get notifications in multiple languages? ​

Not currently. All SignalBreak notifications are sent in English only.

Roadmap: Multi-language support is planned for 2026, prioritized by customer demand:

  • Spanish
  • French
  • German
  • Japanese

Language setting will be configurable in Settings → Profile → Language Preference.

Request a specific language →

What information do notification emails contain? Is sensitive data included? ​

Real-time alerts include:

  • Signal title and severity (e.g., "OpenAI GPT-4 Outage - Critical")
  • Affected provider and model names
  • Number of workflows affected (count only, not workflow names)
  • General impact summary (e.g., "3 workflows affected, 2 have fallbacks")
  • Link to portal for full details

Real-time alerts do NOT include:

  • Workflow names or descriptions
  • API keys or credentials
  • Specific customer data processed by workflows
  • Internal notes or comments
  • Detailed configuration information

Digests include:

  • Summary statistics (signal counts by severity)
  • Aggregated impact metrics (workflow availability %)
  • High-level recommendations
  • Links to detailed reports in portal

Security considerations:

  • Notification emails are not encrypted in transit (standard email)
  • Emails may be stored in email provider systems (Gmail, Outlook, etc.)
  • Email forwarding may expose information to unintended recipients

Best practices:

  • Use corporate email accounts, not personal email
  • Avoid forwarding SignalBreak notifications outside your organization
  • Configure email retention policies per your security requirements
  • Regularly review team members and remove former employees

For highly sensitive environments: Disable email notifications and use portal-only monitoring. Consider Enterprise plan with IP allowlisting and SSO.

How quickly are real-time alerts sent after a signal is detected? ​

Target SLA: Within 5 minutes of signal detection.

Typical delivery time:

  1. Signal detected by SignalBreak monitoring: T+0 seconds
  2. Signal classified and severity assigned: T+10-30 seconds
  3. Workflow impact analysis: T+30-60 seconds
  4. Email queued for delivery: T+60-90 seconds
  5. Email sent to provider (SMTP): T+90-120 seconds
  6. Email delivered to inbox: T+2-5 minutes

Factors affecting delivery time:

  • Email provider processing delays (Gmail, Outlook, etc.)
  • Spam filtering checks (may add 1-2 minutes)
  • Network latency between SignalBreak and email provider
  • Email server queue load

If alerts arrive late (>10 minutes):

  • Check signal detection timestamp in portal vs. email timestamp
  • Verify email provider isn't queuing or rate-limiting
  • Contact support if consistent delays observed

For critical incidents requiring immediate response: Don't rely solely on email notifications. Implement:

  • Portal dashboard monitoring (refresh every 1-5 minutes)
  • Slack/Teams integration (coming Q1 2026)
  • Webhook to PagerDuty or internal on-call system (Enterprise, coming Q2 2026)

Support ​

Need help with notifications? We're here to assist:

Documentation:

Contact Support:

Feature Requests:

Enterprise Support:

  • Dedicated Slack channel
  • Priority support SLA (response within 4 business hours)
  • Custom integration assistance

Last updated: 2026-01-26

AI Governance Intelligence

© 2026 SignalBreak