Overview

Set retention windows and legal exceptions for documents, logs, and generated outputs.

Audience

• Admin
• Compliance

Product Area

Data Lifecycle

Prerequisites

• Compliance policy approved

Steps

1. Define retention classes

Set class-specific windows for evidence, audit, and operational records.

1. Configure exceptions

Apply legal-hold and regulatory overrides by data class.

Expected Result

The Data Lifecycle workflow completes without unresolved validation errors, and the result is visible to the intended roles.

Security and Audit Notes

• Use the least-privileged role that can complete the task.
• Confirm the resulting change or decision appears in the workspace audit trail when the workflow changes customer data or access.

Limits and Preconditions

• Available controls depend on the tenant plan, enabled modules, jurisdiction, and administrator policy.
• If a named control is not visible, confirm entitlement and role access before treating the behavior as a product failure.

Troubleshooting

• Policy conflicts: Resolve overlapping rules by explicit priority ordering.

Related Articles

• Run Legal Hold Process

Escalation

If the documented result cannot be reached after the checks above, capture the workspace identifier, affected product area, timestamp, and a redacted error message, then use Support. Never include secrets, privileged legal content, or customer documents in the initial report.