The bell in the top bar is Message Center (/messages). It is the inbox inside the signed-in app. There is no Message Center item in the sidebar.

Each person has their own messages. Marking one read updates your list only.

Open the inbox

Click the bell. The page title is Message Center. Under it, Learn more opens this page, and Notification settings opens workspace Preferences. Opening the list does not mark anything read.

Badge on the bell

What you have unread	Badge	Accessible name
Nothing	Icon only. No count.	Message Center
Unread messages, none critical	The unread count, or 99+ when the count is over 99. Primary color.	Message Center, N unread (N is the full count, including when the badge shows 99+)
At least one critical unread message	The same total count, with the same 99+ cap. Error color.	Message Center, N unread, includes critical items

Critical means the platform treats that message as a failure, such as a failed readiness scan. A warning can still show under Needs action. A warning alone does not switch the bell to the error color.

The badge uses the same filters as the list. Hide a type in preferences and those messages drop out of the count and out of the critical color. A successful run titled Productivity ingest completed never appears in the list or on the badge.

Filter the list

Needs action is the default tab. It shows warnings and failures. All shows every message, including successes.

Unread keeps the current tab and shows unread messages only. Turn it off to see read and unread together.

Rows are grouped on your computer’s local calendar: Today, Earlier this week (the previous 6 local days), and Earlier.

Inside a day, messages that share a title, a severity, and a link are one row. The row shows the title, a small severity label (Failed, Warning, Success, or Muted), the newest time, and a count. One unread dot stays when any message in the group is unread. Open the row to see each message. Opening the group does not mark anything read and does not leave the page. A message that does not repeat stays one row, with no expand control.

A row shows the title, the severity label, up to two lines of the message, and a relative time. Unread rows have one dot. There is no icon on the row.

Select the checkbox on a row, or the checkbox in the card header for every message on the current tab. Checking a collapsed group selects each message in it. Mark read marks only that selection. Mark all read still marks every message for you.

Mark unread is on a message you have already read. It puts that message back on the unread badge. It does not open the message.

When the list is longer than one page, the count under the list is how many you have loaded of the total, and Load more fetches the next page.

Click a message to mark that message read. If it links to a page in the app, you go there. If it has no link, you stay on Message Center.

Empty list and load errors

If this filter has no rows and nothing is unread, the page says You’re caught up. Notification settings opens workspace Preferences.

If Needs action is empty and All still has messages, the page says Nothing needs action. The control on that empty state switches to All.

If the list loaded and the unread badge still counts messages that are not in this list, the page says The unread badge is out of date. Retry loads the list and the badge again. Could not load notifications. appears only when the list request fails.

In-app preferences

Open the workspace menu in the top bar, then {workspace} settings → Preferences. That page has three switches: Status updates, Team activity, and System announcements. They choose which of those types appear in Message Center and on the bell for this workspace. The helper text on that screen says the switches control Message Center. Another workspace keeps its own switches.

Email

Under the switches, each type has an email row. The labels match the switches: Status updates, Team activity, and System announcements.

Row	Choices	Default
Status updates	As it happens, Weekly digest	Weekly digest
Team activity	Off, As it happens, Weekly digest	Off
System announcements	Off, As it happens, Weekly digest	Off

Off means that type is not emailed, including when the message is critical. Status updates has no Off choice.

Mail goes to the email on your account. Each workspace sends its own mail.

Weekly digest is one email on Monday at 8:00am in the timezone from Settings → Preferences, covering the previous 7 days. The first item, when there is something to say, is Agentic Foundation this week: how many repositories are blocked, the most common blocking rule, and how many merged fixes the next scan cleared. The same text is one unread Status message in Message Center for that week. A retry does not add a second copy. If that summary is empty and the week has no other status messages, no digest is sent. A missing or invalid timezone uses UTC.

As it happens sends when the message is created. Quiet hours are 8:00pm until 8:00am in that timezone, and they are fixed. A non-critical message created in that window waits until 8:00am.

A critical message (a failure, such as a failed readiness scan) emails immediately, including during quiet hours, when that row is As it happens or Weekly digest. That message is left out of the Monday digest. Reading it in Message Center does not cancel that mail.

If you have already read a message in Message Center, it is left out of the Monday digest. A non-critical message that has not been emailed yet is also skipped once you read it.

An integration message uses the Status updates email row.

Emails other than Status updates include a link to workspace Preferences and an unsubscribe link. Opening unsubscribe shows a confirmation page and leaves your settings as they are. Confirming sets that row to Off and opens workspace Preferences. Status updates mail has no unsubscribe link. Status email stays on.

Slack and Teams

Slack and Teams are optional posts for the same messages. They sit on workspace Preferences, beside the email rows, and they use the same three labels: Status updates, Team activity, and System announcements. An integration message uses the Status updates row for Slack and the Status updates row for Teams.

A workspace admin connects each app from this page. Connect Slack opens Slack’s install screen, where the admin installs the app and picks the channel. A private channel appears on that screen only if the admin is already in it. Connect Teams is on the next row. It uses Microsoft sign-in, then the admin chooses one channel. After the app is connected, every member turns on their own rows, including workspace admins. Admins do not turn chat on for other people. The admin can disconnect either app.

This connection is for notifications. Onboarding does not require it. It is separate from the Slack and Teams tiles in the tech stack catalog, which are still coming soon.

Until Slack is connected, the Slack rows are disabled and nothing is posted to Slack. Slack offers Off and Channel. Channel turns on after connect, because the channel was chosen on Slack’s screen. Until Teams is connected, the Teams rows are disabled and nothing is posted to Teams. Teams Channel stays disabled until the admin saves a channel. A channel post is sent only when someone has Channel selected and a message is delivered. Connecting or saving a channel does not post by itself.

Choice	What you get
Off	No post for you. Every Slack row and every Teams row starts here.
Direct message	Teams only. A direct message to the Teams user that uses the same email as your account. If no user matches, that person’s message is skipped and is not posted to the channel in their place. Slack does not send direct messages.
Channel	One post in the channel chosen for that app. Slack uses the channel from the install screen. Teams uses the channel the admin saved. When several people choose Channel for the same message, the channel still gets a single post.

Rows stay Off until that person changes them. Slack posts start after someone sets a row to Channel. Teams posts start after someone sets a row to Direct message or Channel. The three switches still control which types appear in Message Center. Status email still sends when Slack and Teams stay Off.

An admin disconnect stops later posts for that app. The rows are disabled again until an admin connects it.

Sample workspace

From the sign-in screen, choose Try it with sample data. The sample bell and Message Center use the same badge, tabs, groups, and read actions as a signed-in workspace. Workspace Preferences shows the email table, with Status updates on Weekly digest and the other email rows set to Off. Connect Slack and Connect Teams are on that page. Choosing either tells you the sample workspace does not connect chat. The Slack and Teams rows stay Off. Account Settings → Preferences does not change the sample inbox.

Related

• Settings