Requesting a centralized Large Folder Operations Dashboard in the Box Admin Console or via API to improve visibility and control over major content transfers.

During a large folder ownership change, an unexpected behavior occurred where ownership polling and job sequencing did not reflect the actual state of completion. This led to a move propagating recursively from an empty child folder to an inherited, multi-million-object parent folder.

A built-in dashboard would provide transparency into large operations and prevent this class of issue from occurring silently.

Proposed Capabilities

-Status Tracking — show all active or queued large folder transfers (ownership, move, or copy) across the enterprise.

-Estimated Time Remaining (ETA) — progress percentage and item counts to completion.

-Rollback / Reverse Option — controlled, reversible transfer to restore ownership or hierarchy state if initiated in error.

-Reporting & Audit — exportable logs of who initiated the transfer, when, and what content was affected (including item counts and folder IDs).

-Workaround report - For parent folders with lots of subfolders and objects at the transferred level, a Google Sheet or CSV export with the Box file name, Box path (and recursive level), as well as the Box URL would be helpful to send to stakeholders to utilize to maintain business as usual by navigating to the Box link directly.

-Workaround permissions - A temporary Box Group can add the users at the parent level and be added to the destination owner's folder during the transfer to maintain permissions as an option before the transfer.

Value

-Prevents cascading, unintended ownership changes on large hierarchies.

-Gives admins real-time insight into progress and impact of long-running operations.

-Enables proactive response in case of accidental or malicious large-scale content moves.

-Reduces reliance on Support escalation for backend job status checks.

Example Use Case

A content move initiated on a single folder propagated recursively to millions of objects due to inherited permissions and ownership promotion. A dashboard with visibility and rollback would have allowed early detection and controlled recovery without requiring Support intervention.