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

35 results found

  1. Avatar API Driven Capability

    Avatar —

    Customer would love to have the API Driven Capability to Upload to the user’s Avatar, and might require additional API parameters like “center point” to ensure a portrait is centered.

    Customer stores Avatar/Portraits of their people in centralized personnel databases, which is the key store for that data. Their users engage with it there for uniformity. Also API Driven would allow them to build Avatar Processes into their Native Mobile Apps that also impact their Box Experience in a positive manner.

    They already have several workflows that output Avatar to outside systems upon change internally.

    7 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. Provide overwrite switch in CLI to account for existing folder in download location

    Currently BOX CLI download doesn't have overwrite action. If a folder already exists in the location where the new folder is being downloaded, the CLI errors out.

    There should be a over-write switch to the box CLI folder download. It should be something like:

    box folders:download Folder_ID --destination=<location> --over-write=Yes

    8 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. Update the .NET SDK to support .NET Core 3.1

    The current .NET Core NuGet package is set to support .NET Standard 1.4, but this means that support for old libraries is required. For example, the SDK throws exceptions when getting an admin client due to incompatibilities with System.IdentityModel.JwtToken >= 5.4. These sort of problems are going to continue to happen as the framework progresses.

    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. Display service account login in JWT app configuration console.

    Request:
    It would be really helpful if the service account login were displayed on the JWT app configuration page. This would make it easy to identify the login without having to run a separate script and would lower the barrier to entry for developing unprivileged BOX JWT apps.

    Background:
    We are making heavy use of service accounts to promote development server/automation-friendly Box apps. Our development model, outlined here (https://github.com/box-community/sample-jwt-app-primer) involves inviting low-privilege service accounts to collaborate on folders. This enables programatic access to Box files on a selective basis.

    A major pain point is identifying the login associated…

    22 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. 15 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. Allow Metadata search for files uploaded via Box API

    Documents in BOX are not searchable based on Metadata when uploaded using BOX API

    Document uploaded into BOX via EPHESOFT using BOX API and 3 metadata elements are attached to the document. We can see the document in the BOX and the metadata elements are present in the Custom Metadata section in the 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)

    There are two ways to find files in Box based on the metadata. The existing Search API provides a metadata filtering option and also indexes metadata content. The Metadata Query API provides SQL-like syntax for finding files based on specific metadata condtions. See https://developer.box.com/guides/metadata/queries/create/ and https://developer.box.com/guides/search/full-text-search/

    If there are unmet needs please add a comment!

  7. error in documentation

    On the Authenticate with JWT (SDK) page the Node code snippet creates a const "configJSON," but then when the page references it later, it calls it "appConfig" in another code snippet instead. It references the enterpriseId in the configJSON variable but calls it appConfig.enterpriseId out of nowhere instead. The code breaks like this. Please fix for the sake of people trying to use these code snippets.

    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)
  8. Stop interception of browser search shortcut in developer docs

    The box developer docs hijack CMD+F and that's exactly not what I expect it to do

    CMD+F is a shortcut for most (all?) browsers to bring up a native Find dialog, but your reference docs hijack it in favor of some type of auto-complete search on the page which is actually never what I want, or expect to happen.

    https://box.dev/en/reference/

    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)
  9. Qs re: API and "is_external_collab_restricted" parameter

    I believe that the API allows for updating the "isexternalcollab_restricted" parameter. However, the API documentation and example does not illustrate this. Would you kindly update the documentation on this?

    If I'm wrong and adjusting this paramter via the API actually isn't possible, would it be possible to request this be available?

    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)
  10. Add Python code example

    On page https://developer.box.com/docs/work-with-users
    It would be super-helpful to have a Python example for Generate a User Access Token.
    I've had a tough time finding the right Python call to use for App Users for getting an access token.

    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)
  11. Clarify Python example

    On page https://developer.box.com/docs/work-with-users
    Creating a new App User, Python.
    Should specify login=None for clarity in create_user() call. Also add

    Specify login=None to indicate you are creating an App User.

    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)
  12. API currently doesn't expose email addresses of non-Box uploaders who upload via email

    Specifically in the context of uploading via email.

    API currently does show emails of uploaders that are Box users, whether in enterprise or not. It does not show emails of uploaders that are not Box users (name shows as "Unknown User".

    Webapp shows names for Box users, email addresses for non-Box users. It seems odd that the webapp would expose the email address but the API doesn't.

    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)
  13. 3 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. More efficient way to get metadata on files in search

    Search by metadata returns a list of files. That list isn't much use without knowing the metadata it matched. To use Box's metadata for anything past the initial search query that's related to display, each individual search result must be queried for its metadata.

    4 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. Unmanageable API Key Whitelists

    Enterprises with a lot of active software development groups have unmanageable API Key whitelists. This manifests in a lot of ways.

    There is no way to limit API Keys to development (limit liability). Typical dev-qa-prod cycle requires 3 API keys. No way to associate API Keys to specific projects. There is no way to tell if old API Keys are still in use.

    13 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. Ability to pull API calls report from Admin Console rather than relying on CSM to get information

    The ability to pull reports showing how many calls they are making on a certain period.

    9 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. 401 Error Description

    Increase detail provided in 401 (token can't be generate, access expired) response when working with SDK.

    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)

    We have made several updates to our SDKs since this was filed. If there is a specific API / SDK that’s still not returning the appropriate error message, please leave a comment to let us know.

  18. Difficult Managing App Users in Admin Console

    We've already purchased EKM and would like these app users to be managed within their main enterprise account so that they can own the encryption keys.

    If Box were to create the App users under their main enterprise account, this would adversely affect the ongoing administration of the core Box experience.

    For example, app users would appear in the same tab as managed users. The admin event feed would also be capturing all the interactions of the 10,000 additional app users.

    We have strong concerns that the addition of the 10,000 app users will make it difficult for us to…

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

    App users and managed users are now separated in the Admin Console. App users are hidden by default but may be viewed by switching filters within the Admin Console. See this post for more details: https://community.box.com/t5/Box-Product-Updates/App-Users-Filter-in-Users-amp-Groups-Tab/idi-p/67874

    The separate request to provide a filter in the Admin event stream has been logged as a separate idea here: https://pulse.box.com/forums/909778/suggestions/37027681

  19. File ID for older file version

    To enable the ability to preview older file versions without promoting them to current.

    0 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)
  20. 0 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)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base