For the complete documentation index, see llms.txt. This page is also available as Markdown.

Notifications

What triggers a notification, where notifications appear, and how to mark them read or unread.

The notification panel surfaces team-membership events: invites you've sent and invites that have been accepted. Click the bell icon at the top-right of any workspace to open the panel.

Notifications dropdown open from the bell icon, showing All / Unread tabs across the top, a Mark all as read action, and the empty state "No Notifications - You're all caught up. New notifications will appear here" with a Refresh button

What triggers a notification

Event
Notification

You send a team invite

Invite-sent notification

A teammate accepts a team invite

Invite-accepted notification

There are no in-app toasts. The bell dropdown is the only surface; the small dot on the bell icon is the only ambient signal.

Where they appear

  • Bell icon at the top-right of the workspace. Shows a small dot indicator when there's anything unread. Click for the full panel.

Reading and managing

The panel has two tabs across the top – All and Unread – plus a Mark all as read action. Each row in the panel is a notification with read / unread state and a click action that navigates to the relevant resource (the shared project, the comment thread, the rendered output). Notifications are dismissible; once you act on them, they go away.

When the panel is empty: "No Notifications. You're all caught up. New notifications will appear here." plus a Refresh button to manually pull.

Limits and known issues

  • Notifications scope to the active workspace. Switching workspaces shows that workspace's notifications.

  • The notification feed has a finite history. Past several hundred entries, older notifications roll off. Keep what you need until you've acted on it.

Last updated

Was this helpful?