Define version limits by user, folder or file
We like the ability to set the number of file versions per user, folder or file
AdminAnonymous
(Why is this required?, Box)
shared this idea
Hi, this is an interesting idea, however, we would be worried about the configuration complexity of adding differing version limits below the enterprise level.
-
Anonymous
commented
Current State: Box auto-saves frequently (every few minutes) or upon hard saves in Word. This creates numerous versions (potentially v1-v50) during a single editing session.
Pain Point: Legal teams need to distinguish between meaningful document milestones and routine auto-saves. Currently, they resort to renaming files to track major versions (e.g., "Contract_BoxRL.docx").
Proposed Solution: Enable "milestone versioning" with custom labels, while grouping auto-saves as subversions.
Example Workflow:
v1: Initial file upload to Box
v1.1, v1.2, etc.: Auto-saved redlines (grouped as subversions)
v2 "Box RL": Legal marks editing complete with a label
v2.1, v2.2, etc.: Next round of auto-saves
This would eliminate file renaming workarounds and provide cleaner version history for contract management. -
Anonymous
commented
Example Workflow:
v1: Initial file upload to Box
v1.1, v1.2, etc.: Auto-saved redlines (grouped as subversions)
v2 "Box RL": Legal marks editing complete with a label
v2.1, v2.2, etc.: Next round of auto-savesThis would eliminate file renaming workarounds and provide cleaner version history for contract management.