Understand comments and work updates¶
A work update draws your attention to something that happened or needs action. It can appear in your personal inbox or alongside a work conversation. Read the original request, task or approval before deciding what to do: seeing, reading or resolving an update does not complete that work.
Availability: This guide explains the inspected implementation and intended Inbox and Workstream screens. The frontend still uses sample content. Connected notification delivery, comment audiences and recovery are not accepted for a live workspace. The guide does not establish that every event appears everywhere or that every recipient receives it immediately.
For meeting invitations, participant/session changes and artifact alerts, read Understand meeting updates.
For work-response evidence and recognition announcements, read verified responses and recognition. Sending a message or resolving an inbox item does not verify a contribution.
Choose the right record to read¶
| What you are looking at | How to interpret it |
|---|---|
| A workflow comment in a discussion | A comment associated with the workflow or one of its tasks. It provides context; it is not an approval decision or a task completion. |
| An item in Work | Attention connected to an assignment or related action. A later occurrence can update an existing item. |
| An item in Mentions | Attention classified as a mention. This label does not establish that typing someone's name sends them a notification. |
| An item in Alerts | An informational update. Several entries can concern the same underlying work. |
| An unread badge or refreshed list | A cue to review current information. It is not a delivery receipt, a complete activity history or proof that the original work changed successfully. |
The inspected inbox design provides Work, Mentions and Alerts lanes, source references and Active/Resolved states. Follow the inbox guide to review those lanes. Use workstreams for the official updates and discussions attached to eligible work. Exact comment-entry controls and notification preferences are not established by these inspected screens.
Follow an update back to work¶
- Check that you are in the right workspace and read the item's work reference.
- Read the update's context and time. A later notification can concern an older request.
- When a linked work action is available, open the original work and verify its current status, assignment and relevant discussion.
- Perform a required decision or action in that work's own controls. An inbox state change cannot substitute for it.
- Return to the inbox to manage your own attention, using the state controls available in the connected experience.
A workstream may remain readable when starting another discussion is unavailable. The linked record still applies its own access rules. If it cannot be opened, ask for an authorized access check; receiving an update does not grant permission to the underlying work.
For warnings, overdue work and escalation, use deadline monitoring. A notification time is not a new deadline or a guarantee that another person was notified.
Understand who may receive an update¶
Different updates have different audiences. Workflow comments can be copied into conversations for the workflow's involved people, including the author. A deadline warning follows its selected recipient; it does not automatically notify every follower. Some other notification types can include the workflow owner, current assignee, approvers, copied people and followers.
These are separate delivery paths. A comment in a discussion does not guarantee a matching personal inbox entry or channel update. A notification's workstream label does not guarantee that a message was posted in that workstream. The current audience checks and conversation copies still need reconciliation before confidential collaboration can be treated as verified.
Review the actual conversation audience and the underlying work's sharing rules before relying on a discussion for sensitive information. Do not infer an audience from a label such as Official, Discussion or approval-only, or assume that every person receives an identical conversation history. Administrators and support should verify the specific source and conversation when investigating a discrepancy.
When an item returns or appears more than once¶
A later occurrence of the same work action can update an existing Work item, replace its title and text, and make it Active again. Its recorded read state is preserved. An active item can therefore remain read after new information arrives. Check the item's content and the source work instead of depending only on an unread badge.
Mentions and Alerts are created as separate entries by the inspected path. Multiple entries do not necessarily mean multiple distinct business actions. Conversely, a single Work entry can represent more than one occurrence.
The current implementation does not establish that older delayed events are always prevented from replacing newer Work-item text or time. When updates conflict, use the underlying work's current state and history. Do not repeat an approval, submission or other consequential action merely to make a notification look current.
Recover when updates are missing or confusing¶
| Situation | Next step |
|---|---|
| The inbox changed but no conversation message appeared | Check the source work and the relevant conversation separately. An inbox update and a conversation post have different delivery paths. |
| A completed or resolved item becomes active again | Compare the new text with the source work. Reactivation concerns your attention item and does not itself reopen the business task. |
| Another person sees a different discussion or history | Check the actual participants and work access. Per-person conversation copies have unresolved synchronization limits. |
| An alert is repeated or its time looks older | Review the source history before treating it as another action. Give support the reference and approximate times. |
| A badge changed but the list still looks stale | Refresh the view and reopen the relevant work. A refresh signal is not an acknowledgment that the browser loaded or displayed the latest state. |
| A time-critical warning is missing | Check the task's actual deadline and assignment directly, then follow your organization's escalation procedure. Do not wait for a notification to establish whether action is due. |
For support, share the workspace, work reference, affected lane or conversation, approximate occurrence time and the result you expected. Use approved support channels and disclose private message contents only when necessary and authorized.
For managers and business reviewers, assess these updates as attention aids. Confirm decisions and completion in the owning work record. This draft does not claim complete delivery coverage, guaranteed alert timing or measured operational improvement.