Use correspondence through HiveAI¶
HiveAI can ask Correspondence for memo and official-letter information and propose changes to those records. Reading information, approving a change, carrying out that change and working with a protected file are separate activities. Each has its own access and completion requirements.
Availability: This draft describes the correspondence capabilities implemented for HiveAI. It does not confirm that the complete assistant journey is available in your environment. The matching assistant Final Screens, connected frontend, approval path and access checks still require verification. The frontend is work in progress. Consequently, this page explains supported work and result meanings without inventing assistant buttons or a click sequence. The ordinary correspondence journeys are described in the linked guides below.
Information the assistant can request¶
| Information | What it provides | How to interpret it |
|---|---|---|
| Memos | A bounded selection of accessible memos or the content, status and lifecycle of one memo | An answer can contain the memo body, including an eligible draft. It is not limited to already published communications. |
| Official letters | A bounded selection, one letter's content, or status information | Status requests can return a selection of letters. Check the intended letter before relying on an answer about it. |
| Letter operations | Current letter information, counts of dispatch attempts and attachments, and whether a Records request is pending | Attempt counts do not prove delivery. One summary field currently reports the preferred delivery method instead of the actual delivery state; it must not be read as a delivery outcome. |
| Letter context | Parent/thread references and related references | A related reference is contextual information. It does not prove that you can open the referenced item or that its saved description is current. |
| Preparation guidance | Reminders about authoring permission, current recipient discovery and governed attachment handling | These reminders are not a complete list of recipients, approval processes, classifications or other configuration choices. |
The read path refreshes the required product permission and checks whether each source is eligible for the supplied user scope and classification allowance. Some authority information, such as organizational membership, still comes from the supplied authorization context. Complete revocation and cross-reference visibility need end-to-end verification. An administrator should not treat the presence of an AI read capability as proof that every confidentiality boundary has been accepted.
Browse results are limited to at most 50 requested items. Candidates are selected before the final source-access filtering, so a result can contain fewer items than requested even when other accessible items exist. This path does not return a continuation for the omitted items or reliably flag that limitation. An empty or short result therefore does not establish that the organization has no other matching correspondence. Use the normal authorized correspondence views for a fuller investigation.
Knowledge ingestion and these direct reads are different paths. Correspondence in HiveAI explains classification exclusions, withdrawal, source freshness and background catch-up. A successful read is an observation of source information; it is not an approval decision, proof of delivery or an audit of every later change.
Changes the assistant can propose¶
The broader action path implements the following groups. Ordinary correspondence rules still determine whether a transition is allowed.
| Proposed work | What success means | Canonical guide |
|---|---|---|
| Edit a memo | Save the supplied draft content, recipients and metadata | Prepare a memo |
| Approve, publish, reject, recall or archive a memo | Complete that particular source transition | Memo lifecycle |
| Start memo workflow work | Request the configured workflow start | Memo workflow and recovery |
| Create or edit an official letter | Save a letter draft with the supplied recipients, authorities, metadata and dispatch preferences | Prepare an official letter |
| Submit, approve, issue, reject, recall or archive a letter | Complete the selected source transition; these decisions have separate meanings | Letter lifecycle |
| Request dispatch or record delivery evidence | Queue a delivery attempt or record the supplied outcome evidence | Letter delivery |
| Start letter workflow work or request Records promotion | Request the separate workflow or Records handoff | Letter workflow and Records promotion |
| Complete letter response work or record a memo/letter review | Record contribution evidence for the selected work | Response work and reviews |
Basic memo creation and submission for approval use a different path. Read AI-assisted memo actions for their narrower preparation defaults and conditional draft-archive reversal. Do not assume those creation defaults or reversal options apply to the broader letter actions.
Review the proposed content¶
The source prepares an exact preview tied to the action, target and observed source version, with a five-minute expiry. A preview does not save a draft or complete an approval. It also does not validate every recipient, field combination or business transition that is checked when carrying out the change.
For an edit, review the whole resulting draft: subject or title, body, recipients, classification, accessibility, approval requirements, workflow settings and, for letters, authorities, references and dispatch choices. The edit supplies the full replacement settings; it does not promise to preserve every omitted setting. Missing optional values can become empty values or defaults. An instruction to change only the title must not silently authorize different recipients or removed approval requirements.
The broader edit/create actions cannot add new attachment files through their ordinary action payloads. Edits can specify existing attachments to remove. New files belong in the protected correspondence flow described below. The delivery-evidence action can record evidence details and a reference, but it does not carry a new evidence attachment.
Execution checks the approved payload and current source version, refreshes the action permission, resolves the acting staff context and dispatches the ordinary correspondence command. A changed source can invalidate the proposal. A preview alone does not establish that the person may perform every action on every memo or letter; artifact-specific authority and the full approval path remain acceptance requirements.
Actions that use the correspondence activity recorder have a separate identity dependency. An approved acting person alone does not supply every sign-in detail needed by that step. A preview or approval is therefore not proof the action can finish. See history and recovery for the actions covered, and keep the original operation reference when investigating an unavailable result.
Understand completion and recover safely¶
Creating a letter allocates a new letter identity. The result also retains the original proposal target for tracking. Support and integrations must distinguish those identities when locating the created letter; the proposal target is not necessarily the saved letter's identity.
An executed action proves the reported source operation, subject to verification of the complete delivery path. It does not by itself establish all downstream outcomes:
- Submission is not approval, and approval is not publication or issue.
- Queued dispatch is not delivery or acknowledgment by the recipient.
- A workflow-start result does not prove the workflow has finished.
- A Records request is not confirmation that the letter has been filed.
- Review or response evidence is not automatically a new approval decision.
The source saves action results for recovery. A repeated request for an already completed operation can return its earlier response, even if permissions or the letter have changed since then. Treat it as a historical result and check current source state separately. Saved-result completion can also contain an unavailable business outcome.
If a connection fails or an outcome is unavailable after submission, keep the original operation reference. Recover that result and inspect the current memo or letter before starting a new operation. A failure to read back the result can happen after the command was dispatched. Creating a new request identity immediately can cause additional workflow, delivery or other work. Receipt retention and recovery through every failure boundary are still unverified; this is not a promise of permanent replay history.
These broader actions do not return a general undo option. Use the normal permitted correction, recall or archive process when appropriate, with its own approval and history. Do not assume that recalling a letter retrieves an email already sent, or that archiving deletes a record.
Protected attachments and delivery evidence¶
Protected handoffs are implemented for viewing or uploading memo attachments, viewing or uploading letter attachments, and preparing letter delivery evidence. Their purpose is to continue the work in the appropriate authorized viewer, editor or evidence flow without putting file contents or sensitive credentials into an ordinary assistant proposal.
Preparation checks current permission and source access and issues a handoff with a ten-minute expiry. Preparing it does not open a document session, upload a file or record delivery evidence. Those activities require the corresponding application and document services. No assistant screen sequence for this continuation has yet been accepted.
Completion is checked again. The selected source must still be accessible and match the reported version. A viewing completion expects the same version; upload and evidence continuations expect a changed version. A changed version is part of the validation contract, but it does not independently prove which file or evidence item was created. The complete protected application path must bind that result to the requested work.
If the handoff expires, access changes or another edit makes the source stale, return to the current correspondence context and prepare a fresh authorized continuation. Keep sensitive proof material in the protected flow; do not paste it into an assistant conversation or a general support message. If the file may already have been uploaded, check the attachment list before repeating the upload.
Responsibilities and limits¶
End users review the actual proposed content and the selected memo or letter. Managers distinguish the business decision from downstream delivery, workflow and filing. Administrators verify permissions, organizational scope, protected-file handling and the approval path before enabling these interactions for sensitive work. Support reconciles the original operation, current source and any separate document or delivery evidence through an approved support channel.
This page makes no claim about price, included AI usage, response-time guarantees or production activation. HiveAI licensing, governance, provider and credit controls are separate from Correspondence's source capabilities. The remaining assistant-screen, source-authority, receipt and protected-session gaps remain open.