AdminKyle Adams
(Admin, Box)
My feedback
13 results found
-
5 votesAdminKyle Adams
(Admin, Box)
supported this idea
·
-
1 voteAdminKyle Adams
(Admin, Box)
shared this idea
·
-
1 voteAdminKyle Adams
(Admin, Box)
shared this idea
·
-
1 voteAdminKyle Adams
(Admin, Box)
shared this idea
·
-
39 votesAdminKyle Adams
(Admin, Box)
supported this idea
·
-
9 votesAdminKyle Adams
(Admin, Box)
supported this idea
·
-
19 votesAdminKyle Adams
(Admin, Box)
supported this idea
·
-
4 votesAdminKyle Adams
(Admin, Box)
shared this idea
·
-
5 votesAdminKyle Adams
(Admin, Box)
shared this idea
·
-
102 votesAdminKyle Adams
(Admin, Box)
supported this idea
·
-
318 votes
An error occurred while saving the comment AdminKyle Adams
(Admin, Box)
supported this idea
·
-
41 votes
We are currently scoping this effort, and plan to include it in our roadmap soon.
AdminKyle Adams
(Admin, Box)
supported this idea
·
-
2 votes
We are currently considering how to address customers’ needs for dealing with inactive content.
Reporting functionality for inactive content will be considered at a later date as we enable our customers to manage such content.
An error occurred while saving the comment AdminKyle Adams
(Admin, Box)
commented
Its easy to find active or popular files through the User Activity Report, Enterprise Events API, and File Access Stats.
However, its very difficult to identify content ROT (Redundant, Outdated, Trivial). The definition of ROT may vary for each organization. Example: For a given date range, provide a list of files that have NOT been Previewed, Downloaded, Commented upon, Copied, Moved, Locked, Unlocked, Uploaded, Shared, Add/Removed Watermarked, etc.
Providing a mechanism to identify ROT will improve folder browsing use cases for end-user personas.
Add file_id, folder_id, and user_id as filters to Enterprise Events APIs.
Currently, the only scalable way to filter/query enterprise events is to persist the data to a 3rd-party data store.