Read messages in your work mailbox¶
HiveComms is designed to let you choose a folder in your connected work mailbox, browse messages and inspect a selected message. This guide follows the current Final Screens for the inbox, message detail and empty-folder views. The inspected frontend remains a preview: folder links, message detail, search, attachment cards and sync labels use sample content. A preview screen does not prove that the selected mailbox, folder or message was read.
Start with connecting your mailbox if access has not been established. Organization configuration, your personal connection and the email provider must all permit access.
Choose a folder and find a message¶
- Open HiveComms, then Mailbox, in the correct WorkOS organization.
- Under Folders, choose the folder you need. Folder names come from the provider; your mailbox need not have every folder shown in a design example.
- Where a folder has a parent path, check that path as well as its short name. Two folders can have similar names in different places.
- Review the message subject, sender, date, read indicator and short preview. A missing preview or date does not, by itself, mean the message is missing.
- Select the message to open its detail. Check its subject and sender again before acting on the contents.
The intended folder list distinguishes total messages from unread messages. Those counts describe returned provider information, not the number of rows currently visible or an assurance that every folder was loaded. A folder named Drafts does not establish that creating or saving drafts is supported in Zerohive.
Messages are retrieved in pages. Each page covers part of the folder and is sorted by date. Do not assume that a displayed page represents the entire mailbox or that dates across all pages form one stable global order. Incoming or removed mail can change the results between reads. Page-navigation steps are awaiting verification in the connected interface.
Read message details¶
The intended detail view presents the full subject, sender, available recipients, date, body and attachments. To, Cc and Bcc describe information returned with that message. A missing recipient group is not proof of who else received a copy: providers and stored messages may omit that information.
The preview in the list is a short extract. Open the detail to read the body; an empty preview does not establish an empty body. The service prefers the HTML body when available, otherwise plain text, with a fallback when neither exists. The finished interface still needs to render provider content safely.
Opening the inspected reading path does not explicitly mark a message as read, move it, delete it or file it into Records. An Unread indicator can therefore remain after viewing. Reading a message also does not confirm that the sender received an acknowledgement.
Dates need care when comparing a message with another system or reporting a problem. The detail path does not preserve the original time-zone offset throughout its conversion. Include the displayed time and your time zone when asking support to reconcile a discrepancy.
Understand attachments¶
The detail response includes supported attached files and attached email messages, with names and content. Attachment retrieval is part of loading the message detail. A large or problematic attachment can therefore affect the whole detail result.
The inspected Final Screen lists attachment names. The current frontend attachment cards are sample display content, without a working open or download action in the inspected component. Do not treat clicking a preview card as a successful download. Exact opening, download and accessibility steps remain pending a connected implementation.
An attachment appearing in a message does not show that it was scanned, converted, signed, uploaded into the document library or captured into Records. Follow the applicable document or records procedure when those separate outcomes are needed.
Understand connection checks and refresh¶
Mailbox access can require a provider token to be renewed. The implementation attempts renewal while obtaining credentials when a known expiry is near. It is not proof of a continuously running mailbox synchronization service, and it does not guarantee uninterrupted access.
A displayed connection-check time can be updated during token renewal before a subsequent incoming or outgoing mail connection succeeds. Treat it as recorded connection information. Use the result of the actual folder or message request to understand whether that action succeeded.
If renewal cannot complete, reconnection or administrator help may be needed. A saved Connected status can remain while a later access attempt fails. Follow connection recovery without sharing passwords, PINs, provider tokens or sign-in return links.
Recover when messages do not appear¶
An empty list does not always prove an empty mailbox. Some current provider failures can leave an empty or partial folder/message list. Opening a message can also fail instead of displaying its contents. Clearer distinctions between an empty mailbox, incomplete results and failed reads are still being implemented.
| What you see | What to do |
|---|---|
| No folders, or fewer folders than expected | Check the organization and connected work email. Retry the read once if a temporary interruption is plausible, then ask support to check provider access if the result remains incomplete. Do not infer deletion. |
| A folder appears empty | Confirm the selected folder and its parent path. If you expected mail, investigate access or loading before treating the folder as empty. |
| The expected message is not on the current page | Check the folder, available pages and whether new or removed mail changed the listing. A single page does not establish absence from the mailbox. |
| A row appears but its detail fails | Return to the folder and refresh its contents. If the message is still listed, ask support to investigate that folder and message. Avoid substituting another message with a similar subject. |
| The message body or preview is missing | A preview can be unavailable independently of the body. If detail is incomplete, use the normal provider mailbox where your organization permits it and report the problem. |
| A message remains unread after opening | The current reading path does not explicitly change the provider's read flag. Do not treat that indicator as proof that nobody viewed the message. |
| Connected status is shown, but reading fails | Check the actual failure and follow connection recovery. The saved status and recorded check time do not prove live access. |
| An attachment is listed but cannot be opened in the preview | The preview has no working attachment action in the inspected component. Use an approved working mailbox client if needed; do not assume the file has been downloaded or captured elsewhere. |
| Search or Capture appears in the preview | These controls do not establish working search or Records capture. Use the relevant completed procedure when available. |
For persistent failures, give support the organization, work email, folder path, approximate time and visible error through the approved support channel. Provide only the message details necessary to identify the problem; avoid forwarding unrelated message contents or attachments.
What this reading guide does not establish¶
Folder browsing is separate from sending, delivery confirmation, reply threading, forwarding, draft editing, filing, deletion, Records capture and scheduled synchronization. Their availability must be verified separately. The current preview's extra controls and metrics do not establish those capabilities.
For outgoing activity and delivery interpretation, continue to mailbox email history. The personal sending guide now explains the inspected compose journey, status meanings and recovery. Work-linked email and connected-interface acceptance remain separate continuations.