Smart Routing
Channel-Based DeliveryRoute notifications to email or Slack channels based on feature categories and severity levels
Alert Fatigue Control
Intelligent FilteringConfigure severity thresholds to receive only the alerts that matter to your role
Multi-Channel Support
Flexible PreferencesReceive notifications via email, Slack, or both, tailored to each feature
Multi-Workspace
Workspace IsolationConfigure separate notification preferences for each workspace you manage
Quick Start
1
Go to Notifications Settings
In CloudThinker, navigate to Settings > Notifications
2
Select a Feature Category
Choose which CloudThinker feature you want to configure notifications for
(Alerts, Agents & Tasks, Code Review, etc.)
3
Enable Channels
Toggle Email and/or Slack on for the selected feature
4
Set Severity Level
Choose your minimum severity threshold (Critical, High, Medium, Low)
5
Verify Email (If Applicable)
For external email recipients, confirm the verification link sent to your
email address
Configuration Interface

Feature Categories
Configure notifications independently for each area:- Alerts - Critical and operational alert notifications for system events
- Agents & Tasks - Agent interruptions and task completions
- Code Review / Pipeline Monitoring - Pipeline execution status and failure notifications
- CloudKeepers / Assessment - Cost optimization recommendations and AWS assessment updates
- Discussions - Team discussion activity, replies, and resolved discussions
- Resources - Infrastructure resource changes and updates
Channel Configuration
Each feature category supports flexible channel configuration with independent control:Email Notifications

- Verified external recipients for security
- Multiple email addresses per feature
- Workspace member defaults
- Email verification required for external addresses
Slack Integration

- Channel-based routing (not direct messages)
- Reduces notification overload
- Team-wide visibility and opt-in
- Context-aware channel selection
Severity Filtering

- Low - Informational updates and general notifications
- Medium - Important updates requiring attention and review
- High - Critical issues affecting operations that need prompt action
- Critical - System-critical alerts requiring immediate action
Notification Categories in Detail
Alerts

Agents & Tasks

- Agent Interrupts - When an AI agent pauses and requires your action (e.g., to approve a tool call)
- Scheduled Task Resource Missing - When a scheduled task cannot run because a required resource was deleted or unavailable
Code Review / Pipeline Monitoring

- Pipeline execution status updates
- Pipeline failure notifications
- Code review completion alerts
CloudKeepers / Assessment

- Cost optimization recommendations from CloudKeepers
- AWS Well-Architected Assessment completion and results
- Cost anomaly detection
Discussions

- Replies - When someone replies directly to one of your comments
- Resolved Discussions - When a discussion you’re involved in is marked as resolved
Key Features
Email Verification
To prevent unauthorized access and data leakage, external email recipients must be verified before receiving notifications:- Enter the external email address in the notification settings
- A verification link is sent to that email address
- The recipient must click the verification link to confirm
- Only verified addresses receive workspace notifications
Slack Channel-Based Routing
Instead of sending direct messages to individual users, notifications route to Slack channels:- Better Context - All team members can see notifications in the channel
- Reduced Fatigue - Single channel per feature instead of individual messages
- Opt-In Subscriptions - Team members can choose to join specific notification channels
- Team Awareness - Operations visibility across your team
Multi-Workspace Support
Configure separate notification preferences for each workspace you belong to:- Different severity thresholds per workspace
- Role-specific configurations
- Workspace-specific channels
- Tailored alert strategies based on workspace context
Best Practices
Reducing Alert Fatigue
- Configure severity filters appropriately - Set High or Critical for roles that manage many features
- Use Slack channels - Route team notifications to channels instead of direct messages
- Disable unused features - Turn off notifications for features your team doesn’t actively manage
- Gradual enablement - Start with Critical alerts, then gradually add lower severity levels
Security Considerations
- Always verify external emails - Ensure only authorized recipients have access to sensitive data
- Use workspace-specific channels - Route sensitive operations to dedicated Slack channels
- Review recipients regularly - Periodically audit who receives notifications
- Restrict channel access - Limit notification channel membership to relevant team members
- Monitor notification activity - Track who receives what notifications for compliance
Configuration Strategy
- Start with Critical + High severity for critical operational alerts
- Gradually add Medium severity as your team becomes familiar with the system
- Use different channels for different features - Keep infrastructure alerts separate from cost alerts
- Tailor by role - Adjust thresholds based on team member responsibilities
- Test notification delivery - Verify emails and Slack messages are reaching intended recipients
Next Steps
🚀 Start Configuring
Begin SetupConfigure your first notification preferences in the CloudThinker Settings
🤖 Learn About Agents
Understand AgentsGet to know CloudThinker’s AI agents and their capabilities
💬 Slack Integration
Setup SlackConnect your Slack workspace for richer team collaboration
⚠️ Manage Alerts
Alert ManagementLearn how to configure alerts for different severity levels