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.
256 results found
-
API technical and display name
In metadata template designer: As in the API technical and display name are saved, at least the display name has to be changeable while the technical name has to be presented as a valuable information.
2 votes -
"Scopes enabled by request" in the app authorization page
Would like the "scopes enabled by request" (https://developer.box.com/docs/scopes#section-scopes-enabled-by-request) which have been enabled on their app to be listed in the app authorization or in the configuration page for their app in the dev console.
2 votes -
Make API rate limits more sophisticated, especially for large enterprises
When working with a Box Enterprise that has tens of thousands of users, scripts designed to do things like user information syncing, group syncing, or user provisioning/deprovisioning often run into real issues with the Box API rate limits.
Some calls (e.g. downloading or uploading a file) are clearly significantly more resource-intensive than others (e.g. getting a user’s aliases). The method Google has implemented for the Gmail API (see https://developers.google.com/gmail/api/v1/reference/quota) seems like a really great way to balance the need to protect the back-end systems against the need for increased performance for less-intensive calls. It would be nice if Box…
33 votesThis will be considered for the FY24 roadmap, not planned for FY23
-
Add support for bulkified retrieval of box folder ids
toolkit.getFolderIdByRecordId needs to be bulkified. Otherwise the method is very vulnerable to Salesforce governor limits.
3 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 -
Open Box Notes API for logging
The idea here is to use a box note as a log which could be updated both by humans and an automated api.
My use case for the api would basically be "append a line" to the box note.
3 votes -
Add FolderID in error messaging when attempting to create a folder of the same name in the same path through API
Receive the folderID for an already created folder when attempting to create a folder of the same name in the same path through API.
2 votes -
Enhance deprovisioning via API
We want to use the API to see who’s collaborating with someone who’s been rolled out of the university, as part of deproviosing script. Then we want to look up collaborations of user being deprovisioned and break all collaborations when a user is rolled out
6 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 -
ReadOnly Downloads
Allow files to be downloaded via the API when the only Application scope checked is "Read all files and folders stored in Box". Preferably as well users should be able to go into the list of apps authorized to access their files and enforce readOnly access as well.
It is a completely unnecessary liability for apps that only need to download files, and an unnecessary security risk for a User/Organization's data.
2 votes -
Allow Enterprise Event API Endpoint to access 7yrs worth of data to match the activity reports provided by the web app
Enterprise Events API endpoint only allows retrieval of events up to one year back. Activity reports in Box go back 7 yrs. Events contain a lot more useful data than activity reports so the request is to match the retention period between the two so the same amount of data can be collected via the API or web application.
9 votesBox does not currently plan to extend the lookback period fo Enterprise Events.
-
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.
-
Add Custom URL for shared link via API
Please add support to set custom url when setting up a shared link via API.
We would like to have this feature to automate our operation when new contents have been added to Box.
2 votes -
Add length of field to API documentation
It would be nice to explicitly mention the length of some of the fields. In our enterprise account all the users had 10-digit UIDs, so I thought that was the standard length, but we had some users with preexisting lite accounts rolled in and a few of them had 8-digit or 9-digit UIDs. I see now that the example UID provided had 9 digits, so my bad there, but I initially just looked at the 'id' attribute under 'user object' to try and find the length and it would be nice I think to have something like 'id / string…
1 voteThanks for the suggestion. We generally don’t provide lengths for fields unless there is a concious decision to define a specific length or range as a contract. Given that the type of field for user id is a string, the fact that user id values ranged from 8-10 digits is an implementation detail, not a guarantee.
-
Add field to see how a collaborator was added to a folder
Currently the has_collaborations field with the API will show if a user was added as a result of inheritance (waterfall permissions) or if they were added directly to the specific folder, but there is no way to distinguish between those. For performance reasons and limit the amount of calls, it would be helpful if there was a filed that could be added to distinguish how a collab to a folder occurred
2 votes -
Custom notifications using Box API
Using Box API there is no way to create custom user notifications. It might be helpful to send some information to the customer that some documents have been moved, imported, etc. A user can monitor the folder but this would be a valuable extension for the API for platform developers.
12 votesThanks, this is a great suggestion but not one that is currently on our roadmap. In the mean time, you can consider using Webhooks to get relevant events and make use of a simple transactional email/sms API such as those provided by Twilio/Sendgrid or Amazon SES to send notifications based on those events.
-
Update Classifications via Box's CLI
Update existing Classifications on files via Box's CLI
2 votes -
Make license type info available via API
We'd like to get the license type info (free or paid) when getting the below log by API.
- eventtype:COLLABORATIONINVITE
- event_type:SHARE
Account Type: Unmanaged User / Managed User, etc
User TypeL Lite (10GB) / Enterprise (Yearly), etc3 votesThis is not currently planned as there is unclear purpose and implementing it may expose sensitive information.
-
Allow multi-select of files to download from Content Explorer UI element
Our use case is using Content Explorer to allow users to interact with content in Box. If a user wants to download multiple files via Content Explorer, they either have to download one-by-one, or launch the Content Picker UI element and identify their files again. If Content Explorer supported either multi-select or a checkbox multiple select, users could then download their files with one click.
Specific business process: when working with insurance claims, adjusters regularly need to find and download several images to share with another insurance company to process the claim. Out of 100+ images in the claims folder,…
12 votes -
Enhance API for group membership search
Current implementation of user group membership search is very inefficient.
both
api.box.com/2.0/groups/GROUPID/memberships
and
api.box.com/2.0/users/USERID/membershipsRight now we have to search for membershipId for given groupId and userId .
Our customers have thousands of groups and users.Ideally we should fetch membership info like
GET api.box.com/2.0/group_memberships?groupId=<id>&userId=<id>5 votes
- Don't see your idea?