Notifications Center

Configure how and where you receive alerts for each CloudThinker feature. Route notifications to email, Slack, Microsoft Teams, or Google Chat, with independent severity thresholds per channel.

​

Set up notifications

​

Notification categories

Each feature category is configured independently, with its own channels and severity threshold.

​

Alerts

System-wide alert notifications for critical events and important operational updates.

​

Agents & tasks

• Agent Interrupts — an agent pauses and requires your action, for example to approve a tool call
• Scheduled Task Resource Missing — a scheduled task cannot run because a required resource was deleted or is unavailable

​

Review / pipeline monitoring

​

Review / Pipeline monitoring

​

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

Each channel renders findings in its native format: Slack uses a Block Kit message, Microsoft Teams an Adaptive Card with a severity table, and email an HTML table with a dashboard link.

​

Discussions

• Replies — someone replies directly to one of your comments
• Resolved Discussions — a discussion you are involved in is marked as resolved

​

Resources

Infrastructure resource changes and updates.

​

Optimize

Cost-side notifications from Optimize, the cost-optimization module:

• Optimize refresh paused — a connection needs attention before Optimize can refresh its cost data. Spend figures stop updating until the connection is fixed; see when a connection breaks.
• Optimize report ready — a scheduled cost report finished and is ready to read, with a link to its conversation.

​

Connections

One category pair covers connection health for every provider:

• Connection needs attention — a connection’s credentials stopped working in the background (an expired token, a revoked key), so scheduled work that depends on it pauses. You get one notification per outage, not one per failed retry, and only for failures found in the background — a connection test you run yourself never notifies.
• Connection discovery finished — discovery, the automatic read-only first look at a newly connected service, published opportunities that are ready to review.

​

Channels

​

In-app

Every notification always lands in the notification center inside CloudThinker — in-app delivery is always on and has no toggle. Channel switches and severity thresholds control only external delivery, so the center stays the complete record even for categories muted on every other channel.

​

Email

Each feature can notify multiple addresses — workspace members by default, plus external recipients. External addresses must be verified before they receive anything: enter the address, a verification link is sent, and only after the recipient confirms it does the address receive workspace notifications. This keeps sensitive operations data away from unintended recipients.

​

Slack

Notifications route to Slack channels rather than direct messages, so the whole team sees them in one place and members opt in by joining the channel. The channel picker filters as you type — the search matches partial names and is case-insensitive.

​

Microsoft Teams

Teams notifications work the same way as Slack — pick a channel per feature category and set severity thresholds. Messages arrive as Adaptive Cards with structured data and action buttons. Connect the Teams integration first.

​

Google Chat

Shared Google Chat spaces mapped to the workspace can receive notifications; direct messages cannot. Connect the Google Chat integration, then select a mapped space per feature category.

​

Severity filtering

Set a minimum severity per channel to receive only alerts that meet your threshold: Thresholds are independent per channel — for example, Slack at Medium and above while email stays at High and above.

​

Best practices

• Start with Critical and High severity, then add lower levels as your team settles in.
• Route team notifications to Slack, Teams, or Google Chat channels instead of individual inboxes.
• Turn off categories your team does not actively manage.
• Keep sensitive operations in dedicated channels with restricted membership, and review recipients periodically.
• Tailor thresholds by role — someone covering many features needs a higher floor than a specialist.

​

Next steps