Act on notifications

Notifications are the workspace tapping you on the shoulder. Each one carries a title, a line of detail, and a link to the thing it is about, so acting on one is a single click.

The bell

The bell sits at the bottom of the sidebar with an unread count on it (it stops counting at 9+). Selecting it opens a panel with your five most recent notifications, newest first, unread ones highlighted.

From the panel you can:

• Select a notification to mark it read and follow it to the meeting, task, or page it points at.
• Mark all read, which clears the count without opening anything.
• View all notifications, which opens the full inbox.

The panel updates live. A notification raised while you are looking at it appears without a refresh.

The inbox

View all notifications opens the Notifications page on its Inbox tab: the same list, without the five-item limit, each entry showing its full body, its action, and when it arrived.

Selecting an entry does the same two things the panel does: marks it read, and follows its link.

What generates one

1. You are invited to a meeting

   Adding someone as a participant on a meeting they did not create notifies them, with a link to the meeting.

2. A meeting you are in starts

   Every human participant is notified when the meeting goes live, with a Join Meeting action.

3. Something needs your approval

   When an agent hits an action its autonomy level will not let it take alone, the request lands in your approvals queue and you are told about it. The notification names the action and what it is against, and Review opens the queue.

   You are notified as the person holding the approving role, so a request routed to a role an agent holds notifies nobody: agents do not have an inbox.

4. An agent acts, then asks you to review

   At L2 on the autonomy ladder an agent acts first and is reviewed after. When it does, you get a notification naming the operation, and a review task is created alongside it so the work is on your list rather than only in your inbox.

The notification is not the decision

Approving and denying happen in the approvals queue, never in the inbox. The notification is how you learn there is a decision waiting; the queue is where the run or agent that raised it is waiting for your answer.

Delivery to email and Slack

The Notifications page’s second tab, Delivery Settings, forwards workspace events to a destination outside the app. Email and Slack are the destinations that deliver today.

1. Choose a scope

   DEFAULT subscribes to events across the workspace. TASK narrows to a single task, which accepts a short key such as SUM-14.

2. List the event types

   A comma-separated list, for example task.created,approval.requested,agent.paused.

3. Add a destination

   An email address, or a Slack incoming webhook URL with an optional channel.

4. Select Subscribe

   The subscription appears under Active Subscriptions with its scope, its events, and its destinations. Delete removes it.

Next steps

• Read the cockpit: the live activity feed, which is broader than your notifications.
• Jump anywhere with the command palette: reach a task without leaving the keyboard.
• The autonomy ladder: what decides between acting, notifying, and asking.