Description
Scheduled Archival is a strong step forward for helping admins manage content at scale. The experience is clear and approachable, with helpful previews, notifications, and a grace period that make automated cleanup safer and more transparent.
However, the current implementation is limited to a single rule based on “archive after X months since last edit.” While useful, this does not align with how enterprise governance, compliance, and fiscal-driven cleanup actually operate. Many organizations require date-based archival, fiscal year or quarter cutoffs, and the ability to exclude regulated or audit-sensitive teams.
In addition, large environments cannot rely on a single policy. Different teams, environments, and governance scenarios require multiple simultaneous rules, as well as visibility into what has been automatically archived over time.
What are you trying to achieve
Enable Scheduled Archival to support real enterprise governance by allowing admins to define multiple, flexible archival policies. This includes setting specific cutoff dates, archiving by fiscal year or quarter, excluding designated workspaces or boards, and running multiple policies in parallel for different teams or environments (such as regulated functions or Dev/UAT spaces).
Providing visibility through logs or audit history would further support compliance and accountability. Together, these capabilities would allow organizations to automate cleanup safely while respecting regulatory, operational, and business-continuity requirements.