Messaging data, exports and organization removal¶
Your conversations are connected to other parts of Zerohive: people, work, meetings, documents and contribution evidence. An organization export or deletion therefore has several parts. The Messaging service contributes its own records; the final organization-wide result belongs to the wider operation.
Availability: This guide explains the inspected background behavior. It does not establish a connected export or deletion screen, a completed operation in your workspace, or a restore facility. The responsible administrator should confirm the supported organization-wide process and its final result.
What Messaging records contain¶
| Information | What it includes |
|---|---|
| Conversations and people | Conversation details, participants and the local people information used by Messaging. |
| Messages and receipts | Stored message content, message details and recorded delivery/read status. A receipt is not proof that a person understood a message. |
| Shared-file records | File names, storage references, version information and any saved temporary link. These records describe files; they are not the stored file bytes. |
| Personal attention | Inbox entries and personal meeting summaries. The underlying work and meeting have their own records and owners. |
| Work connections and access information | Links between channels and work, plus the local information Messaging uses to determine available capabilities. |
| Verified work evidence | Work-response verification, retained contribution revisions and the inventories used to reconcile their delivery. |
The export can contain sensitive conversation content, people information, evidence and file links. Give access only to the intended recipients through your organization's approved process. An export is not a sanitized public report.
Understand what an export provides¶
Messaging collects the declared records for the selected organization and returns them as its portion of the export. The reported record count is a count of stored rows. It is not a count of people, unique tasks, messages alone, file bytes or successful deliveries.
This portion does not download attachments from their storage provider. A saved temporary file link can expire and does not turn the package into a durable file backup. If you need the actual files, ask the responsible administrator to confirm their separate inclusion and accessibility.
The service result also does not establish that other services have finished, that the final package has been delivered, or that the package can restore a working organization. Active conversations and related work can change while collection is underway. Confirm the collection period and consistency requirements before using an export as a complete historical snapshot.
Distinguish everyday actions from organization deletion¶
Marking an inbox item read or resolved changes its attention state. Leaving a conversation changes membership. Neither action is the organization-wide deletion process described here.
Messaging's organization deletion is configured to remove the business records listed above, including contribution revisions and reconciliation inventories. Its declared rules do not keep a retained subset or anonymize those rows instead. A completed service result reports the outcome for that service's scope.
That result does not establish removal of attachment objects, source work, authoritative meeting records, analytics copies, backups, logs or other stores. Each requires its own owner and confirmed result. A count of zero retained Messaging rows is not a statement that no related information exists anywhere.
Contribution history after removal¶
Evidence recovery depends on retained original contribution records. When those records are removed, this source cannot replay them from the deleted journal. An export may preserve evidence for its permitted purpose, but the inspected export path does not provide an import or restore procedure.
Before an authorized organization closure, the responsible owners should resolve the required evidence, export and retention scope. Do not assume that a downstream report disappearing, remaining visible or changing proves what has happened to the original records.
Recover when the result is unclear¶
| What you observe | What to confirm |
|---|---|
| Messaging has finished but the organization job is still running | Ask which other service or packaging step remains. A single service result is not the final result. |
| The export has file details but a file cannot be opened | Confirm that actual file content was included separately and that access is still valid. A stored link may have expired. |
| Deletion fails or remains pending | Preserve the operation reference and let support verify the failure and transaction outcome before retrying. Do not manually remove related records to force success. |
| A repeated deletion reports zero removed records | Ask support to reconcile it with the original attempt. Zero now does not explain what the earlier attempt did. |
| Information remains in another view | Identify the source of that view and ask its owner to confirm its own retention and deletion result. |
| Contribution evidence can no longer be recovered | Confirm whether the original evidence was removed and whether an authorized export exists. Recreating a message is not a substitute for the original verification. |
Give support the organization and operation references, approximate time, expected scope and observed result through an authorized private channel. Avoid posting message bodies, file links or exported records in a public support discussion.
For managers and administrators¶
Agree who can receive the export, which files and service records it must contain, who confirms completion, and what recovery is actually supported. Treat database rows, stored files, downstream views and retained operational copies as separately verifiable parts of the organization operation. Use the final confirmed results when making a closure or transfer decision.