Skip to main content

Notifications

Guardian Pro's notification system keeps your team informed about security findings, cost anomalies, compliance changes, and remediation outcomes. With seven notification channels and integrations with popular collaboration tools, you can ensure the right people receive the right information at the right time.

Accessing Notification Settings

Navigate to Settings > Notifications from the left sidebar. You need the org:read permission to view notification preferences and org:write to modify them.

Notification Channels

Guardian Pro supports seven notification channels. Each channel serves a different purpose and cadence:

1. Instant Alerts

Instant alerts are sent in real time when critical or high-severity events occur. These are designed for issues that require immediate attention.

Triggers include:

  • New critical or high-severity security findings.
  • Cost anomalies exceeding configured thresholds.
  • Remediation failures or rollback events.
  • Account connectivity issues.

Instant alerts are delivered via email and, when configured, through webhooks to Slack or Microsoft Teams.

tip

Configure instant alerts for at least your critical findings. Timely notification of critical security issues can significantly reduce your exposure window.

2. Daily Digest

The daily digest provides a summary of the previous 24 hours of activity, delivered once per day at a configured time.

The digest includes:

  • New findings discovered, grouped by severity.
  • Findings resolved or remediated since the last digest.
  • Cost summary and any anomalies detected.
  • Compliance score changes.
  • Scan completion summaries.

3. Weekly Summary

The weekly summary provides a higher-level view of your environment's posture over the past week. It is delivered once per week on a configured day.

The summary includes:

  • Week-over-week trends in findings (new vs. resolved).
  • Health score trend and current value.
  • Top unresolved findings by severity.
  • Cost trend and optimisation opportunities identified.
  • Compliance score changes across subscribed frameworks.

4. Monthly Report

The monthly report is a comprehensive overview of your Guardian Pro activity for the calendar month. It is designed for management review and audit documentation.

The report includes:

  • Monthly executive summary.
  • Finding trends and resolution metrics.
  • Cost analysis summary with month-over-month comparison.
  • Compliance posture across all subscribed frameworks.
  • Remediation activity log.
  • Recommendations for the coming month.
info

Monthly reports are available on the Business and Enterprise tiers. On the Enterprise tier, monthly reports can be automatically generated as PDF and delivered via email or webhook.

5. Projected Savings

Projected savings notifications highlight cost optimisation opportunities identified by Guardian Pro's cost intelligence engine. These are sent when new savings opportunities are identified that exceed a configurable threshold.

Notifications include:

  • Rightsizing recommendations with projected savings.
  • Reserved instance and savings plan opportunities.
  • Idle or underutilised resource cleanup suggestions.
  • Total estimated monthly savings if all recommendations are implemented.

6. Webhooks

Webhooks allow Guardian Pro to send structured notifications to external systems. This channel supports integration with:

  • Slack -- Send notifications to Slack channels via incoming webhooks.
  • Microsoft Teams -- Send notifications to Teams channels via incoming webhooks.
  • Custom endpoints -- Send JSON payloads to any HTTPS endpoint for integration with your own tools, ticketing systems, or automation workflows.

For configuration details, see Webhook Integration below.

7. Notification Preferences

Per-user preferences allow individual users to customise which notifications they receive and through which channels. Users can override organisation-level defaults for their own account.

Configuring Channels

Enabling and Disabling Channels

Each channel can be independently enabled or disabled:

  1. Navigate to Settings > Notifications.
  2. Find the channel you want to configure.
  3. Toggle the channel on or off.
  4. Configure channel-specific settings (delivery time, threshold, etc.).
  5. Click Save.

Channel-Specific Settings

ChannelConfigurable Settings
Instant AlertsSeverity threshold (Critical only, Critical + High, etc.), delivery method (email, webhook, both)
Daily DigestDelivery time (UTC), recipients
Weekly SummaryDelivery day and time, recipients
Monthly ReportDelivery day (1st-28th), recipients, format (email, PDF attachment)
Projected SavingsMinimum savings threshold (e.g., only notify if savings exceed $100/month)
WebhooksEndpoint URL, event types, payload format

Webhook Integration

Webhooks enable real-time integration with external tools. Guardian Pro supports Slack, Microsoft Teams, and custom HTTPS endpoints.

Slack Integration

