Inbox

Inbox is your workspace notification queue. It collects review requests, comments, mentions, replies, Issue activity, Issue deadlines, lifecycle updates, Meeting recovery events, access request updates, and direct access changes so you can triage them without leaving the current workspace.

Open Inbox from the top workspace navigation.

Work through notifications

Inbox uses a queue/detail workspace:

• The left rail lists notifications for the selected control state.
• The right pane shows the complete canonical page or workflow for the selected notification, opened to the relevant tab and focused item when it still exists.
• The filter action opens typed filters for notification type, sender, Team, Project/Feature, Initiative, Issue priority, and Issue status type when display-safe options exist.
• The display action controls ordering, read visibility, unread-first ordering, and whether row IDs are shown.
• The more action includes scoped Mark all as read, Delete all, and Delete all read commands.

When a filter has no notifications, the left rail stays quiet and the empty state appears in the detail pane.

Filter and display the queue

Use Add Filter to narrow the queue. Multiple filters combine with AND-style behavior, so selecting an Issue priority and a Team shows notifications that match both.

Active filters appear under the Inbox header as removable chips. If a previously selected object is no longer available or visible, Inbox keeps the chip removable without exposing private names or identifiers.

Display options are local to the Inbox URL:

• Newest and Oldest choose queue order.
• Show read controls whether read notifications remain visible.
• Show unread first groups unread rows before read rows within the selected order.
• ID shows a display-safe identifier/reference before the row name.

Snooze/reminder controls are not available in this version. Inbox does not pretend to support snoozed notifications until real reminder storage and freshness behavior exist.

Triage a notification

Select a notification to open its real product context. Depending on the event, the right pane opens an Artefact, Issue, Feature, Initiative, Meeting Minute, Module, Folder, access-request list, or member list. Comments, replies, Activity entries, reviews, deadlines, requests, members, and recovery states are focused when a stable reference still exists. If the referenced item has disappeared, Inbox keeps the containing canonical page visible with safe unavailable copy.

Unread notifications are marked read after they remain selected for a short moment, and clicking a row marks it read immediately.

Each row keeps its notification triage actions:

• Mark read or unread.
• Flag or remove a follow-up flag.
• Archive or unarchive.

The destination pane does not repeat a notification header, Details card, or second read/flag/archive action group. Actions that belong to the destination, such as reviewing an Artefact or resolving an access request, remain in that canonical workflow.

The actor mark identifies who or what executed the event—person, Integrity AI, coding agent, workflow, or system—while the compact action badge identifies what happened.

Bulk cleanup deletes only your notification rows in the current Inbox scope. It does not delete Issues, sources, folders, artefacts, reviews, access requests, lifecycle updates, or audit evidence.

On desktop, keyboard shortcuts are available while you are not typing in a field: j or ArrowDown moves down, k or ArrowUp moves up, Enter opens the related item, Shift+R toggles read state, Shift+F toggles the flag, and Shift+A archives or unarchives.

Access requests AdminA

Source and folder access requests appear in Inbox for responders who can act on them. Selecting a responder notification opens the canonical Module or Folder access surface with the exact request focused. Approve or deny there and, when approving, choose the role offered by the request flow. Only users with the current effective capability see the supporting reader and actions.

Requesters also receive Inbox notifications when a request is submitted, approved, denied, cancelled, or closed.

Restricted modules

Inbox can show that a notification exists without revealing restricted module, folder, artefact, Team, or object details. Destinations always check current access rather than trusting the stored notification snapshot. Depending on the current policy, a reference can remain accessible, direct-shared, locked/discoverable, redacted, hidden, or unavailable. Hidden and unavailable destinations expose no outward link or private route identity.

Issue activity

Issue activity notifications are Inbox-first. Issue-level subscribers can receive notifications for comments, replies, mentions, and visible property or lifecycle activity. Thread followers receive notifications for that thread only.

Reactions do not create Inbox notifications, and actors do not receive notifications about their own actions. Email is narrower than Inbox delivery: only unread mentions and replies to top-level threads you started are eligible when Issue activity email is enabled in account notifications.

Issue deadline notifications are also Inbox-first. Due-soon and overdue rows can be created for the current assignee and current Issue subscribers, then emailed only when the unread row, user preference, current Issue access, and due-date state still allow delivery.

Mobile flow

On narrow screens, Inbox opens on the queue. Selecting a notification opens its canonical destination, and the back control returns to the queue without changing your active filter or destination focus. Reloaded, copied, and browser back/forward URLs preserve normalized selection, tab, and focus state.

Related

• Issue Activity
• Dates and deadlines
• Subscriptions and notifications
• Notification settings