Retention policy limits and data export behavior with eDiscovery holds

Answer the Questions First

1. Is content subject to an active retention policy excluded from admin data exports once deletion is scheduled?

Yes, in most Slack plans that support Compliance Export (Enterprise Grid and certain Enterprise Plus configurations), the export API will only return items that are still present in the data store at the time of export. If a retention policy has already marked a message or file for deletion and the deletion has been executed, that item will no longer be part of the export payload.

2. Does an eDiscovery hold prevent retention‑based deletion for messages and files?

When an eDiscovery hold is active on a channel, user, or entire workspace, Slack suspends the deletion of any content that falls under the hold’s scope. The hold overrides the scheduled retention deletion for the duration of the hold. Consequently, those items will remain available for export until the hold is lifted.

3. Are retention limits applied uniformly to channel messages and direct messages for export and hold purposes?

Retention rules in Slack can be scoped to channels, private groups, or the entire workspace. However, the export feature itself does not differentiate between channel and DM content; it exports all retained items that meet the query criteria. The only difference arises if a retention policy is applied only to channels or only to DMs—then only those scoped items will be subject to deletion or protection by holds.

Likely Explanation

• Retention policies schedule deletion but do not physically remove data until the policy’s expiration date is reached.
• eDiscovery holds lock any content that falls within their scope, preventing the retention engine from deleting it.
• Export operations query the data store for items that are still present; thus, deleted items never appear.
• The same export mechanism handles channel and DM data; the difference lies only in the policy scope, not in the export logic.

Confirmed Facts (Slack Documentation & Common Practice)

• Slack’s Compliance Export feature is available only on Enterprise Grid and certain Enterprise Plus plans.
• Retention policies can be configured to delete messages or files after a set period, but the deletion occurs only when the policy’s expiration threshold is met.
• When an eDiscovery hold is in place, Slack’s data‑retention engine respects the hold and preserves the content regardless of any active retention schedule.
• Export limits are governed by the size of the data set and the plan’s export quotas (e.g., 10 GB per export per channel).

Practical Steps for Your Workspace

1. Verify the Retention Policy: In the Admin console, go to Settings & administration > Workspace settings > Data Retention. Note the retention period and the scope (channels, DMs, or all).
2. Check eDiscovery Holds: Navigate to Compliance > eDiscovery and review any active holds. Confirm whether the hold covers the channels or users you’re interested in.
3. Run a Test Export: Use the Compliance Export API or the UI export button for a small channel. Verify that:
   • Items scheduled for deletion but still within the hold appear in the export.
   • Items already deleted (no hold) are absent.
4. Monitor Export Logs: After export, review the export report for any warnings about size limits or truncated data.
5. Adjust Policies if Needed: If you need to preserve data longer, extend the retention period or modify the hold scope.

Diagnostic Detail Needed

To refine these recommendations, could you confirm which Slack plan you’re operating under (Enterprise Grid, Enterprise Plus, etc.) and whether the eDiscovery hold is applied to the entire workspace or specific channels?