Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
68 results found
-
Folder-Level Activity Reporting: Ability to Report on Activity and Access Stats at the Folder Level
Add an 'export' option available for folder Owners & Co-Owners to export various items at the folder level (meaning in the webapp - not the Admin Console) for
--Activity (uploads, download, moves, previews, create shared link, invite collaborators, etc.) in the folder
--Collaborations
--Etc.308 votesThis suggestion is under consideration by the Product Team for future development, however, it is not on our roadmap. Please share additional feedback and use cases to help us understand the importance of this release.
-
Option to request access to a folder
Request: If an external or internal user is forwarded a Box folder invite and they are not a current collaborator, they should have a mechanism to request the access and such request should automatically go to folder Owner/Co-owner for approval or decline. This should be done in a way that does not display or communicate the folder owners name.
Rationale: We have many external users that are part of large teams. Adding all (and maintaining) in the team is not feasible. These external users often forward the folder invites.
40 votesI would like to understand the use case better. Is the folder being shared externally using the shared link feature?
-
Templates - Restrict Templates to Specific Users/Groups and/or Folder Structures
Metadata templates are currently global across an entire EID. This does not scale well for large organizations with 50,000, 100,000 or more than 200,000 users.
This request is to add 'scope' parameters to Metadata Templates such that a specific template can be restricted to...
1. A specific set of users
2. A specific set of Groups
3. A specific Folder structure41 votesWe are currently scoping this effort, and plan to include it in our roadmap soon.
-
Shared Link Lookup Tool
Problem: Admins often need to do investigation of files stored in Box and all they have to go off of is the file/folder's shared link. Since admins can't search by shared link in the current Content Manager UI, a Shared Link Lookup tool would provide similar information.
Key Features:
-Provide ability to enter a shared link (standard or vanity URL)
-Information returned after searching:
-File/folder name
-File/folder owner
-File/folder location (Owner -> Folder hierarchy)
-Status (whether the file/folder has been deleted or not)
-Admin-level 'delete' (ability for the admin to delete the file on the spot)53 votesThank you for your input. This idea is considered for future roadmap. Please reach out to me if you like to share your use case.
-
Admin Trash -- Include Items in 'Trash' when using Search in Content Manager from the Admin Console
Search in the Content Manager does not currently include items in Trash. This is a security/eDiscovery challenge currently.
62 votesThank you for your input. This idea is considered for future roadmap. Please reach out to me if you like to share your use case.
-
Report / Customizable dashboard for a workflow
I would like to get an overall view of my workflow and which files are at which stages, including:
- How many files are in Step 1, Step 2, Step 3, etc.
- How many files have completed
- How many files were denied (or stopped in process)32 votes -
Custom 'Views' / 'Labels' to Organize Folders in Box
Request: provide the ability for end users to label or categorize folders in order to create different 'views' or 'workspaces' for their folders
40 votesValidating problems and solutions.
-
Ability to see owned vs. collaborated content
From content manager, we would like the ability to filter the content by only showing content the user is 1) an owner of and/or 2) is a co-owner of, and/or 3) is collaborated on.
When a user leaves the organization, we will disable the account for a few months. Before it is deleted, we would like to have the possibility to easily see the impact for other users if/when the content is deleted. If needed, we would then assign new owners for content collaborated on before that content is deleted.
4 votesThank you for your input. This idea will be considered for future roadmap. Please reach out to me if you like to share your use case.
- Don't see your idea?