Skip to main content

Inbox

Inbox is the user-specific feed for watched ticket changes, watched document changes, and AI review items. It keeps updates visible without turning every workspace change into noise.

Open Inbox whenever Today shows unread updates, after you submit important project Check-Ins, or when an AI proposal needs review.

What appears in Inbox​

Each row shows the item type, status, title, summary, and available actions.

You may see:

  • Watched ticket comments, assignments, status changes, priority changes, due date changes, moves, archives, or title/description edits.
  • Watched document publishes, revisions, moves, archives, or deletes.
  • Memory diffs.
  • Operating proposals.
  • Ticket or roadmap proposals.
  • Duplicate or conflict resolution proposals.
  • Suggestions created from project Check-Ins, docs, chat turns, or background scans.

Rows can include a short ID so support or teammates can identify the item.

Accept or reject​

AI review items have Accept and Reject actions. Ticket and document updates can be marked read or archived.

Accept when:

  • The proposed change is accurate.
  • The source context supports it.
  • The scope is correct.
  • The change is specific enough to be useful later.
  • The proposal should affect future planning, memory, or execution.

Reject when:

  • It is stale.
  • It is speculative.
  • It duplicates existing state.
  • It applies to the wrong project.
  • It overstates a strategy, decision, or customer fact.
  • It updates the wrong ticket or roadmap item.
caution

AI review: Inbox is the control point. Do not accept review items in bulk without reading them. Accepted items can change memory, tickets, roadmap structure, or other operating state.

Memory diffs​

A memory diff proposes changes to durable memory. It may add, update, supersede, or archive facts.

Before accepting a memory diff, ask:

  • Is the fact true today?
  • Is it useful enough to be durable memory?
  • Is it written clearly?
  • Does it belong to the current project or the whole organisation?
  • Is the source recent and trustworthy?

Reject memory diffs that turn guesses into facts.

Operating proposals​

Operating proposals are review items that may affect work. Examples include:

  • Creating or changing a ticket.
  • Updating roadmap structure.
  • Resolving duplicate ticket candidates.
  • Capturing a proposed follow-up from a check-in.

Some proposals are generated because TOW avoided making an automatic change. For example, if a check-in could match more than one active ticket, TOW can ask for review instead of guessing.

caution

Review-sensitive action: Accepting a proposal can change execution state. Check the target item, project scope, and rationale before accepting.

Project scope​

Inbox respects the active project picker.

Use All Projects to see organisation-wide review pressure. Use a specific project to process only that project's review queue.

Watching and notification settings​

Use the Bell on a ticket or document to follow it and choose an Inbox, Email, or Push channel for each event. TOW automatically follows individual items you create, edit, are assigned, or comment on unless you explicitly unfollowed that item.

The Notifications tab in user settings also provides:

  • Default event and channel rules for tickets and documents you follow.
  • A separate channel rule for direct @user mentions.
  • Project follows for ticket creation, ticket activity, ticket comments, document activity, and ticket SLA warnings or breaches.
  • Knowledge scope follows for document creation, changes, and comments.
  • An Only notify me for direct @mentions mode.
  • Browser registration and removal for Web Push.

The most specific rule wins: an individual ticket or document rule overrides a knowledge scope, which overrides a project follow. This means muting a project does not prevent TOW from automatically following a ticket you later edit or comment on. Explicitly unfollowing that ticket still blocks automatic follow. Direct user mentions use the global mention channels and bypass watch or mute state. Group mentions and replies are not treated as direct mentions.

Inbox and unread badge behavior are one channel. Turning Inbox off for an event also keeps that event out of the unread badge count. Disabling Email or Push cancels delivery that is still queued; it cannot recall a message already sent.

The channel fallback table keeps older global, category, and project channel choices visible and editable. Event-specific ticket, document, project, and knowledge rules take priority over those fallbacks. Resetting a fallback removes the stored override and resumes inheritance.

Browser device registrations and push transport outbox rows are deliberately excluded from organisation exports. They contain session-bound delivery secrets and transient provider state, so users register browsers again after an import.

note

Project scope: If the inbox count on Today does not match the list you see, compare the project scope in Today and Inbox. The count and list are scoped.

What happens after review​

After you accept or reject an item, TOW refreshes affected areas such as:

  • Inbox.
  • Today.
  • Tickets.
  • Memory Diffs.
  • Memory.

AI item status changes from pending to accepted or rejected. Notification rows stay available until you mark them read or archive them.

Role availability​

User typeAvailability
Organisation memberCan review Inbox items visible to them in accessible scopes.
Project member, lead, or adminCan process project-scoped items where project access allows.
Organisation admin, owner, or server adminBroad review access across the organisation.

Some accepted actions may still require project write access or administrative permission, depending on the target.

Hidden gotchas​

  • Inbox is not a task list. It is an update and review surface for things you already have access to.
  • Rejecting an item is normal and often correct.
  • A rejected duplicate proposal may suppress that duplicate candidate so it does not keep reappearing.
  • Review items can appear after background Agent Runs finish, not only immediately after a user action.
  • If an item seems missing, check project scope and wait for AI status to return to idle.
  • In direct mentions only mode, ordinary watch and scope notifications are paused. Required AI review items remain in Inbox so they can still be accepted or rejected; critical account and delivery incidents also remain enabled.