- An active workspace membership and access to notification settings
- A list of assignments, work, customer, operations, or governance events you own
- Browser notification permission when desktop alerts are required
Notifications are personal
Open Settings → Notifications. These controls belong to the signed-in user, not the workspace administrator. Unread state remains in each inbox; a notification preference determines whether eligible activity enters notification history and may create a toast, desktop alert, or sound.
A notification is a route to work, not the work itself
- 01EventSource event
A message, assignment, due action, customer change, or governance event occurs.
- 02GateEligibility and preferences
Role access, inbox source, and personal notification settings decide whether it becomes a signal.
- 03SignalPersonal attention feed
Unread, read, and cleared describe the Member's notification history—not the work state.
- 04DecideOpen the source record
Confirm current owner, status, priority, evidence, and next action where the work actually lives.
- 05OutcomeAct, then acknowledge
Complete, reassign, or schedule the work before marking or clearing the notification.
Configure the feed
- Under Notification feed, leave the feed enabled if you want new persisted notification history.
- Enable only the categories you need: assignments, work, customer, operations, and governance.
- Under Inbox alert sources, choose Shared inbox messages for customer messages assigned to you and Personal email for private threads you own.
- Under Desktop & sound, enable Desktop alerts and accept the browser permission prompt.
- Enable Attention sound, choose Balanced, Loud, or Maximum, and select Test sound.
- Trigger a safe assignment or test activity and confirm it appears through the intended surfaces.
Turning the feed off does not clear existing notification history.
| Layer | What it does | Common reason it appears silent |
|---|---|---|
| Notification feed | Persists enabled event categories in WRKZY | Feed or category is disabled |
| Inbox source | Allows eligible shared-inbox or personal-email activity into notification handling | Wrong source is disabled or the item is not assigned/owned |
| Desktop alert | Shows background alerts on supported signed-in devices | Browser permission is denied or unsupported |
| Attention sound | Plays for enabled realtime alerts, including visible inbox alerts | Sound disabled, session playback blocked, or operating-system volume low |
Choose signal over volume
Keep assignment and customer-work signals on when you own a queue. Enable operations or governance only if you are expected to act on them. Desktop alerts are most useful when WRKZY runs in the background; they are not a substitute for queue review, SLA views, or follow-up ownership.
Verify browser behavior
Browser permission is device- and browser-specific. If the page says alerts are blocked, re-enable notifications in browser settings and return to WRKZY. A browser can block audio until you interact with the page; use Test sound after clicking in the app. Your operating-system focus mode and volume still apply.
Recovery
If one expected alert is missing, first confirm the underlying item exists and is assigned to you. Then check feed, category, source, desktop permission, and sound separately. Do not repeatedly reassign customer work just to test notifications. Use a safe internal record and capture event type, approximate time, browser, device, and which layer succeeded.
- Required feed categories enabled
- Correct inbox sources enabled
- Browser permission granted on this device
- Test sound works at a safe volume
- Real test event appears without duplicate noise