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 ~
10051 results found
-
Update Box AI Studio configuration
Update AI Studio configuration in the admin console to be consistent with other AI features and features in Box to have the option for Enable for all, Disable for all, Enable for specific users, and disable for specific users
5 votes -
Large Folder Operation proactive notification and approval request
Provide a notification to a user should they be attempting to perform a Large Folder Operation and request admin approval for the action for an audit trail
1 vote -
Default agent for hub
I want to be able to create a custom agent and set it as the default agent for a hub. The idea is that if I want a hub to return a consistent result every time someone searches it, I can build an agent that provides that experience and have that agent automatically selected as the hub’s default. I do not want users to have to choose which agent to use.
1 vote -
Real-time visibility of whether a user has external collaborations ユーザーが外部コラボレーションを行っているかをリアルタイムで確認する機能
・Problem Statement / 課題
In the legacy Content Manager, an admin could see — in real time — that a managed user had a folder collaborated with an external party, along with the owner name. This was used as a pre-check before deleting/offboarding the user. The new Content Manager no longer surfaces external folders, so this real-time check is no longer possible through the UI.
レガシーContent Managerでは、管理者は対象ユーザーが外部とコラボレーションしているフォルダの存在と所有者名を、リアルタイムで確認できました。これはユーザーの削除/オフボーディング前の事前チェックとして使われていました。新Content Managerでは外部フォルダが表示されなくなったため、このリアルタイム確認がUI上で行えなくなっています。
Note: This request is not specifically about Content Manager. The legacy CM simply happened to be where this was possible. We are requesting the capability (real-time admin-side visibility of a user's external collaboration status), regardless of where in the product it is surfaced (Admin Console, a dedicated view, etc.).
補足：本要望はContent Managerに限定したものではありません。 レガシーCMがたまたまそれを実現できる場所だっただけです。要望しているのは「管理者側でユーザーの外部コラボレーション状況をリアルタイムに把握できる機能そのもの」であり、提供場所（Admin Console、専用ビュー等）は問いません。・Requirements (phased) / 要件（段階別）
The top priority is real-time confirmation of a user's external-collaboration status. Reporting (with up to 24h delay) does not satisfy this.
最優先事項は、ユーザーの外部コラボレーション状況をリアルタイムで確認できることです。レポート（最大24時間の遅延あり）ではこれを満たしません。Phase 1 (minimum acceptable): For a given managed user, show in real time whether they have any external-folder collaboration (yes/no, existence only).
Phase 2 (desired enhancement): Additionally show which external tenant(s) the user is collaborating with.
第一段階（最低限）： 対象ユーザーについて、外部フォルダコラボレーションの有無をリアルタイムに表示する（yes/no、存在のみ）。
第二段階（追加で望ましい）： 加えて、そのユーザーがどの外部テナントとコラボレーションしているかを表示する。・Current Workaround and Its Limitations / 現行のワークアラウンドとその限界
Affected customers are currently using the API (List items in folder against folderid: 0 / root) as a temporary workaround, expected to last only a few months. This is not a sustainable solution.
該当顧客は現在、API（List items in folder を folderid: 0／ルートに対して実行）を一時的なワークアラウンドとして使用していますが、これは数か月程度の暫定策と想定されています。持続可能な解決策ではありません。
Other admin-side options are insufficient for this use case:Reports: Content reports reflect data only up to ~24 hours before report run time (per Box Support, "Running Reports"). Content added in the last 24h can be missing → fails the real-time requirement.
Instant Login (Admin Console): Does not work for external folders, so it cannot be used to verify external collaboration.その他の管理者側の選択肢は、本ユースケースには不十分です：
レポート： コンテンツレポートはレポート実行時点の約24時間前までのデータしか反映しません（Box Support「Running Reports」より）。直近24時間に追加されたコンテンツが欠落しうるため、リアルタイム要件を満たしません。
Instant Login（Admin Console）： 外部フォルダには機能しないため、外部コラボレーションの確認には使えません。・Business Impact / ビジネスインパクト
In Japan, external-collaboration visibility directly affects user-offboarding and license-seat management for customers with record-retention obligations. Without a real-time check, IT cannot confidently delete users (compliance risk per customer), which ties up limited license seats and creates operational friction. This pattern is likely to recur across regulated/large enterprises in the Japanese market, so the capability has value beyond a single account.
日本では、外部コラボレーションの可視性が、記録保存義務を持つ顧客のユーザーオフボーディングおよびライセンスシート管理に直接影響します。リアルタイムの確認手段がないと、IT部門は確信を持ってユーザーを削除できず（顧客視点ではコンプライアンスリスク）、限られたライセンスシートが拘束され、運用上のフリクションが生じます。このパターンは日本市場の規制業界/大企業で繰り返し発生する可能性が高く、単一アカウントを超えた価値を持つ機能です。・Problem Statement / 課題
In the legacy Content Manager, an admin could see — in real time — that a managed user had a folder collaborated with an external party, along with the owner name. This was used as a pre-check before deleting/offboarding the user. The new Content Manager no longer surfaces external folders, so this real-time check is no longer possible through the UI.
レガシーContent Managerでは、管理者は対象ユーザーが外部とコラボレーションしているフォルダの存在と所有者名を、リアルタイムで確認できました。これはユーザーの削除/オフボーディング前の事前チェックとして使われていました。新Content Managerでは外部フォルダが表示されなくなったため、このリアルタイム確認がUI上で行えなくなっています。
Note: This request is not specifically about Content Manager. The legacy CM simply happened to be where this was possible. We are requesting the capability (real-time admin-side visibility of a user's external…1 vote -
Increased Character Limit - Box Forms
Please increase character limit to 1000 for Box Forms long text. We have questions in surveys that we are looking to send out via Box Forms that exceed the current, 100-character limit.
13 votes -
Delete User App Authorization
It would be nice to delete User App Authorization from the Admin Console. While Server App Authorization can be deleted by contacting support, User App Auth cannot.
Disabling auth is a good temporary workaround, but when there are many user app auths it can get cluttered and difficult to manage.
1 vote -
Report on file insights for all files
Currently you can only view file insights on an individual file, from the file details. I need the ability to view file insights for all files, in a single report.
Add a reporting feature in the admin console for file insights, where fields can be selected to be included in the report or not: People, Previews, Views, Downloads, Comments, Edits, Last Viewed Date, etc. And a File insights report is generated for ALL files in Box.
Having insights on individual files only makes it unfeasible to measure file utilization across the repo, at scale. How can we measure which files have high views and which are not being viewed at all, across the file corpus, without a report. Manually navigating to file insights for each individual file, exporting, then merging all reports, for hundreds or thousands of files, is not feasible. Please provide a report to deliver thisCurrently you can only view file insights on an individual file, from the file details. I need the ability to view file insights for all files, in a single report.
Add a reporting feature in the admin console for file insights, where fields can be selected to be included in the report or not: People, Previews, Views, Downloads, Comments, Edits, Last Viewed Date, etc. And a File insights report is generated for ALL files in Box.
Having insights on individual files only makes it unfeasible to measure file utilization across the repo, at scale. How can we measure which files…1 vote -
Restrict Hub Shared Link Creation to Admins Only
Many users can access a Hub via its shared link.
However, because there is currently no way to identify or control users who access via shared links, we would like to only invite required users directly to the Hub and eliminate the risk of anyone else viewing it.
Under the current behavior, even with the strictest settings, Hub co-owners can still create shared links.
It would be very helpful to have a stronger restriction so that even Hub co-owners cannot create shared links for Hubs, and only admins (or a similarly restricted role) can do so.
--
Hubは共有リンク経由で多くのユーザーがアクセスできます。
しかし、共有リンクからアクセスしたユーザーを確認し制御する方法が現状ないため、Hubには必要なユーザーを招待してそれ以外の人が見るリスクをなくしたいと考えています。
現状の仕様では、どんなに強い制限にしてもHubの共同所有者は共有リンクを発行できてしまいます。
Hubの共有リンクの発行は、Hubの共同所有者にもさせないように、さらに強い制限（管理者以外Hubの共有リンク発行不可）があると嬉しいです。Many users can access a Hub via its shared link.
However, because there is currently no way to identify or control users who access via shared links, we would like to only invite required users directly to the Hub and eliminate the risk of anyone else viewing it.
Under the current behavior, even with the strictest settings, Hub co-owners can still create shared links.
It would be very helpful to have a stronger restriction so that even Hub co-owners cannot create shared links for Hubs, and only admins (or a similarly restricted role) can do so.
--
Hubは共有リンク経由で多くのユーザーがアクセスできます。
しかし、共有リンクからアクセスしたユーザーを確認し制御する方法が現状ないため、Hubには必要なユーザーを招待してそれ以外の人が見るリスクをなくしたいと考えています。
現状の仕様では、どんなに強い制限にしてもHubの共同所有者は共有リンクを発行できてしまいます。…1 vote -
Batch Send Bulk Actions in Box Sign
After sending documents to multiple recipients using Batch Send, we’ve noticed that we are unable to perform actions such as editing, canceling, or sending reminders for the entire batch at once. Instead, these actions must be carried out individually for each recipient, which is quite time-consuming and inefficient.
Could you please add below features in batch send?
- Edit or cancel the entire batch in one go
- Send reminders to all recipients included in the batch simultaneously?
2 votes -
Delete or hide Source Systems without having to delete all associated jobs
The process to delete a Shuttle Windows source is to first manually locate and delete all completed Shuttle jobs that ran under that source, then delete the source server via the trash can button when selecting a source system via the new job wizard. Box Support have confirmed this experience.
Box Shuttle admins should be able to delete, or at least hide a source system, as part of clean-up activities, without having to manually export (if needed) and delete all previously configured jobs which is a frustrating user experience that introduces a lot of extra, hard-to-justify work on the admin side.
The process to delete a Shuttle Windows source is to first manually locate and delete all completed Shuttle jobs that ran under that source, then delete the source server via the trash can button when selecting a source system via the new job wizard. Box Support have confirmed this experience.
Box Shuttle admins should be able to delete, or at least hide a source system, as part of clean-up activities, without having to manually export (if needed) and delete all previously configured jobs which is a frustrating user experience that introduces a lot of extra, hard-to-justify work on the admin…
1 vote -
Improve Box Shuttle Filter to search by Source System
I'd like to be able to filter the Shuttle job list on the name of a source system.
This requirement is derived as a result of a product limitation where source systems cannot be deleted unless all completed jobs are deleted. Without this filter option, finding and deleting all jobs associated with a single source system is extremely laborious.
1 vote -
Request for improvement of the event where the cell date is different when previewing an Excel file
In Excel, if you enter a date in a cell with a custom format, a different date will be displayed when viewed with previewer permissions.
For example, if you enter "2026/1/1", if you check it with the previewer permission, it will be displayed as "2026/10/12".
This event is described below.Introducing Box Preview – Box Support
https://support.box.com/hc/en-us/articles/360044195013-Introducing-Box-Preview“Date values with the custom format "yyyy/m/d (aaa)" may show incorrect dates. This is due to a bug in the library that Box Content Preview has a dependency on. The workaround is to use a different format such as "yyyy/m/d (ddd)" or "yyyy/m/d".”
Editor and viewer permissions are displayed as they were entered, but previewer permissions are not the date entered.
It seems to be caused by a bug in the library that Box Content Preview depends on, but there is no way to check the correct date because the previewer permission does not allow downloading the file.
Therefore, we strongly request improvements.【In Japanese】
＜タイトル＞
Excelファイルをプレビューした際にセルの日付が異なる事象の改善要望
＜本文＞
Excelにおいて、表示形式がユーザー定義となっているセルに日付を入力すると、プレビューアー権限で表示した際に異なった日付が表示されます。
例えば、『2026/1/1』と入力したセルはプレビューアー権限で確認すると『2026/10/12』と表示されます。
この事象は下記に記載があります。Boxプレビューの概要 – Box Support
https://support.box.com/hc/ja/articles/360044195013-Box%E3%83%97%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC%E3%81%AE%E6%A6%82%E8%A6%81カスタム形式「yyyy/m/d (aaa)」を使用した日付の値は、誤った日付を示す場合があります。 これは、Box Content Previewが依存しているライブラリのバグが原因です。 回避策として、「yyyy/m/d (ddd)」、「yyyy/m/d」のような別の形式を使用します。
編集者権限やビューアー権限は入力時と同じものが表示されますが、プレビューアー権限では入力されている日付ではありません。
Box Content Previewが依存しているライブラリのバグが原因のようですが、プレビューアー権限はファイルのダウンロードができないため正しい日付を確認する方法がありません。
そのため、改善を強く要望いたします。In Excel, if you enter a date in a cell with a custom format, a different date will be displayed when viewed with previewer permissions.
For example, if you enter "2026/1/1", if you check it with the previewer permission, it will be displayed as "2026/10/12".
This event is described below.Introducing Box Preview – Box Support
https://support.box.com/hc/en-us/articles/360044195013-Introducing-Box-Preview“Date values with the custom format "yyyy/m/d (aaa)" may show incorrect dates. This is due to a bug in the library that Box Content Preview has a dependency on. The workaround is to use a different format such as "yyyy/m/d (ddd)" or "yyyy/m/d".”
…
5 votes -
Automatic Approval Removal When Deleting Apps
Since the maximum number of app approvals is limited to 100, periodic deletion of apps is required. However, at present we must request Box to perform these deletions.
We’d like both JWT and OAuth authentication to automatically revoke authorization when an app is deleted in the developer console.
If the service account owns any content, we would like a dialog similar to the one shown when deleting a user, allowing us to choose whether to move or delete the content.
アプリ承認の上限数が100であるため、定期的な削除が必要ですが、現状はBoxに依頼をする必要があります。
JWT 認証と OAuth認証の両方で、開発者コンソールでアプリを削除したときに自動的に承認を削除するようにして欲しいです。
もしサービスアカウントがコンテンツを持っている場合は、ユーザーの削除と同様のダイアログを表示してコンテンツを移動、削除どちらかを選択させたいです。4 votes -
Saved as Default: Search by Name
If you change your organization display to ‘By Name,’ it should remain consistent across all folders and be saved as the default. You can always switch back to ‘Last Updated’ if needed. Ideally, I’d like mine to stay set to ‘By Name,’ or have a navigation setting where you can choose your preferred organization as default.
1 vote -
Resize navigation pane
There should be a way to resize the width of the quick access navigation pane on left of screen. Most locations are cut off and unable to see what they actually are.
1 vote -
Regarding cross-file search within Box using the Box AI Agent for Copilot
We used Box AI Agent for Copilot to perform a cross-folder search across all folders in Box to which we have access (including subfolders) and to generate a ranking of the top file updaters. However, the search results were limited to files located directly under root-level folders, and files within subfolders were not included in the search scope. Since Copilot is able to perform cross-folder searches across all folders when searching SharePoint, we would appreciate it if a similar cross-folder search capability, including subfolders, could be implemented in Box AI Agent for Copilot.
1 vote -
Improvement of API performance and creation of guidelines for API usage
When utilizing Box’s API, if the amount of content per folder is enormous or the number of invitations to a folder is high, the processing speed drops significantly. As a result, it takes a long time to complete operations, which is quite frustrating.
We would like the API to deliver a more comfortable and speedy processing experience, so I hope you will improve the performance when using the API.
Additionally, there are currently no guidelines regarding API performance, so we have no choice but to verify performance degradation through testing.
This is hindering proactive API development. Please create clear guidelines that specify the details regarding API performance.
(In Japanese)
APIパフォーマンスの向上とAPI利用ガイドラインの作成：BoxのAPIを活用する際、1フォルダあたりのコンテンツが膨大だったり、フォルダへの招待数が多い場合、処理速度が大きく低下してしまい、処理が完了するまで多くの時間がかかり不満に思っています。
より快適でスピーディな処理をAPIで実現したいので、API利用時のパフォーマンス向上をしてほしいです。また、現時点ではAPIパフォーマンスに関するガイドラインが存在しないため、検証ベースでパフォーマンス低下の可否を確認するしかありません。
そのため、積極的なAPI開発の妨げになっています。 APIパフォーマンスに関する仕様を明確にまとめたガイドラインを作成してください。When utilizing Box’s API, if the amount of content per folder is enormous or the number of invitations to a folder is high, the processing speed drops significantly. As a result, it takes a long time to complete operations, which is quite frustrating.
We would like the API to deliver a more comfortable and speedy processing experience, so I hope you will improve the performance when using the API.
Additionally, there are currently no guidelines regarding API performance, so we have no choice but to verify performance degradation through testing.
This is hindering proactive API development. Please create clear guidelines…
20 votes -
Support MS Teams Integration on GCCH
Would like to see Box to able to integrate with Microsoft Teams on a GCH environment without having to sideload Box into the environment by a system integrator to get it to work.
1 vote -
Simply MFA enablement to provide a simple SINGLE notice to collaborators that MFA was enabled for company "X"
Enabling MFA for external collaborators caused mass emails to each external collaborator for every folder they are invited to, so a collaborator invited to 100 unique folders would be sent 100 emails, and would in turn click 'accept' in those emails, causing 100 emails to be send back to the content owner that it was accepted. This appears to happen even if the collaborator has already accessed the file (Triggered by enabling MFA).
Instead of emailing for every instance of an invited collaborator email address on every folder, instead prompt them to setup MFA only when they access a file or folder that requires MFA and only if they have not already setup MFA, or optionally, send only a SINGLE email to an external collaborator indicating that MFA had been enable by a specific company and if they wanted to access any of those files, the would need to setup MFA by accessing their Box account.
One email, rather than hundreds or thousands.
Enabling MFA for external collaborators caused mass emails to each external collaborator for every folder they are invited to, so a collaborator invited to 100 unique folders would be sent 100 emails, and would in turn click 'accept' in those emails, causing 100 emails to be send back to the content owner that it was accepted. This appears to happen even if the collaborator has already accessed the file (Triggered by enabling MFA).
Instead of emailing for every instance of an invited collaborator email address on every folder, instead prompt them to setup MFA only when they access a file…
1 vote -
File Outcome Actions for Form Uploaded Files
Include the ability to take file actions on files uploaded from a Box Form like you can in Relay. We have several Forms and Relays that not only take text/date/dropdown input but also have file upload fields and were hoping to move them to Automate so that we could take advantage of the additional features, but are unable to since there is no option to use an Outcome to take action upon the uploaded files.
1 vote
- Don't see your idea?