PERSONAL ATTENTION
Review what needs your attention without treating every message the same.
Use personal unread and notification state across supported conversations, with room-level choices and current record visibility.
Your attention state belongs to you
Unread context and room preferences help organise the next review.
More alerts do not automatically mean better follow-up
A direct question, a followed record update and a general room message deserve different attention. Tsumira keeps notification and participation state for the person using the workspace, rather than assuming every message should interrupt every colleague. The inbox and conversation views help the person return to relevant work. They support review and follow-up, but do not guarantee that every message will be noticed on every device.
Read your own attention context
Notification receipts and conversation read state are associated with the current person. The host inbox can aggregate their supported module notifications without making one module’s private data public to another user. Open the originating conversation or record to understand the event before deciding what to do. A count tells you there is something to inspect; it is not a complete description of the customer request or business action behind it.
- Personal receipts and read state
- Supported cross-module inbox context
- Links to the originating work
Choose how a room should reach you
Supported room preferences distinguish notification levels and temporary muting. Following a record conversation and being a member of a direct or group room have related but different participation meanings. The current preference flow manages the person’s own choices, not somebody else’s inbox. Use a quieter level for background discussion and an appropriate level where active responsibility requires attention, then review the conversation itself when returning to the work.
- Room-level attention preferences
- Temporary mute choices
- Individual settings rather than team-wide overrides
A notification is not permanent permission
Open the underlying subject with the reader’s current authority.
Choose the supported level
Keep notification access current
A notification link is not a permanent grant to the record it refers to. The current subject’s visibility is checked when information is exposed or opened. A private file, personal mailbox or internal meeting keeps the relevant authority boundary even if a past event once generated attention. Delivery channels and device permissions also affect visible alerts. Use the actual inbox and thread state to review work rather than assuming a push notification is an infallible reminder system.
- Current subject visibility
- No extra rights from an old link
- Device and channel behavior remain relevant
A concrete workflow
Review personal attention
Open the relevant unread or notification view for the current person.
Inspect the source
Read the record or conversation behind the item before interpreting its urgency.
Set room preferences
Choose the supported attention level or temporary mute appropriate to your role in the discussion.
Follow through in context
Respond or take the next reviewed business step, then use the current read state to continue the review.
An illustrative working example
Illustrative workflow: return after a day away
A colleague returns to a busy workspace and opens their personal attention view. They inspect a direct question and a record update they follow instead of reading an arbitrary company-wide stream. A background room is muted temporarily, while a customer case still needs review. Opening that case checks current access; a past notification does not override a permission change.
Questions about this topic
Can I change another colleague’s notification preferences here?
The room preference flow described here writes the current person’s own choices. It is not a general override of everyone’s attention settings.
Does a notification link grant record access?
No. Current record or conversation authority still applies when the link is opened or information is shown.
Will every message always create a visible push?
No. Preferences, supported channels, device settings and permissions affect visible delivery. Review the actual inbox and conversation state.
Is unread state a customer-delivery receipt?
No. Personal team attention and an external message’s transport or provider status are different facts and should be read separately.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Slack
Workflow concept: Plan personal alert preferences without creating duplicate attention everywhere.
Microsoft Teams
Workflow concept: Review which meeting or work updates need a personal notification.
Outlook
Workflow concept: Compare notification messages with the underlying record’s current availability.