Skip to content

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

217 results found

  1. Need to send message with collaborator invite by using java SDK or any rest point

    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 .

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Improve wording on Box Edit confirmation prompt

    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).

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Provide php SDK

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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Remove 100 "to_user_ids" limit of WebhookV1.

    With webhook V1, we have the upper bound of 100 users in "touserids" field for each notification, so when a webhook has too many recipients (that is, more than 100 users are to be set in "touserids" field), we send multiple webhook notification for a single event so "touserids" is kept within 100 users for each notification.

    For e.g. if an upload event was to trigger notification to 1000 recipients, we send 10 webhook notifications to the notification url with 100 users embedded in "touserids" field of each notification.

    This causes duplicate…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Provide read-only scope for user information

    I'd like to provide our central identity management team a way to tell whether or not a given Box user has a > 0 byte usage before they delete the user's account (for example, as someone leaves our organization). I'd like to give them read-only API access to https://api.box.com/2.0/users, without giving them any additional access. Support tells me that this isn't currently possible. It'd be nice if it was--this could be useful for a number of other uses, too, such as reporting.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add Support for Reading Tags on Weblinks

    You can currently add tags for weblinks via the API, but can't read them. This is a huge oversight, which makes it nearly impossible to add any sort of dynamic filtering capabilities. That is, there's no way to return (or parse) out a list of available tags -- since you can't read any of them.

    To accomplish any sort of dynamic filtering, you have to bypass the tags altogether and add them to a field you can read. For example, after a colon in the title field. However, that's a temporary stop-gate solution with issues of its own.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Allow non-admin users to call 'Get Enterprise Users API'.

    I want to develop a program that provides an auto-completion feature that displays the names of enterprise users.

    However, the current "Get Enterprise Users API" could only be called by co-admins.
    I also want to be able to call from other than co-admin.

    By the way, "Get Groups API" could be called from other than co-admins by providing the filter.
    I think there is a contradiction in this specification.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Asynchronous API calls that return a JOB_ID rather than having the session cancelled after 60 seconds

    Currently API calls like the "Move Owned Items" almost always run longer than 60 seconds. As a result the session is killed by the Box infrastructure. The "Move Owned Items" task continues to run in basically an asynchronous background mode. But once this happens, the automation process has no way to check the status of the "Move Owned Items" task.

    A graceful way to handle this would be to return control back to the caller normally with a JOB_ID that can be used to call back to the "Move Owned Items" API call to check the status of the "background"…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. "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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Update Classifications via Box's CLI

    Update existing Classifications on files via Box's CLI

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Make source.parent.name to include all of path

    source.parent.name show just folder name.

    For example, if the collaborator folder is A and it lcates “All files/A”. the customer get api.box.com/2.0/events?streamtype=adminlo..,

    source/parent/name just show A. This behavior make the user not to find the folder easily.
    It should be shown “All files/A”

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Support for Collections in Content Explorer & Content Picker

    Some of our use cases revolve around searching for specific metadata field or date range.

    If UI Elements were able to be initialized with a collection, this would allow us to pass in a specific collection of files and display them easily even though those files may live in disparate folders.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Pull list of all collaborators with a certain user_type at a folder level

    Currently, you can only search by user_type at the enterprise level as documented here: https://developer.box.com/v2.0/reference#get-all-users-in-an-enterprise

    It would be helpful to be able to do this at a folder level as well.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Surface either EID or user_type when requesting collaboration object

    Currently, requesting a collaborationobject does not surface either EID or usertype. (as seen in https://developer.box.com/v2.0/reference#get-collabs)

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This request is not currently on our roadmap but we’ll update this request if that changes. In the mean time, you can use a subsequent request to get the user information and specify the enterprise in the `fields` query string parameter.

  20. Using folders:items is not recursive

    Running the command
    box folders:items [IDOFFOLDER] --csv --save-to-file-path=[PATHTOFOLDERTOSAVE_REPORT]

    To get a list of files and their respective SHA1 values is difficult as this command has to be run on each folder within the tree. There should be a recursive option, or better yet, a report a user can run to provide the SHA1 values within a tree. This is very important for eDiscovery and chain of custody.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base