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.
271 results found
-
extend external collaborators
Our internal policy expires external collaborators after 90 days. We have a few folders where we have over 400 external collaborators where we would like to maintain access beyond 90 days Is it possible to programmatically extend access to the users in those folders.
5 votes -
Box UI Content Explorer and Content Picker: Support Download ZIP Natively through top-level Element options
Box's REST API now supports ZIP downloads via the external API in addition to the internal managed web app. It has been a common ask to provide native support for this endpoint in the Box UI Elements - Content Explorer & Content Picker UI Elements through exposing the feature as a top-level option/property when rendering the UI Elements.
5 votes -
Expose user's last activity date and last login date via API
The Box CLI:GET commandlet is a good tool but if it could grab more basic information, it would be great.. For my company, we would like to see the Last Activity and Last Login of an end user's Box Account. This would help us determine when to de-provision a Box Account after we can verify it hasn't been used in X amount of time.
5 votes -
Expand maximum number of collaborators
We wants the max number of collaborators to spand past the 15k limit documented in the Scale and API boundaries.
5 votes -
Cleanup and Enhance the file/folder webhook events to cover all the happy paths (new file, new file version, restore previous version)
As a Box Application Developer I want to be able to receive a unique, webhook events for the following scenarios:
- User uploads new file (brand new binary object placed into a Box Folder) - Folder based event (exists: FILE.UPLOADED)
- User uploads a new file version - File AND Folder based event (e.g. FILE_NEW.VERSION)
- User restores a previous file version - File AND Folder based event (e.g. FILE_RESTORE.VERSION)
As the owner of an enterprise application that has deep integration in the BOX platform, it is surprising that I have no way to use the Webhooks to monitor files for new versions…
5 votes -
Transfer Ownership Enterprise Event
Currently, when you delete a user the only way to show that the content from one user to another user in the enterprise events are track two separate events:
- UPLOAD (Creation of the new folder with the user's naming convention)
- MOVE (From unknown location/user, to the new folder)This mean you needs to track the newly created parent.name and the move event with the item.name. I'm proposing two potential enhancements:
1) Enhance the MOVE event to show the source user/item details AND target user/item details.
2) Create a new TRANSFER_OWNERSHIP event so that you can distinguish between a…5 votes -
API to provide last access date in addition to modify date
In file/folder get info API, the last access date of the file and folder should be provided (in addition to the modify date)
5 votes -
Allow Search API call to search using wildcards
if I wanted to get the item ids of all files within a users account, I would have to run the Get Folder Items for all subfolders. If there’s a large folder tree, it would either take to long to iterate through all subfolders or I would run into an API rate limitation. It would be easiest if the Search API call can allow searching using wildcards so it would just take one API call to get a list of all item ids.
5 votes -
Add folder upload support to UI Elements
Currently, Content Uploader UI Element only supports uploading files. We want the ability to expand that functionality to folders.
5 votesGreat suggestion! We’ll look into it.
-
Request to Add Overwrite/Version Functionality to File Copy Operations via API
Currently the only way to add a version to a file is to download it and upload the new version with the If-Match header.
We are archiving files when a new file version is uploaded to a "main" folder, and to do that we have to download the existing version to our server and then generate a separate request to upload the file.
Ideally, we would be able to combine the requests into one - a COPY (https://box-content.readme.io/reference#copy-a-file) that can overwrite an existing file in the destination folder if the appropriate etag is supplied during the copy request.
5 votesThis is not something we will build due to other roadmap commitments.
Alternatively, you could always upload latest version to “backup folder,” delete file from “current version” folder, then copy “backup folder” version to “current version” folder.
This will get you 100% version history in backup folder and avoid the need to download & upload the file a second time.
-
Allow more than 10 redirect URIs in app configuration
Our app sits on top of regionally distributed infrastructure, supporting multi-tenancy, and we need to be able to configure more than the maximum of 10 redirect URIs that is currently allowed. It would be nice if we could configure as many as needed.
4 votes -
Support a parameter to remove all external collaborations for all folders and files under the given folder
Folder trees often needs to be cleansed of external users. It would be easier for admins to have a single call to traverse through a tree to remove external collaborations (external users, and possibly managed users, etc).
My suggestion is to add this as a parameter to the existing collaborations API call.
4 votes -
Add ability to use the shift key for multi-selecting group of items in the UI Elements Content Picker
Add ability to use the shift key for multi-selecting group of items in the UI Elements Content Picker
4 votes -
Adding Annotation events to Enterprise Event Queue API
Add the annotation events to the Enterprise Event Queue API.
4 votes -
Read Enterprise Settings using API
Is there a way to read Enterprise Settings using API? That would be much beneficial where the Admin can choose certain settings like Storage and there wont be a necessity to change the Code every time the Admin wants to change the settings. The API can read the existing settings and manage users based on those configurations. Currently, the application that manages Box accounts has to store those locally and every time there is a change in those settings, that calls for a Change management and code deployment.
4 votes -
Add ability to get a user's collaborations via API
Since there is a function to get a list of invitations to the group, I want to provide the same to the users.
Like,
https://api.box.com/2.0/users/:user_id/collaborations4 votesWe don’t currently plan to provide such an API, however please leave a comment if you have more information about how this would be used. In the interim, you can identify all of a user’s collaborations by requesting items in the user’s root folder (id = 0) and filtering out those where the owned_by user is the current user. This would require an additional API call for each item to get the collaboration id, but if you are only interested in knowing which items re collaborated versus owned by the user, it may be sufficient for your purposes.
-
Box CLI - need more output options for folders:items.
Specific to "box folders:items" but probably other commands as well:
1) If I'm asking for --csv, AND specifying the fields via --fields=, I don't need a header telling me the fields I just requested. I'd like an option to disable the header, or default disable it and make me add it back.
2) If I'm asking for specific fields as --csv, give me just those fields. If I'm asking for --fields=id I don't want it served back to me as "folder,#", I don't want to know it's a folder. If I later do something against that ID that is not…
4 votesHello,
We are not planning on changing --csv or --json behaviour in CLI.
Fields ID and Type are returned by API by default and removing them from the CLI would mean to modify the existing CLI behaviour.
-
API to sync folders for users.
If we could sync folders directly through our internal web app it would cut several steps out of user workflows. I would love to put a sync slider next to the job line so they could sync directly from this screen.
Specifically, I am talking about leveraging the tools via APIs. So having an API we could leverage to sync folders down for users.
4 votesThis request cannot practically be implemented as an API. A client needs to control the state of local items on an endpoint such as a user’s computer, much like the Box Drive or Box Mobile clients do today. The only planned supported means for such synchronization capabilities are the Box Drive and Mobile clients.
-
copy move or rename API events to include id of both the target and origin locations
In copy/move/rename events, the API should include the id of both the target and origin locations (from-to)
4 votes -
Populate accessible_by field in get collaborations
When managing collaborators, the end user needs to see who they have sent invitations to, even if those invitations have not yet been accepted and the other user has not created a box account. The call to get collaborations on a file or folder returns accessible_by: null for pending collaboration requests, essentially hiding the details of the pending requests and making it impossible to display those details to a user in a custom app. This data is definitely available because this feature exists in the main Box.com interface, but has not been exposed to the APIs yet.
4 votes
- Don't see your idea?