Understand retention, archiving, and deletion
Distinguish hiding, archiving, and deletion without assuming an unpublished retention period or global deletion behavior.
In this article
- Hide
- Remove an item from a view without proof that its underlying record was deleted.
- Archive
- Remove a conversation from the active path while retaining it under applicable features and policies.
- Delete
- Request removal of a record when the control is actually connected and authorized; shared or linked data can follow different rules.
- Retention
- Duration and rules applied to data; no universal period should be inferred from the current interface.
- Use conversation actions only after verifying their visible result.
- Conversation archive and restore controls are connected in Data controls. Global deletion, export and shared-link management remain preview controls.
- Do not promise that deletion removes every copy, notification, attachment, shared record, or regulatory trace.
- Ask your organization for its approved policy when a retention or deletion obligation applies.
Practical guidance
Studio’s Data controls includes connected conversation archive management. Review the current profile scope before using bulk archive, and use the archived-conversation list to restore an item. Other visible controls, including global deletion, data export and shared-link management, do not currently provide the same connected workflow.
Advanced tips
Use archiving for organization, not as evidence of erasure. After a bulk action, verify its reported count and the relevant list. For a retention obligation, follow the organization’s policy rather than inferring a deletion deadline or universal removal guarantee from the UI.
Was this article helpful?