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.
- or
No existing idea results
- ~ No ideas found ~
9818 results found
-
Support more than two most recent web browser versions
I would like the Box to support web browsers of more than the latest two versions.
Although I certainly do not want to use legacy versions of years ago, it would be realistic to say versions less than one months old for instance should be supported.
Whilst a new version of Microsoft Edge is released every few days, the Box requirement of the latest two versions is a little too onerous.1 vote -
Enabling Ready Sign Links for Part 11 CFR
Currently, if a CFR-enabled user created a template, all Ready-Sign Link requests that come from that template will not be CFR compliant as this is not enabled. If implemented, it would enable all templates that are created by a CFR enabled user to be CFR compliant.
2 votes -
Function to erase gridlines in Excel files when using BoxSign
We usually hide the gridlines of Excel files.
However, when we sign an Excel file using BoxSign, the gridlines is displayed in the PDF file.
Since the display of gridlines makes it difficult to understand the display of materials and affects business, we would like you to be able to erase the gridlines of Excel files even when using BoxSign.【BoxSign利用時にExcelファイルの罫線を消す機能】
普段、Excelファイルの罫線は非表示にして利用しています。
しかし、ExcelファイルにBoxSignを用いてSignした際、PDF化されたファイルには罫線が表示されてしまいます。
罫線が表示されることで資料の表示が分かりづらくなり、業務に影響があるため、
BoxSign利用時にもExcelファイルの罫線を消せるようにしていただきたいと思います。22 votes -
Comments in Box Notes
When entering comments in boxNote, we would like it to be clear which part the comment pertains to. (Imagine adding comments with the relevant section highlighted, similar to using a marker.)
2 votes -
Fix missing Access-Control-Allow-Origin header for CORS 401 requests
This relates to the upload files API endpoint (https://developer.box.com/reference/post-files-content/) but likely applies to other endpoints as well.
When making a call to the above endpoint via CORS, you provide a Bearer token to the request. This token is used to identify the box account to make the request on behalf of, which is then used to return an Access-Control-Allow-Origins header configured to that box account's CORS whitelisted domains.
In the case of a successful request to the above endpoint, the OPTIONS preflight request returns the Access-Control-Allow-Origin header with the request origin set. The actual POST request then returns a 201 with Access-Control-Allow-Origin: *.
In the case of a domain mismatch, I assume the Access-Control-Allow-Origin header would not be present on the POST request, causing a CORS failure.
However, if the token has expired or is otherwise invalid, the API cannot identify which Box account to run as. The OPTIONS request still returns the requesting origin as the Access-Control-Allow-Origin header, however, the POST request returns a 401 status but no Access-Control-Allow-Origin header.I assume the above is because the valid token is used to identify whether the CORS request is from a valid domain. The consequence of this is that browser CORS protection kicks in, and the resulting 401 error cannot be read, even though it originated from a valid domain.
Two proposed solutions:
1. Allow the requestor to specify the account id (or some other way of identifying the box account) in the request. The app can then use this id instead of the token to determine the appropriate CORS domains. This will, of course, allow unauthenticated requests to trigger a CORS check for a particular account. However, this is standard for CORS. The CORS layer is designed to trigger before other parts of the request.
2. Always return the Access-Control-Allow-Origin header for 401 requests, either as "*" or as the requestor origin. This of course basically exempts 401 requests from CORS protection, so should likely be only enabled as an optional setting in your box account.This relates to the upload files API endpoint (https://developer.box.com/reference/post-files-content/) but likely applies to other endpoints as well.
When making a call to the above endpoint via CORS, you provide a Bearer token to the request. This token is used to identify the box account to make the request on behalf of, which is then used to return an Access-Control-Allow-Origins header configured to that box account's CORS whitelisted domains.
In the case of a successful request to the above endpoint, the OPTIONS preflight request returns the Access-Control-Allow-Origin header with the request origin set. The actual POST request then returns…
1 vote -
Name Issue
It's way too hard to see the full names of my documents. I don't always care about upload date/size. Sometimes I just want to be able to expand the name section so that I can see the full name. Also, the 'upload date' and 'size' sections are WAY too big given how few characters are used to relay their data.
1 vote -
Bulk Adding Unmanaged Users with the Same Organization Email Address
Mass add unmanaged users with the same orgainization email address. Currently have to manually add each unmanaged users.
1 vote -
Warning or reminder on unsuccessful transfers
Box Drive should present a pop up when a new unsuccessful transfer occurs, or there's pending transfers that need to be remediated. As of right now, if a user creates a folder or drag and drop folders and files in a location they're not supposed to (no permission, for example), no warning or error message is given to the user.
The files and folders are then listed in "Unsuccessful Transfer" section on Box Drive, but no reminder is given to the user or any warning that their files are in limbo. They could be working for months without knowing their stuff is not being uploaded, since they expect for Box to "just work" and when no pop up warning is displayed the assumption is that it's all good.
Box Drive should present a pop up when a new unsuccessful transfer occurs, or there's pending transfers that need to be remediated. As of right now, if a user creates a folder or drag and drop folders and files in a location they're not supposed to (no permission, for example), no warning or error message is given to the user.
The files and folders are then listed in "Unsuccessful Transfer" section on Box Drive, but no reminder is given to the user or any warning that their files are in limbo. They could be working for months without knowing their…
2 votes -
Out of Office Setting for a user profile
People go on holiday, and people have specific notification settings set for themselves.
So it would be a nice feature if a user could have a setting in their profile that redirected their notifications to another BOX user or group for a period that they set in their profile. Also remind them when they login that they have the setting turned on as to not redirect for longer than required.2 votes -
Be able to set your personal notifications to also include someone else.
Be able to set your personal notifications to also include someone else.
Many of our users work in teams, so it would be good to allow a user the ability to specify if another BOX user or group should receive the altered notifications that they receive.
2 votes -
Restrict expiry time length
By default we have set an automatic expiry length after 7 days, but a user can change that manually when they share the content.
It would be nice to have an admin setting that allows a maximum time our users can adjust the sharing length of time to.
i.e. a setting for say no more that 90 days from the date of the share.2 votes -
More than 150 files in collections
Expand the number of available items that can be added to a collection.
We have users who work on campaigns and need to collect files from lots of different locations, this and in come cases exceed 400 files, and we believe the limit is currently 150.2 votes -
Allowing "Viewers" to download excel files with a watermark
People granted "Viewer" permissions should be able to download excel files with a watermark, rather than only being able to download a watermarked PDF version
1 vote -
Insights Total Storage File Types
Add more file types in insights. Because of the kind of files we work with, most of it says other.
1 vote -
When reverting to the previous version on box, V3 → V2 = V4. I would like to keep the version name as V2 instead of V4. Is it possible?
When reverting to the previous version on box, V3 → V2 = V4.
I would like to keep the version name as V2 instead of V4. Is it possible?
Senior employees are not familiar with the system and are confused about what it means to have a new file even though they have returned it.1 vote -
[Folder Settings] - [Restrict access to this folder via shared links to collaborators only] Please tell me how to change the settings for a
Please let me know if there is a setting that allows me to check at a glance whether the corresponding setting is enabled for all employees.
1 vote -
[Folder Settings] - [Restrict access to this folder via shared links to collaborators only] Please tell me how to change the settings in bul
[Folder Settings] - [Restrict access to this folder via shared links to collaborators only]
Please tell me how to change the settings for all employees at once.1 vote -
Restrict Access Right to Sub-Folders
Hello,
After creating FOLDER A and SUB-FOLDERS B, C, D under A, along with sub-subfolders E, F, G under B, I granted User X viewer access to A. However, I aim to restrict or remove their access to C, E, F, and G. Unfortunately, this functionality isn't currently available with Box.com. Could you consider adding this feature? Thank you!
6 votes -
Use Device Based Authentication for Box for EMM on iOS
To enforce device compliance requirements through Microsoft Conditional Access policies, the Box for EMM app would need to use the Microsoft Edge browser when completing SSO on iOS. It currently uses Safari to complete SSO, which doesn't allow the Conditional Access policy to properly check information about the device.
Microsoft Support suggested requesting Box for EMM on iOS to use device based authentication to allow the Conditional Access policy to apply correctly.
2 votes -
Rich text for Box Sign email_message field
Allow for formatting with email_message field of the send box sign request api request body
1 vote
- Don't see your idea?