Notification Management
Interlynk provides a two-tier notification system: organization-level defaults and user-level overrides. Notifications can be delivered via Slack, Microsoft Teams, and email through configured integrations.
Organization-Level Notifications
Organization-level notification settings define the baseline notification behavior for all users and integrations.
Configuring Defaults
Navigate to Settings > Organization > Notifications.
The notification table displays all available notification types, each with:
Active
Toggle to enable or disable the notification type
Notification
Name of the notification event
Description
What triggers this notification
Level
Severity level: Alert, Warning, or Info
Toggle individual notifications on or off.
Changes are saved automatically via bulk update.
Severity Thresholds
Notification levels control the urgency of the message:
Alert
Orange
High-priority events requiring immediate attention (e.g., critical vulnerability discovered)
Warning
Red
Significant events that should be reviewed soon (e.g., policy violation)
Info
Blue
Informational events for awareness (e.g., SBOM upload completed)
Organization admins set the default level for each notification type. Users can override these at the personal level.
Integration-Based Notifications
Organization-level notifications are delivered through all configured integrations:
Slack: Messages sent to configured webhook channels.
Microsoft Teams: Messages sent to configured webhook channels.
Email: Messages sent to configured email addresses.
Each integration can be configured with its own notification type filter (All, Alert, Warning, Info) — see Integrations for details.
User-Level Notifications
Users can customize their personal notification preferences to override organization defaults.
Personal Notification Settings
Navigate to Settings > Personal > Notifications.
The Messages tab displays the same notification types as the organization settings.
Toggle individual notifications on or off for your account.
Your personal settings override the organization defaults for notifications delivered to your personal channels.
Project-Specific Preferences
The Preferences tab allows fine-grained control over which products and categories trigger notifications:
Navigate to Settings > Personal > Notifications > Preferences.
The table is organized by product group (expandable rows).
For each product/environment, select the notification categories:
All
All notification categories
Vulnerabilities
New vulnerabilities, severity changes, VEX updates
Licenses
License compliance violations
Policies
Policy scan results, violations
Uploads
SBOM uploads, processing completions
None
Suppress all notifications for this product
Click Save for each product to apply preferences.
Email vs. Integration Preferences
Personal email notifications: Controlled by the email integration at the organization level and user notification settings.
Slack/Teams notifications: Controlled by the organization's webhook configurations — these are channel-level, not user-level.
In-app notifications: Controlled by the user's personal notification preferences.
Users who want to receive notifications only for specific products should use the Preferences tab to select categories per product rather than disabling notifications globally.
Digest vs. Real-Time
Instant: Notifications are sent as soon as the event occurs. This is the current default delivery frequency.
Integration connections (Slack, Teams, Email) support a frequency setting, currently set to Instant.
Common Misconfigurations
All notifications disabled at org level
No one receives any notifications
Re-enable critical notification types in org settings
User overrides not taking effect
User still receives notifications they disabled
Verify the user's personal settings are saved correctly
Slack/Teams notifications but no email
Email integration not configured
Add an email connection in the integrations settings
Too many notifications
Notification fatigue
Use category-based filtering per product and raise the severity threshold
Notifications for irrelevant products
User receives alerts for products they don't manage
Configure product-specific preferences in the Preferences tab
Recommended Best Practices
Enable alerts for critical events at the organization level (e.g., critical vulnerabilities, policy failures) and allow users to opt into informational notifications.
Use product-specific preferences to reduce noise — team members should only receive notifications for products they own.
Configure at least two delivery channels (e.g., Slack + email) for critical alerts to ensure delivery even if one channel has issues.
Review notification settings quarterly as team membership and product ownership change.
Avoid the "All" notification type on high-volume Slack channels — filter to Alert or Warning to prevent channel overload.
Last updated