The pattern: enable the feature, set the retention period to match the org's use cases, ensure compliance-needed sends route through Compliance BCC, monitor storage reclamation, train users on link expiration. The cost is minimal; the storage benefit and compliance alignment are real.
- Confirm the org uses link-based attachments
Check outbound email infrastructure: are large attachments converted to links automatically? If yes, this setting matters; if all attachments are inline, the setting has no effect.
- Enable Delete Attachments Sent as Links
Setup, Email Settings (location varies). Toggle on. The default 30-day retention applies unless overridden.
- Set the retention period to match use cases
Default 30 days works for most. Sales-critical: 90 days. Service: 14 days. Compliance-required: per regulatory schedule (typically routed through Compliance BCC instead).
- Verify Compliance BCC handles long-retention requirements
For emails requiring multi-year retention, the link-based attachment is the wrong tool. Compliance BCC archives the email plus attachments to the long-term archival vendor.
- Monitor storage reclamation after enabling
First-time enable on a mature org reclaims significant storage. Confirm reclamation in the Company Information storage usage view.
- Train users on link expiration
Sales reps especially should know that link-based attachments expire. Educate them to use inline attachment or extend retention for critical sends.
- Document the retention policy and audit quarterly
Compliance teams want the retention policy documented. The quarterly review confirms the setting still matches current practice.
Whether auto-delete is active. Default depends on org age and edition.
Days to retain the file before auto-delete. Default 30; configurable per org.
For long-retention needs, route through Compliance BCC instead of relying on link-based attachment.
Sales reps and senders who attach files need to understand link expiration behavior.
Quarterly review of retention policy against current practice and compliance.
- Retention period applies org-wide. Per-send retention overrides are not supported without custom code.
- Recipients clicking after expiration see a 404 with no sender notification. Sales follow-up workflows feel this most.
- Auto-delete conflicts with long compliance retention. Compliance BCC is the right tool for archival; auto-delete bounds storage cost.
- Disabling auto-delete does not retroactively restore previously-deleted files. The decision is forward-looking only.
- First-time enable on a mature org produces significant storage reclamation. Monitor to confirm and to understand the new steady-state.