Would be great if Box had a company intranet functionality similar to platforms like Simppler, Igloo, Claromentis, Jostle, etc... Many of them integrate with Box, but one stop shopping is always preferred. A digital workplace is so important now that so many are working remotely. Bringing all of our apps under one roof (e.g., Box, Salesforce, Teams, Zoom, Yammer...), giving employees a portal/hub to go every morning to improve communication, lighten the inbox, providing a place to hold not only our knowledge but our policies, forms, news, process management for things like onboarding new hires, training staff, etc...

A server side authentication token that is long lived and provides access to all endpoints, not just read and write like JWT auth. I have posted a support ticket here describing my needs: https://support.box.com/hc/en-us/community/posts/1500000258202-Server-Side-Authentication-Scopes

Instead of having to provide a fileId to perform an action on any given file, it would be nice to be able to pass a pathname as an alternative option

Be able to tag files from iOS devices within the Box app. This will be helpful for people on the go who want to be able to do tasks from their iPhone or iPad.

Box Content Explorer currently supports dynamically sized columns with the browser window width, but user-resizable columns are needed to accommodate large items' names.

We want app user functionality to crawl a given Box folder and refresh every 24 hrs so we always have the latest document ingested into Watson Discovery.

Improve wording on Box Edit confirmation prompt

When a file is opened with Box Edit from UI elements, we display a confirmation prompt that asks user to proceed or not (this is UI elements only and not displayed when opening file from webapp). Currently, the prompt lets you choose approve/reject, but we want this text changed to OK/cancel (just like other Windows apps).

When calls are made to https://developer.box.com/reference/get-events?stream_type=changes, we expect changes made to Box Notes to be reported. Currently, they're not being reported.

Change the location where appearing warning message on Box Edit when opening with "UI Elements Open with"

Would like Box Edit to appear warning message on the monitor where is located browser that users try to open with it
Currently the warning message appears in primary monitor but this would be inconvenient if they try to open with it on browser in secondly monitor.

We would like to be able to run reports through the API. Having the ability to automate running reports would be very helpful for automating processes.

It would be good to see php support for the Box SDK.

We have to automate the process where I need a code to send an optional message along with a collaborator invite. With Box Ui we can send optional message along with collaborator invite but I didn't find any method in BOX SDK .

Update API to retrieve comments associated with items in Trash

Currently, an application can only be defined with a single OAuth Reply URL. This is very restrictive for applications where multiple authentication endpoints are required.

The workaround is to define multiple applications, but this doesn't scale well.

In my experience, all other OAuth providers I've used allow for many URLs to be defined within a single application.

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.

Why don't you at least include some guidance on https://developer.box.com/docs/box-cli regarding where to start if you are using Linux? I have been unable to effectively use my box account since the webdav support ended, and every so often take another stab at it. It would be nice if this page at least pointed to the best resources for installing on Linux, rather than just giving a link to the download pages.

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.