W Workhouse
← Help docs

Managing your notifications

Notifications in the portal have three layers: the Inbox shows everything, email toggles control what also reaches your email, and per-task settings tune individual tasks. Set each one once and the right things find you without the noise.

Layer 1: the Inbox

The Inbox button in your header (with an unread badge) collects every event on your work: new comments, approval requests, approval decisions, status reports, action items assigned to you.

Three filters keep it manageable:

  • Unread — what's new since you last looked
  • Read — things you've seen but kept around
  • Archived — things you're done with

Click any notification to jump straight to the task or thread it's about. Archive freely — archiving only files the notification, it doesn't affect the underlying task.

The Inbox always shows every event. Nothing below changes that; the next two layers only control delivery.

Layer 2: email delivery

In Settings → Notifications you'll find a toggle per event type:

  • New comments — someone replied on a task you're on
  • Approval requests — you have a new deliverable to review
  • Approval decisions — the agency responded after your approval decision
  • Status reports — a new status report is available

Turn an event's email off and it still lands in your Inbox — you just won't get the email. A common setup: email on for approval requests (time-sensitive), email off for comments (you'll catch them in the Inbox on your own schedule).

Layer 3: per-task watch and mute

At the top of every task there's a notification button showing the task's current mode:

  • Watch this task — get notified about everything that happens on it. Use for the launch-critical task you're tracking closely.
  • Use default — the standard behavior: you're notified when you're assigned, reviewing, or have commented on the task.
  • Mute this task — silence it entirely, with one exception below. Use for the long-running task that updates constantly without needing you.

The @-mention exception

One rule overrides everything: @-mentions always get through — even on muted tasks. If someone needs you by name, you'll know. That's what makes muting safe.

A sensible starting point

  1. Leave tasks on Use default — it covers the cases where you're actually involved
  2. Keep email on for approval requests and anything else you'd want to know about same-day
  3. Mute noisy tasks instead of ignoring your Inbox — muting is reversible and surgical