Apply File-Based Policies via API
Having retention policies at the file level (even if only available via API) would make integrations simpler when retention logic is coming from external sources (i.e., other systems).
Providing this functionality would allow for more elaborate use cases. For example, if a classified document is uploaded and identified, it can be automatically retained for a set period of time.
Folder-based retention for everything, as it leads to over-retention of content. In an ideal process, for example, when a document is switched from Draft to Final, the retention policy would be applied to the document (and would work for that version and future versions). We would also like retention policies to be managed within our tools, though the content resides within Box. In such a situation, the folder-based retention method is not an elegant solution, and single-file policies would assist in meeting these needs.
Currently, to achieve this type of solution, we must move content to a retention folder and back to its source folder every time there is an update made to that file. This creates a cumbersome process and requires custom development work in all scenarios.
