At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Retention class | Validate and persist the policy label | Policy identity on frozen evidence | The app does not select a lawful duration |
| Retain until date | Compare the recorded date with evaluation time | Retain or expired disposition | A date alone does not authorize deletion |
| Legal hold | Override elapsed retention for deletion checks | Legal-hold disposition | The organization owns hold authority and release |
| Missing policy | Block evidence capture | Configuration-required state | Capture cannot proceed without a valid date |
How it works
- Open Create enterprise freeze.
- Select the required Governed spaces.
- Enter the approved Retention class.
- Set Retain until from the governing policy.
- Select Legal hold when authorized.
- Select Prepare and queue freeze.
Example
A regulated evidence package must remain available until a policy date. The administrator records that date and the approved retention class before capture. A later legal hold prevents deletion after the date passes. Compliance Glossary records and applies that state. Legal and records owners still decide when the hold may be released.
What this does not mean
Compliance Glossary does not provide legal advice or choose jurisdiction-specific retention periods. It does not create a legal hold merely because an administrator selects the control. The organization must define authority, approval, review, and release outside the app.
Related questions
Next step
Define the retention policy and hold authority before creating the baseline.
View on Atlassian Marketplace