Understand linked updates in a channel¶
A channel can show an update from related business work alongside the messages people write. This helps a team notice progress without treating the conversation as the authoritative work record. Open the related work when you need to check its current state, approve something or complete a task.
Availability: The final Channel design includes a Linked update and Open linked work item. The current app preview still uses sample content. Setting up the relationship, delivery to every intended reader and live refresh have not been accepted. This page explains the implemented relationship and its limits; a complete setup journey still needs verified screens and connected behavior.
Read a linked update¶
- Open the intended workspace, then HiveComms, Collaboration and Channels.
- Choose the channel and review the update's title, message and time.
- Use Open linked work item when shown in the intended experience.
- Confirm that the opened item has the expected reference and workspace. Use that item for the next business action.
An update describes an event that occurred. It is not a guarantee that the work is still in that state. A claimed or completed step can be followed by other work, and an older update can remain visible in the channel.
The inspected background path produces updates for workflow starts, task claims and task completions. A relationship to a source item does not mean that every edit, comment, approval decision or change in every product is automatically copied to the channel.
Understand the relationship between work and a channel¶
The platform stores a relationship between one business work item and one channel in the workspace. Changing that relationship selects a new target channel and makes the relationship active. Different work items can use the same channel.
Changing the target channel does not move or erase messages already stored in the previous channel, copy all earlier history into the new channel or confirm that a new update has arrived. A complete unlink journey has not been verified either. Ask the responsible workspace team to manage the relationship through the approved process while that experience is unfinished.
The source work and channel keep their own access rules. Seeing an update does not grant permission to open its linked record, and permission on a record does not automatically make someone a channel participant. Before arranging delivery into a channel, the responsible team must confirm that the channel's audience is appropriate for that work.
Know what delivery does and does not establish¶
Saving the relationship and delivering an update are separate events. An active relationship is not proof that the latest source event has been received, stored, shown to every member or read.
Automatic delivery still has unresolved issues, particularly when an update should appear for several recipients and a linked channel. Reliable delivery and live refresh must be verified before using channel updates as a required operational handoff. For urgent work, check the owning record and use your organization's approved communication process.
The message guide explains ordinary message receipts. Do not interpret a system update, its displayed time or a conversation badge as proof that every intended recipient received or acknowledged it. Managers and executives should use source records for completion, approval and workload reporting.
Recover when updates are missing or misleading¶
| What happens | What to do |
|---|---|
| An expected update is missing | Check the owning work item first. Ask support to confirm the source event, active relationship and intended channel. |
| A relationship was changed but old messages remain | Existing channel history is retained. Changing the target channel does not remove earlier information. |
| A new channel does not contain earlier history | There is no automatic history-copy guarantee. Open the original work item for its authoritative history. |
| The linked item refuses access | Confirm your workspace and permissions with the work owner. Channel membership does not override source access. |
| An update appears old or repeated | Compare the source item and event time. Ask support to investigate before repeating the underlying business action. |
| The update points to an unexpected item | Stop before acting and report the visible reference and destination mismatch. |
| Setup or changing the target channel times out | Have the responsible team establish which channel is currently selected before submitting another change. A repeated request can change the relationship again. |
When requesting help, include the workspace, channel name, work reference, expected event and approximate time. Keep private message content and file links within your approved support channel.
See workstreams for conversations within a workflow, channel membership for ordinary conversation access, and search for finding existing summaries.