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
9875 results found
-
Create JSON file from Form
It would be very helpful to have the option to create a JSON file from the fields in a form to be used in a Doc Gen template. This would save us much time and frustration vs. manually creating the JSON.
2 votes -
AI Agent Suggested Prompts Need Additional Detail Capability
The ability to define the suggested prompts is very helpful. However, as we build very targeted agents we find the prompts, not custom instructions, need to be more detailed, which makes them long. It would be very helpful to customize the suggested prompt button with a short descriptions but have the actual prompt input in a separate text box and hidden from end-users. The hidden, long, prompt would run when the visible prompt is selected.
Something like this would be a big win for us. Please let me know if this is not clear.
2 votes -
Request to automate shared link generation upon file upload
A customer regularly uploads files into multiple folders (with different locations and hierarchy levels) and then has to generate a shared link for each file. Currently, they need to create each link manually, which is quite time-consuming.
It would be very helpful if features such as Relay could automate this process by automatically generating shared links for uploaded files and sending notifications with created links
1 vote -
Support streaming uploads or appendable upload sessions (unknown final size)
I have a use case where data is generated continuously (sensor readings). I want to build a file in Box by streaming bytes over time and then finalizing the file when the session ends.
Currently, Box’s chunked upload API requires specifying a file_size up front and mandates a fixed total in each Content-Range header. This prevents uploading content when the final size is not known at the start of the session.
Request:
Add support for a streaming or appendable upload workflow, where:- A client can create an upload session without knowing the final file size
- Chunks can be uploaded incrementally as data is produced
- The file size is determined at commit time, not at session creation
This would support scenarios such as live sensor feeds or any workflow where file contents are produced continuously.
Is there an existing workaround or planned support for this capability?
I have a use case where data is generated continuously (sensor readings). I want to build a file in Box by streaming bytes over time and then finalizing the file when the session ends.
Currently, Box’s chunked upload API requires specifying a file_size up front and mandates a fixed total in each Content-Range header. This prevents uploading content when the final size is not known at the start of the session.
Request:
Add support for a streaming or appendable upload workflow, where:- A client can create an upload session without knowing the final file size
- Chunks can be uploaded incrementally…
1 vote -
Improvement of search within the Hub
We would like to search for information within texts in the Hub, not only from files and folders in the Hub.
Currently, to enable information search within the Hub, we compile all information in Box Notes and add it to the Hub. However, this results in longer access times for users. We would like to improve the issue where supplementary texts written within pages are not searchable.2 votes -
Add Section Divider Lines and Blank Fields for Cleaner Forms
I would recommend adding divider lines to allow cleaner grouping or sectioning of fields in a form. It would also be helpful to have "blank" field for better organizing when adding fields in two columns but the number of fields for a particular topic is an odd number. Having a blank filler field would allow starting the next topic on the next row rather than beside a field that isn't related. This would make the form look cleaner and be easier for end-users to follow.
2 votesWe've released the static text field that should resolve the blank field request and we've decided to prioritize multi page forms which could serve as a workaround for Divider lines.
-
Couldn't see full group name
When collaborating, if the group name is long,
the part that doesn't fit in the UI gets truncated.
Is it possible to improve the UI so that the entire group name is displayed?
This happens both when collaborating and when viewing the collaboration list.ーーーーーーーーーーー
(日本語)
コラボレートの際にグループ名が長い場合、
UI上に入りきらない部分が見切れてしまう問題がある。
UIの改善でフルグループ名を表示できないか？
コラボレートする時とコラボレート一覧を表示する際の両方で発生している。1 vote -
Display by name, Alphabetical as a Default. Necessary for our business!
It is 100% Necessary for our file Storage and Sharing needs for files to show up alphabetically BY DEFAULT. We just transferred over from Dropbox, and this is really annoying and a waste of time to have to set viewing each time we log in, and when we share files to have to explain to customers how to set their display. Display by name alphabetical should not only be an option, but a Default. Please make this available immediately. Our business model and client sharing workflow success depends on this. Thank you for implementing right away
1 vote -
Ability to Customize Styling of Box Sign Email Notifications
Hi Box Support,
I’d like to submit a feature request for Box Sign regarding the email notifications that are sent to recipients when requesting signatures.
Currently, these emails appear to use a standard layout and font, with limited ability to customize the visual presentation. It would be extremely helpful to have the option to customize the email’s styling, including:
Font size and font family
Line spacing and paragraph formatting
Branding options (e.g., header image, color accents)
HTML support for enhanced formatting
This would allow users to create a more professional, brand-consistent, and user-friendly experience for signers. Even limited template or styling options would be a big improvement.
If this is something being considered or available via an enterprise or API-based solution, I’d love to learn more. Otherwise, I hope this request can be considered for a future update to Box Sign.
Thank you for your time and for the great product.
Best regards, haej
Hi Box Support,
I’d like to submit a feature request for Box Sign regarding the email notifications that are sent to recipients when requesting signatures.
Currently, these emails appear to use a standard layout and font, with limited ability to customize the visual presentation. It would be extremely helpful to have the option to customize the email’s styling, including:
Font size and font family
Line spacing and paragraph formatting
Branding options (e.g., header image, color accents)
HTML support for enhanced formatting
This would allow users to create a more professional, brand-consistent, and user-friendly experience for signers. Even limited template or…
5 votes -
Share multiple files at once
Currently, you can only share one folder/file at a time. Not a smooth process.
1 vote -
We would like to see Box Hubs have a separate shared link permission setting
Currently, Hub shared links can be allowed from “Enterprise Setting” > “Content & Sharing”, but with the current settings, if Hub shared links are disabled, general folder and file shared links will also be restricted, which is very inconvenient.
Therefore, please consider making the shared link setting of the Hub independent, and allow shared links to be allowed for each individual Hub.【日本語】
現在Hubの共有リンクは、「管理コンソール」＞「コンテンツと共有」から許可できますが、現在の設定値ではHubの共有リンクを禁止すると、通常のフォルダとファイルの共有リンクにも制限がかかってしまい非常に不便です。
そのためHubの共有リンク設定を独立させ、Hub個別で共有リンクの許可を行えるよう検討をお願いします。11 votes -
Expand number of folders displayed in folder hierarchy
Our team works in incredibly deep folder structures and would appreciate the opportunity to view all subfolders in the folder hierarchy to more easily navigate through our folder structure. For example, if someone shares a file with me and it's in the "trailers" folder, it's very difficult for me to tell which project this is associated with unless I navigate many levels up in the folder structure to see a folder with the project name. Ideally, we would be able to see as many folders as can fit in the window space. Our team uses the Box web app and is not interested in leveraging Box Drive.
Our team works in incredibly deep folder structures and would appreciate the opportunity to view all subfolders in the folder hierarchy to more easily navigate through our folder structure. For example, if someone shares a file with me and it's in the "trailers" folder, it's very difficult for me to tell which project this is associated with unless I navigate many levels up in the folder structure to see a folder with the project name. Ideally, we would be able to see as many folders as can fit in the window space. Our team uses the Box web app and…
4 votes -
Changing default columns view in File Explorer with Box Drive - Move or hide sync status
The recent 2.48.250 release has forced a new Sync column in File Explorer. This new column is fixed in position and can't be hidden. I, for one, don't care to have this column take us space in the Explorer as I have a smaller laptop screen.
When you select the column and hide in Explorer, it shows up at the next refresh back in the same position.
The integration with File Explorer should follow Windows 11 preferences and be adjustable just as OneDrive is.
1 vote -
Ability to exclude invitation restrictions in tenant settings in Hubs
We would like the ability to add folders with editor privileges in Hubs, even if only co-owners or higher can be invited in the tenant settings, so that it does not affect the invitation restrictions in the tenant settings.
Anticipate that many companies will not be able to change the invitation restrictions on the tenant side due to personnel issuances, security risk avoidance, etc.
Like to see this feature implemented, as it would improve the convenience of Hubs if there is a function to prevent tenant settings from affecting Hubs.テナント設定で共同所有者以上のみ招待可能な場合でも、Hubsでは編集者権限を持つフォルダを追加できるように、テナント設定の招待制限には影響しないようにする機能が欲しいです。
人事発令やセキュリティリスク回避等で、テナント側の招待制限を変更することができない企業は多い事が予想されます。
Hubsではテナント設定が影響しないようにする機能があれば、Hubsの利便性向上に繋がるかと思われますので本機能の実装を希望します。4 votes -
Allow Box AI summaries to display by default when a file is opened or selected
It would be helpful if Box AI could automatically show the summary panel by default when a user selects a file or opens it in preview.
Currently, users must manually trigger the AI to see summaries.
For workflows involving many files, default visibility of summaries would improve usability and make Box AI insights more accessible and efficient.4 votes -
We would like to have a clear indication of whether a file request link has been issued for a folder.
Currently, it's not immediately clear whether a folder has a file request issued.
We would like to have an icon display, similar to a shared link icon, so that it is visually clear when viewing the folder that a file request link has been issued.
(In Japanese)
フォルダでファイルリクエストリンクが発行されているか分かるようにしたい現在、ファイルリクエストが発行されているフォルダかすぐにはわかりません。
フォルダを見た際に、ファイルリクエストリンクが発行されていることが視覚的にわかるよう、共有リンクのようなアイコン表示をできるようにしたいです。
15 votes -
More collaborative annotations
When editing drafts of print and digital materials, using comments/annotations in Box has been my team's go-to. However, I think the level of collaboration for that option could use improvement. It would be nice to be able to respond to directly under someone's comment so everyone knows what is being referred to, and I don't have to type "in response to {name's} note on {thing}..." to get my point across. It would also be nice to resolve/remove comments in some cases.
2 votes -
bulk update metadata
For metadata driven relays, it would useful from the list view to be able to multiselect files within a folder and set the meta value for a particular field for all the selected files.
3 votes -
Fix the known notification issue immediately
Promptly fix the known issues with notifications listed in the following article
Due to this bug, there have been frequent incidents of not receiving notifications when documents are uploaded by clients.
This has significantly damaged the reliability of Box at our company, and there are calls for its use to be discontinued.16 votes -
Allow customization of the “From” email address when sending notification emails via Box Relay instead of always using the default noreply@b
■ Need
Allow customization of the “From” email address when sending notification emails via Box Relay instead of always using the default noreply@box.com.■ Background & Issue
Currently, all notification emails sent by Box Relay originate from noreply@box.com. However, due to certain mail‐handling policies and recipient filtering rules, there is growing demand to send these Relay notifications from a company’s own domain/address.■ Example Use Case
In a process where the labor union reports employee work status to company officers using Relay notifications:
Issue: It is burdensome to ask all officers to adjust their mail filtering rules for noreply@box.com, leading to misrouting or unread notifications.
Proposed Solution: Enabling a custom sender address (e.g. alerts@yourcompany.com) would improve deliverability, reduce operational friction, and ensure timely receipt.
=============================
■ ニーズ
Box Relay で通知メールを送信する際、送信元メールアドレス（From）をデフォルトの noreply@box.com 以外に任意のドメイン／アドレスへ変更可能にしたい。■ 背景および課題
現在、Box Relay の通知メールは全て noreply@box.com から配信されています。しかし、特定のメール運用ルールや受信側のフィルタ設定の都合から、社内関係者や取引先への通知メールを自社ドメインのアドレスで送信したいという要望が増えています。■ ユースケース例
労働組合が役員宛に社員の労働状況を報告する業務において、Relay を使った通知を実施。
課題：受信側（役員全員）に対して自社ドメインのメール振り分け設定を依頼するハードルが高く、誤配や未読連絡が発生しやすい。
解決策：送信元アドレスを自社ドメイン（例：alerts@yourcompany.com）に変更できれば、受信側の信頼性と開封率が向上し、運用負荷も大幅に軽減できると期待。
■ Need
Allow customization of the “From” email address when sending notification emails via Box Relay instead of always using the default noreply@box.com.■ Background & Issue
Currently, all notification emails sent by Box Relay originate from noreply@box.com. However, due to certain mail‐handling policies and recipient filtering rules, there is growing demand to send these Relay notifications from a company’s own domain/address.■ Example Use Case
In a process where the labor union reports employee work status to company officers using Relay notifications:
Issue: It is burdensome to ask all officers to adjust their mail filtering rules for …
3 votes
- Don't see your idea?