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.
244 results found
-
box-ui-elements content-explorer needs real thumbnails
The Content Explorer element needs at least the option to use actual
file thumbnails rather than the generic ones based on file type
currently shown. Otherwise browsing large collections of images and
videos is very cumbersome to the point of not even being worthwhile. The
API appears to have a thumbnail/representation endpoint so using it from
content-explorer seems like a no-brainer.8 votes -
box-ui-elements content-explorer needs real thumbnails
The Content Explorer element needs at least the option to use actual file thumbnails rather than the generic ones based on file type currently shown. Otherwise browsing large collections of images and videos is severely handicapped. The API appears to have a thumbnail/representation endpoint so hopefully this is not a big ask.
Other things that would really improve Content Explorer for our use case:
- list/grid toggle button
- ability to hide the modified date and owner (useless for our application which is a repository of read-only archived files uploaded by an uploader app)0 votes -
Provide a Go / Golang SDK for Box
Add Golang SDK
1 voteAt this point we have no plans to add SDK support for Go/Golang
-
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 votesThanks for the suggestion! Providing a read-only scope for Users via API is not currently on the roadmap, but we’ll update this request if that changes.
-
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.
0 votes -
We want to be able to use the BoxAPI only from whitelisted IP addresses
We want to be able to use the BoxAPI only from whitelisted IP addresses
(For example, register the IP address list of our proxy server )We believe it is the best to be able to specify a list of accessible IP address range on the apps in the application registration screen
1 vote -
I would like to automatically set some options when creating a Box user. This is more about options in the Account settings.
We are currently provisioning automatically BOX users via our IDP and SAML assertion.When a user is added to an Active Directory group, his BOX account is automatically created.
I would like to automatically set some options when creating a BOX user. This is more about options in the Account settings. For example : country, number of lines displayed by page, default homepage…
Having particular attributes or API calls to manage these issues would fulfill the need.
1 vote -
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…
3 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.
-
A way to be able to select the rights of the developer console, which is similar to allow users to use Box Relay.
A way to be able to select the rights of the developer console, which is similar to allow users to use Box Relay.
This is a way to prevent users not to make sand boxes and API.7 votes -
Add "synchronize" or "versions" to the BoxCLI "folders:upload" functions
I am looking for a way to "synchronize" a folder and all of it's contents with the BoxCLI.
So, lets say i run this command:"box folders:upload /root/test_folder --parent-folder=%ID%"
How can i upload the folder, and only "Update" what has changed?
It would be nice to have something for "Folders" like you have for "Files"
"box files:versions:upload FILEID PATH"
maybe - "box folders:versions:upload FOLDERID PATH"
which would update all of the contents of the folder, version stuff that exist, add items that don't.
I know i can "box:folders:delete"... then "box:folders:upload" again.. but seems a waist of bandwidth and time..
3 votes -
Add "Box DICOM Import" functions to the BoxCLI
One thing that would be handy is to be able to upload a folder (of dicom files) and process the contents with the "Box DICOM Import" functionality using the BoxCLI.
Maybe something like: (add a flag to current box:folders:upload command)
"box folders:upload /root/test_folder --parent-folder=%ID% --dicom-import"
That would be Nice!
3 votes -
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 -
Bulk API support
It would be great if we have a bulk API option. I would like to pass in the list of entity ids(could be files, folders users etc) and get back the results. This will reduce the number of api calls we do to get all the information.
We try to manage client's storage accounts and the main problem is with rate limiting for a large clients.
Implementation can vary, either limit the response size or provide an ack id and developers can poll for the id and get the data back once the api is ready to spit out the…
24 votesThank you for the suggestion. This is an interesting idea but not one we currently have on the roadmap. In the mean time, you can apply techniques such as caching (i.e. fetch what you need once for a session and keep it in local storage) to reduce round-trips, and the use the ?fields query string parameter to request only the minimal set of fields you need, which can reduce API response times.
-
Total space used and total space allocated at enterprise level through API
Whenever we want to get total space used and total space allocated at enterprise level through api, we have to iterate through every user. Even then total space allocated at enterprise level would not be 100% accurate. If you guys can expose any api where we would get those information accurately.
1 vote -
Format Event Stream Event Types on Box.dev
On box.dev, please format the available event types for the event stream in a more readable format. Descriptions for the event would also be helpful.
1 vote -
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 -
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 -
Possible to unlock by just id of the lock object
Locks may have been destroyed by others.
In the current, just before releasing the lock, the owner of the lock needs to confirm that the owner is himself, so it is useless.
If we can release this from the object returned at locked, we can write logic more smartly.1 vote -
Clearer token scope documentation
Can you specify that the item_share scope for downscoping tokens is for shared links and not collaboration?
1 vote -
Ability to Initiate Custom CLI Scripts from Admin Console
Admin/Co-Admin Only Function.
For co-admins -This could be added as an optional setup parameter. Scope would be user administration and custom reporting. A user defined menu to initiate "batch job " . The script selection display could include script name, description and the ability to link to a documentation folder in box.1 vote
- Don't see your idea?