To send notifications to Slack:

  1. In Slack, create an Incoming Webhook for your target channel (see Slack's documentation).
  2. Copy the webhook URL.
  3. In Guardian Pro, navigate to Settings > Notifications > Webhooks.
  4. Click Add Webhook.
  5. Select Slack as the type.
  6. Paste the webhook URL.
  7. Select which event types to send (findings, cost anomalies, remediations, etc.).
  8. Click Test to send a test notification.
  9. Click Save.

Microsoft Teams Integration

To send notifications to Microsoft Teams:

  1. In Teams, add an Incoming Webhook connector to your target channel (see Microsoft's documentation).
  2. Copy the webhook URL.
  3. In Guardian Pro, navigate to Settings > Notifications > Webhooks.
  4. Click Add Webhook.
  5. Select Microsoft Teams as the type.
  6. Paste the webhook URL.
  7. Select event types and click Test.
  8. Click Save.

Custom Webhooks

For integration with ticketing systems, SIEM tools, or custom automation:

  1. Navigate to Settings > Notifications > Webhooks.
  2. Click Add Webhook.
  3. Select Custom as the type.
  4. Enter the HTTPS endpoint URL.
  5. Optionally, add custom headers (e.g., authentication tokens).
  6. Select event types.
  7. Click Test to verify connectivity.
  8. Click Save.
caution

Webhook endpoints must use HTTPS. HTTP endpoints are not supported. Guardian Pro validates webhook URLs against a security allowlist to prevent misuse. Only recognised webhook domains (such as Slack and Microsoft Teams) and verified custom domains are accepted.

Webhook Event Types

You can select which events trigger webhook notifications:

Event TypeDescription
New FindingsTriggered when new security or cost findings are discovered
Finding ResolvedTriggered when a finding is resolved or remediated
Cost AnomalyTriggered when a cost anomaly is detected
Remediation StatusTriggered when a remediation completes or fails
Scan CompleteTriggered when a scan finishes
Compliance ChangeTriggered when a compliance score changes significantly

Webhook Payload

Webhook payloads are sent as JSON and include:

  • Event type and timestamp.
  • Summary of the event.
  • Affected resources and their details.
  • Severity and priority indicators.
  • Direct link to the relevant page in Guardian Pro.

Per-User Preferences

Individual users can customise their own notification preferences without affecting other users:

  1. Click your profile icon in the top-right corner.
  2. Select Notification Preferences.
  3. Toggle channels and event types on or off.
  4. Click Save.

Per-user preferences override organisation-level settings for that user only. For example, a user can disable daily digest emails while other users continue to receive them.

note

Per-user preferences only control what that user receives. They cannot enable channels that the organisation has disabled or subscribe to channels not available on your subscription tier.

Notification History

Guardian Pro maintains a notification log accessible from the notification bell icon in the header. The log shows:

  • The 50 most recent notifications.
  • Unread notification count (displayed as a badge on the bell icon).
  • Click any notification to navigate directly to the relevant page.

Channel Availability by Tier

ChannelStarterBusinessEnterprise
Instant AlertsEmail onlyEmail + webhooksEmail + webhooks
Daily DigestEmailEmailEmail + webhook
Weekly SummaryEmailEmailEmail + webhook
Monthly ReportNot availableEmailEmail + PDF + webhook
Projected SavingsNot availableEmailEmail + webhook
WebhooksNot availableSlack + TeamsSlack + Teams + Custom
Per-User PreferencesBasicFullFull

Troubleshooting

Not receiving email notifications

  • Check your spam or junk folder.
  • Verify your email address is correct in your user profile.
  • Ensure the notification channel is enabled in organisation settings.
  • Check that your per-user preferences have not disabled the channel.

Webhook not delivering

  • Verify the webhook URL is correct and accessible.
  • Ensure the endpoint uses HTTPS.
  • Check that the endpoint responds with a 200 status code.
  • Use the Test button to send a test payload and review the response.
  • Review the webhook delivery log for error details.

Too many notifications

  • Adjust the severity threshold for instant alerts (e.g., Critical only).
  • Increase the minimum savings threshold for projected savings notifications.
  • Disable channels you do not need.
  • Use per-user preferences to fine-tune individual delivery.

Next Steps

  • Scan Preferences -- Configure what triggers findings that generate notifications.
  • Action Centre -- Act on the findings you are notified about.
  • Cost Intelligence -- Explore the cost data behind savings notifications.
  • Subscription -- Check which notification channels are available on your tier.