Skip to main content
The Notifications page decides which workspace events CloudThinker sends outside the app, such as an agent waiting for approval or a failed automation, and where each one goes. Every notification also lands in the in-app notification center, which is always on and has no switch.

​
Prerequisites

  • The workspace Admin role to change settings. Developers and Viewers can open the page but can’t edit it. See workspace roles.
  • For Slack, Microsoft Teams, or Google Chat delivery: a Team plan or above (see pricing), and the integration set up:

​
Set up delivery channels

A delivery channel is where notifications go. Email is ready by default. The chat channels each post to one channel or space that you pick.
1

Open Notifications

Go to More → Workspace settings → Notifications. The page has two sections: Delivery channels and What to notify me about.
2

Choose email recipients

On the Email card, open Manage email recipients. Workspace members receive email by default. To include someone outside the workspace, such as a team alias, type the address and click Add email.Success state: the card shows Workspace members, or Members + 2 more after you add two addresses.
3

Pick a Slack channel, Teams channel, or Google Chat space

On the Slack, Teams, or Google Chat card, click Pick a channel (or Pick a space for Google Chat), then search and select one. Posting to a shared channel lets the whole team see alerts, and people opt in by joining it. Each integration posts to exactly one channel or space per workspace, so you can’t send approvals to one Slack channel and digests to another. To reach a second audience, add its email alias as an email recipient.Success state: the card shows the channel or space name. A card that says Set up, Finish setup, or Upgrade to enable isn’t delivering yet. See Troubleshooting.

​
Choose which events to send

1

Open a module group

Under What to notify me about, events are grouped by module, such as Resolve, Review, Optimize, and Agents & Tasks. Click a group to expand it.
2

Turn channels on per event

Each row is one event, and each column is a delivery channel. Turn on the cells for the channels that event should reach. A dash means that channel isn’t available for the event.
3

Set a severity threshold where offered

The Alerts and Keepers rows show a severity picker once a channel is on. Pick the lowest severity that should reach that channel:Each channel has its own threshold. For example, send Medium and above to Slack, and only Critical to email.
Success state: changes save as you make them. The next matching event posts to the channels you turned on.

​
Events you can route

The “Email on by default” column shows which events send email before anyone changes a setting. The Alerts, Keepers, and Well-Architected Assessment rows sit at the top of the list and keep their own settings, so read their current state on the page. Slack, Teams, and Google Chat cells start off, so turn on the events you want each channel to get. Automation run failed sends one notice per failure streak, not one per failed run. If the failures go on until the automation is turned off, you get Automation turned off. Two approval notices don’t have rows of their own. A destructive write that waits for a person raises a High alert, so it reaches every channel on the Alerts row whose threshold is High or lower. A break-glass use sends an in-app notification to the workspace owner and every workspace Admin, which includes every organization Owner and Admin. There’s no test button. To check routing end to end, turn on Agent approvals for a channel, set a test chat to Manual Approval mode, ask for a small write on a test connection, and then Decline the card.
Start with approvals, incidents, and connection health on a shared channel. Add digests and lower-severity events once the team knows what normal volume looks like.

​
Workspace settings vs. your own email

This page sets what the workspace sends. Each member can mute their own copy of an email from Account Settings → Notifications, without changing it for anyone else. For an event whose email is off by default, a member can turn on their own copy there. Personal settings cover email only: Slack, Teams, and Google Chat posts follow this page and the channel’s own settings.
An Agent CLI session doesn’t send approval notifications on its own, because the approval card is already in your terminal and browser. Run /cloudthinker notify in the session to alert the workspace approvers once.

​
Troubleshooting

Slack, Teams, and Google Chat delivery need a Team plan or above. Email and in-app notifications work on every plan. See Subscription.
Set up means the integration isn’t connected yet. For Teams, Finish setup means the bot isn’t installed or the workspace isn’t mapped. For Google Chat, an organization admin must map a space to this workspace. Follow the integration guide linked in Prerequisites.
The picker searches as you type and matches partial names. If the channel still doesn’t show, check that the CloudThinker app can see it in Slack, then search again.
Changing notification settings needs the workspace Admin role. Ask a workspace Admin to change them, or to change your role.
Check that the email cell is on for that event, that (for Alerts and Keepers) the severity threshold isn’t higher than the event, and that the recipient hasn’t muted their own copy in Account Settings → Notifications. The in-app notification center always has the record.

​
Next steps

Slack integration

Connect Slack so notifications and approvals reach a channel

Approvals

Decide which agent writes ask a person, and who answers

Teams integration

Install the bot and map workspaces for Teams delivery

Google Chat integration

Map a Google Chat space to receive workspace notifications