> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt > Use this file to discover all available pages before exploring further. # Notifications Center > Configure and manage role-specific notifications across email, Slack, and Microsoft Teams channels for timely cloud operations alerts Stay informed about critical cloud operations with intelligent, role-specific notifications. Configure how and where you receive alerts for CloudThinker features with flexible severity filtering and multiple delivery channels. *** ## The Problem With Alert Fatigue Generic cloud alerting sends everything to everyone — and when everyone gets everything, nobody reads anything. Security engineers don't need to see every cost recommendation. Finance teams don't need Kubernetes OOMKill alerts. On-call engineers don't need compliance digest emails at 3 AM. The result: critical alerts get buried in noise, teams disable notifications entirely, and important findings go unacted on. CloudThinker's Notifications Center solves this with role-based routing and severity filtering: each team member configures what they care about, at what severity threshold, through which channel — so the right person gets the right alert at the right time. **Channel-Based Delivery** Route notifications to email or Slack channels based on feature categories and severity levels **Intelligent Filtering** Configure severity thresholds to receive only the alerts that matter to your role **Flexible Preferences** Receive notifications via email, Slack, Microsoft Teams, or any combination, tailored to each feature **Workspace Isolation** Configure separate notification preferences for each workspace you manage *** ## Quick Start In CloudThinker, navigate to **Settings > Notifications** Choose which CloudThinker feature you want to configure notifications for (Alerts, Agents & Tasks, Code Review, etc.) Toggle Email, Slack, and/or Microsoft Teams on for the selected feature Choose your minimum severity threshold (Critical, High, Medium, Low) For external email recipients, confirm the verification link sent to your email address *** ## Configuration Interface Notifications main settings page showing Slack notification channel configuration The notification system organizes around CloudThinker's core features, allowing independent configuration for each area. Access comprehensive settings by selecting each feature category. ### 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](/guide/code-review/setup) / Pipeline Monitoring** - Code review findings with severity breakdown, pipeline execution status, and failure notifications * **[CloudKeepers](/guide/infrastructure/cloudkeepers) / [Assessment](/guide/infrastructure/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 Email recipients input form showing how to add multiple email addresses for notifications Send notifications to verified email addresses, supporting both workspace members and external recipients. **Key Features:** * Verified external recipients for security * Multiple email addresses per feature * Workspace member defaults * Email verification required for external addresses ### [Slack Integration](/guide/slack-integration) Slack channel dropdown selector showing available channels for notification routing Route notifications to Slack channels instead of direct messages, reducing notification fatigue while maintaining team awareness. Start typing to filter channels by name — the search matches partial names and is case-insensitive, making it easy to find channels in large workspaces. **Key Features:** * Channel-based routing (not direct messages) * Searchable channel picker with type-ahead filtering * Reduces notification overload * Team-wide visibility and opt-in * Context-aware channel selection ### [Microsoft Teams Integration](/guide/teams-integration) Route notifications to Microsoft Teams channels using Adaptive Cards for rich, structured alerts. Teams notifications work the same way as Slack — configure per-feature categories, select a Teams channel, and set severity thresholds. **Key Features:** * Adaptive Card format with structured data and action buttons * Channel-based routing with searchable picker * Per-category channel selection (e.g., code review findings to `#code-reviews`, incidents to `#incidents`) * Same severity threshold filtering as other channels * Requires [Teams integration](/guide/teams-integration) to be connected first *** ## Severity Filtering Alerts section showing email and Slack severity filter controls with High and Medium thresholds Filter notifications by severity level to receive only alerts meeting your threshold: * **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 Each channel can have independent severity thresholds. For example, configure Slack for Medium and above while Email is set to High and above. *** ## Notification Categories in Detail ### Alerts Alerts configuration showing system alerts with severity filtering for email and Slack channels System-wide alert notifications for critical events and important operational updates requiring attention. ### Agents & Tasks Agents & Tasks section showing agent interrupts and scheduled task resource missing notifications with channel toggles Notifications for AI agent activity and task execution: * **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](/guide/code-review/setup) / Pipeline Monitoring Code Review section showing pipeline monitoring notifications with email enabled and Slack disabled #### Pipeline Monitoring * Pipeline execution status updates * Pipeline failure notifications with AI-analyzed logs #### Code Review Findings When an AI code review completes on a pull/merge request, CloudThinker sends a notification with: * **Severity summary** — count of critical, high, medium, and low findings * **Finding details** — title, severity, file path, and line number for up to 10 findings * **Resolved tracking** — count of previously identified findings that have been resolved * **Action link** — direct link to the code review dashboard Code review findings notifications are sent automatically after each review completes. Configure severity thresholds to control which reviews trigger a notification — for example, set to **High** to only be notified when critical or high-severity findings are detected. Each notification channel renders findings in its native format: * **Slack** — [Block Kit message](/guide/slack-integration#code-review-notifications) with severity emoji indicators * **Microsoft Teams** — [Adaptive Card](/guide/teams-integration#code-review-notifications) with FactSet severity table * **Email** — HTML table with findings details and dashboard link ### [CloudKeepers](/guide/infrastructure/cloudkeepers) / [Assessment](/guide/infrastructure/assessment) Assessment section showing AWS Well-Architected Assessment notification configuration with toggles for email and Slack channels Notifications for cost optimization and cloud assessment updates: * Cost optimization recommendations from [CloudKeepers](/guide/infrastructure/cloudkeepers) * AWS [Well-Architected Assessment](/guide/infrastructure/assessment) completion and results * Cost anomaly detection ### Discussions Discussions section showing replies and resolved discussions notification options with email enabled Notifications for team collaboration activities: * **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: 1. Enter the external email address in the notification settings 2. A verification link is sent to that email address 3. The recipient must click the verification link to confirm 4. Only verified addresses receive workspace notifications This ensures that sensitive cloud operations data is only distributed to intended recipients. ### 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 or Teams 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 or Teams 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 1. **Start with Critical + High severity** for critical operational alerts 2. **Gradually add Medium severity** as your team becomes familiar with the system 3. **Use different channels for different features** - Keep infrastructure alerts separate from cost alerts 4. **Tailor by role** - Adjust thresholds based on team member responsibilities 5. **Test notification delivery** - Verify emails and Slack messages are reaching intended recipients *** ## Next Steps **Begin Setup** Configure your first notification preferences in the CloudThinker Settings **Understand Agents** Get to know CloudThinker's AI agents and their capabilities **Setup Slack** Connect your Slack workspace for richer team collaboration **Setup Teams** Connect your Microsoft Teams workspace for Adaptive Card notifications **Alert Management** Learn how to configure alerts for different severity levels