What's new: Content Retention Policy for Work-in-Progress (WIP) Content
TL;DR:
Admins can now create content retention policies to manage the lifecycle of Creative Cloud Projects stored in Adobe cloud for business. Define how long completed projects are retained before they're permanently deleted.
This capability is available through the Adobe Admin APIs for Storage Management.
What are the requirements?
- Your organization uses Adobe cloud storage for business with Creative Cloud Projects
- You have admin access to the Admin Console
- An authorized external system, such as a project management or workflow tool, is configured to signal project completion via the Adobe Admin API
Why should admins set up WIP content retention?
Admins can create one or more content retention policies to define how long Creative Cloud Projects are retained after being marked as complete, before they are permanently deleted. With WIP content retention, admins can:
- Create one or more retention policies for WIP content within an organization
- Modify policies at any time: extend or shorten retention periods, with changes applying to all active projects from each project's original retention start date
- Delete a policy to immediately stop enforcement without deleting any projects
- Manage precedence when multiple policies apply to the same project (earliest retention date wins)
How does the retention lifecycle work?
A Creative Cloud Project is considered marked as complete when it has reached the end of its working lifecycle and is no longer active work. This status is set through an integration with an authorized external system, which invokes the Adobe Admin API to start retention.
| Stage | What happens |
|---|---|
| Project marked complete | Retention period begins |
| Retention period ends | Project is soft-deleted and moves to Deleted view |
| 30 days after soft delete | Project is permanently and irrecoverably deleted |
Restoring a project:
End-users can restore a soft-deleted project within the 30-day window. On restore, the project becomes active again. The original retention period does not automatically restart. Retention only re-applies if an admin explicitly re-associates a policy. If the project is subsequently marked as complete again by an authorized external system, a new retention period begins anchored to the new completion date.
How do I get started?
Review the API documentation and configure your policies through the Admin Console. View the Storage Management API documentation
Already set up a retention policy? Running into issues or have feedback? Drop it in the thread, the team is reading.
Quick Links
Was this helpful? Click the Like icon below, it helps us know what's working.
More questions? Start a conversation | Catch up on all updates: ICYMI
AdChoices