Notifications
The Studio inbox at /notifications — deploys, failures, comments, member changes, sessions, rollbacks.
The Notifications page (/notifications) is the personal inbox for everything Studio thinks you should know about. It catches workspace events that involve you directly (mentions, deploys you triggered) and the ones you've opted into.
Layout
The header pill row is the filter set:
- All — every notification, with a count.
- Unread — only unread, with a count.
- Deploys — successful deploys to any instance you have access to.
- Failures — failed deploys, including reason.
- Comments — when a teammate comments on a patch or page.
- Members — when someone is added to or removed from the workspace.
- Sessions — when a teammate opens a project you're on in Studio.
- Rollbacks — when a prior deploy is rolled back, with the reason field shown.
The Mark all as read action clears unread state on the visible filter.
Notification rows
Each row carries:
- Icon / avatar for the person or system that triggered the event.
- Headline — e.g. "Acme Member Portal deploy succeeded", "GitHub deployment failed for IEC", "Lee left a comment on BUW Underwriting Console".
- Detail line — version, commit summary, error message excerpt, or comment preview.
- Timestamp — relative ("2 minutes ago", "yesterday").
- Context — the instance URL and project name where the event happened.
- Actions —
MARK READ/MARK UNREADper row.
Empty state
If you have no notifications, the page shows: "Your inbox is empty. Once a deploy lands, a teammate comments, or someone @-mentions you, it'll show up here."
Where this lives in code
app/notifications/page.tsx— the inbox UI.