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
10097 results found
-
Please extend the period for which activity data can be retrieved through Folder Insights.
Please extend the activity history retention period available in Folder Insights from 90 days to 180 days.
件名：フォルダインサイトで取得可能なアクティビティの期間を長くしてほしい
本文：フォルダインサイトで取得可能なアクティビティの期間を過去90日間から過去180日間にしてほしい1 vote -
4 votes
-
Use Radio Buttons for Single-Selection Folder Picker in Box AI Home
When picking a destination folder for files generated in Box AI Home, the folder picker uses checkboxes. Since users can pick only one folder, radio buttons would provide a clearer and more appropriate selection experience.
2 votes -
Signer to add fields to the signature request additionally to those added by sender
When using BoxSign, there are many cases where the requester will add additional fields.
In such a situation, there are times when signers themselves would like to add new fields, but they are unable to do so, and many voices are voicing concerns about the lack of convenience across the company.
We would like to request the implementation of this feature to improve convenience.BoxSignを使用する際に署名リクエスト者がフィールドを追加するケースが多々あります。
その状況下で署名者自身でも新たなフィールドを追加したい時がありますが、追加することできず社内全体で利便性に欠けている声が多く上がっています。
利便性向上のため本機能の実装をお願いしたいです。19 votes -
Granular Control of Invites
Currently, there is a single option in Enterprise Settings for Content & Sharing to restrict who can invite collaborators and add content to a Hub.
These should be individual settings: One for who can invite collaborators and one for who can add to a Hub.
Additionally, co-admins should be able to override this setting on folders.
1 vote -
Provide a Command/API to Log Out from Box Drive
Background:
There is currently no command or API available to log out from Box Drive programmatically.Request:
We would like to request the addition of a command or API that allows users to log out from Box Drive remotely. This would be particularly valuable for enterprise IT administrators who need to immediately terminate Box Drive sessions and clear local cache in the event of a device theft.Use Case:
- Remote logout of Box Drive when a PC is stolen, to prevent unauthorized access to corporate data stored in Box
- Clearing the local Box Drive cache remotely to ensure that no locally synced files remain accessible on the stolen deviceThank you for your consideration.
Background:
There is currently no command or API available to log out from Box Drive programmatically.Request:
We would like to request the addition of a command or API that allows users to log out from Box Drive remotely. This would be particularly valuable for enterprise IT administrators who need to immediately terminate Box Drive sessions and clear local cache in the event of a device theft.Use Case:
- Remote logout of Box Drive when a PC is stolen, to prevent unauthorized access to corporate data stored in Box
- Clearing the local Box Drive cache remotely to ensure…3 votes -
Load Images from a Document into AI Home
When converting document files to HTML format in AI Home, the images contained in the document files are not included in the AI’s response. We would like the images in the document files to be read and included in the AI Home response.
-in Japanese-
AI HomeでドキュメントファイルをHTML形式に変換するとき、ドキュメントファイル内にある画像はAIからの回答に反映されません。ドキュメントファイル内の画像も読み込んで、AI Homeからの回答に反映されるようにしてほしい。1 vote -
I want to sort folders and files by name when selecting them in BoxAutomate
Currently, when selecting folders and files in BoxAutomate, I can only sort by modification date. I would like to be able to sort by name.
-in Japanese-
BoxAutomateでフォルダ/ファイルを選択するとき、現在は更新日でしかソートできません。名前順でソートできるようにしてほしい。1 vote -
When deleting a branch in Box Automate, I want to keep the contents under it.
When you add a branch to a workflow in Box Automate, the workflows configured under that branch appear under “Branch 1,” but if you delete the branch, all of its contents are deleted as well. Since the contents under the branch appear under “Branch 1” when the branch is added, I would like the contents of “Branch 1” to remain even when the branch is deleted.
-in Japanese-
BoxAutomateでワークフローの途中に分岐を追加すると、配下に設定していたワークフローが"分岐岐路1"に表示されるが、分岐を削除すると配下の内容がすべて削除されてしまう。分岐を追加した際に配下の内容が"分岐岐路1"に表示されるのであれば、分岐を削除したときも"分岐岐路1"の内容だけでも残るようにしてほしい。1 vote -
form submission export
Box forms submissions should be available via export/report to show each submission and it's form responses, as well as info about the submission (who was it by, when, etc.). This would help with tracking specific forms and reflect functionality with similar products.
33 votes -
Leveraging AI for administrative tasks
I’d like to leverage AI to handle administrative tasks, such as identifying users who are barely using Box and removing them if they do not need a license. Right now, I can run a report, but it would be helpful if I could ask AI to show me all low-volume users. I’d also like to be able to look at high-volume users and activity that may indicate something beyond just doing their job.
3 votes -
Enable selecting files stored in Box directly in File Requests
Currently, file request links only allow you to upload files from local folders.
This is convenient if you use Box Drive, but users who rely solely on the browser have to download files from Box and then re-upload them via the file request link.I would like the file selection for file requests to allow choosing not only folders on the PC, but also files already stored in Box directly from the browser interface.
〈ファイルリクエストでBox内ファイルを直接選択可能にしたい〉
現在、ファイルリクエストリンクでは、ローカルフォルダ内のファイルしかアップロードできません。
Box Drive を利用している場合は便利ですが、ブラウザのみを利用するユーザーは、いったん Box からファイルをダウンロードしてから、ファイルリクエストリンクへ再度アップロードする必要があります。ファイルリクエストでアップロードするファイルの選択時に、PC上のフォルダだけでなく、ブラウザ画面から Box 内に保存されているファイルも直接選べるようにしてほしいです。
13 votes -
I want to open Box Notes in view-only mode
Currently, in Box Notes, it is possible to switch to view-only mode by changing "/notes/" in the URL to "/file/", but this method is not intuitive for users.
Because it is not easy to open notes in view-only mode, users often accidentally edit the notes. We would like to prevent this from happening.
We would like an option to select view-only mode when opening Box Notes from the beginning. It would also be more convenient if it were possible to bookmark Box Notes in view-only mode.
〈Box Notesの閲覧モードで開きたい〉
現在Box NotesではURLの/notes/を/file/に変換することで、閲覧モードにすることが可能ですが、ユーザーにとっては分かりにくいです。
簡単に閲覧モードで開けないことによって、ユーザーが誤って編集してしまうことが多く、これを防ぎたいと考えています。Box Notesを開くときに、最初から閲覧モードで開くために選択メニューを追加してほしいです。
また、閲覧モードにした状態のBox Notesをブックマークできるようになるとより便利です。22 votes -
Show in Box Drive or Reveal in Finder from Box Web
When I am looking at file in Box on a web browser, I want a button that takes me straight to the file in Box Drive/a macOS Finder window. We can already do that in the other direction (see attached, "View on Box.com"); it would be convenient to be able to do this in both directions. I don't know what the Windows equivalent is. Thanks for your consideration.
3 votes -
Enhancement of the content sorting feature in Hub
Currently, when placing multiple pieces of content in Hub, you can manually change their order, but it would be more convenient if sorting could be made easier.
We would like to be able to sort multiple pieces of content placed in Hub all at once, in ascending or descending order, by size, file name, update date, etc.
〈Hubのコンテンツ並び替えを強化してほしい〉
現在、Hubに複数コンテンツを配置するとき、手動で順番を入れかえることができますが、もっと簡単に並び替えができると便利です。Hubに配置している複数コンテンツに対しサイズやファイル名、更新日などを昇順/降順で一括で並び替えを行いたいです。
23 votes -
Per-Application Control for AI API
【Current Behavior】
The AI API setting in the Admin Console is currently a tenant-wide
toggle (ON/OFF). Once enabled, all custom applications (both
Server Authentication and OAuth 2.0 apps) under the enterprise
can invoke AI API endpoints. There is no mechanism to permit or
restrict AI API usage on a per-application basis.【Problem / Business Impact】
Because AI API consumption is billable, administrators cannot
selectively allow AI API access only for specific sanctioned
applications while blocking others. This creates the following
risks:- Uncontrolled billing exposure: Any application with AI API scope enabled can trigger consumption that the administrator did not sanction, leading to unexpected charges.
- Blocked adoption: To avoid unintended billing, customers are forced to keep AI API disabled at the tenant level, which prevents legitimate, pre-approved applications from leveraging AI API capabilities.
- Lack of governance: Administrators have no way to audit or enforce which applications are permitted to consume AI API resources, conflicting with standard enterprise governance requirements.
As a result, customers who want to pilot AI API with a limited
scope, or who want to separate billable vs. non-billable
application usage, cannot proceed.【Requested Feature】
Introduce per-application control for AI API access. Specifically:- In the Admin Console (or Developer Console application management), allow administrators to explicitly allow or deny AI API access for each individual custom application.
- The setting should override the tenant-wide toggle, or at minimum be evaluated in addition to it, so that administrators can maintain a default-deny posture while whitelisting specific applications.
- Provide visibility (e.g., via Admin Console or reporting) into which applications are currently permitted to consume AI API.
【現状の挙動】
管理コンソールのAI API設定は、テナント単位のON/OFFトグルのみ
提供されています。有効化すると、当該エンタープライズ配下の
全てのカスタムアプリケーション（Server Authentication および
OAuth 2.0 アプリケーションの双方）がAI APIエンドポイントを
呼び出し可能となります。アプリケーション単位でAI APIの
利用可否を制御する手段は存在しません。【課題・ビジネスインパクト】
AI APIは従量課金対象であるため、管理者が承認した特定の
アプリケーションのみにAI API利用を許可し、それ以外を制限する
という運用が現状では不可能です。これにより、以下のリスクが
発生しています。- 意図しない課金の発生：AI APIスコープが有効な全ての アプリケーションが課金対象の処理を実行可能であり、 管理者が認知しないAI API課金が発生する可能性がある。
- 利用機会の喪失：意図しない課金を回避するため、テナント 単位でAI APIをOFFのまま運用せざるを得ず、本来承認済みの アプリケーションにおいてもAI API機能を活用できない。
- ガバナンスの欠如：どのアプリケーションがAI APIを利用して いるかを管理者が制御・監査する手段がなく、エンタープライズ における標準的なガバナンス要件を満たせない。
結果として、限定的なスコープでAI APIを試行したい、あるいは
課金対象アプリと非対象アプリを分離して管理したい顧客が、
AI APIの採用判断に至れない状況が発生しています。【要望機能】
AI APIアクセスをアプリケーション単位で制御する機能の実装を
要望します。具体的には以下の通りです。・管理コンソール（または開発者コンソールのアプリケーション
管理画面）において、個別のカスタムアプリケーションごとに
AI APIの利用可否を明示的に許可／拒否できるようにする。
・当該設定はテナント単位のトグルを上書きする、もしくは
併せて評価される仕様とし、管理者がデフォルト拒否を維持
しつつ特定アプリケーションをホワイトリスト化できる運用を
可能とする。
・現時点でAI API利用が許可されているアプリケーションを
管理コンソールまたはレポート機能から可視化できるように
する。【Current Behavior】
The AI API setting in the Admin Console is currently a tenant-wide
toggle (ON/OFF). Once enabled, all custom applications (both
Server Authentication and OAuth 2.0 apps) under the enterprise
can invoke AI API endpoints. There is no mechanism to permit or
restrict AI API usage on a per-application basis.【Problem / Business Impact】
Because AI API consumption is billable, administrators cannot
selectively allow AI API access only for specific sanctioned
applications while blocking others. This creates the following
risks:- Uncontrolled billing exposure: Any application with AI API scope enabled can trigger consumption that the administrator did not sanction,…
4 votes -
content headers
When return JSON files in Box (e.g., via API), the content headers show "text/html" or "application/octet-stream" but should be "application/json". This is preventing automation with third party organizations I need to share data with because the content-type header is incorrect.
1 vote -
Add a "User must pick from the lowest available level" option when adding a Taxonomy to a Metadata Template
The existing options for "What level(s) can users select a value from?" have their use cases, but they do not cover all of the potential applications of the Taxonomy system.
Right now, when I add a taxonomy to a metadata template, the options are "Users must pick from the following level: [level]", and "Users can pick from any level in the list". What I would like to propose is a third option, "User must pick from the lowest available level".
The intent behind this would be to accommodate for Taxonomies where not every item has child items. In much of my experience there are many organizational structures where only some items have further children, and in those cases we would like to require the user to select the lowest option on a branch. For example, in the diagram below a user should be able to select Item 1 because it is the lowest option on that branch, but not Item 2 because there are children items with more specific information (Item 2.1 and Item 2.2).
The existing options for "What level(s) can users select a value from?" have their use cases, but they do not cover all of the potential applications of the Taxonomy system.
Right now, when I add a taxonomy to a metadata template, the options are "Users must pick from the following level: [level]", and "Users can pick from any level in the list". What I would like to propose is a third option, "User must pick from the lowest available level".
The intent behind this would be to accommodate for Taxonomies where not every item has child items. In much of…
1 vote -
Allow Conditional Splits in Box Automate to reliably check file extension or file type
It would be very useful for Box Automate Conditional Splits to have a reliable condition for a file's actual extension or file type.
For example, I need to route files automatically:
.wav / .aif → Audio folder
.mov / .mp4 → Video folder
Everything else → UnsortedI initially tried using the file name with conditions such as “contains .wav” or “contains .mp4,” but these conditions did not work reliably. I eventually had to look for specific words contained in our filenames instead, which is much less flexible and depends on users following a particular naming convention.
Ideally, Conditional Splits would provide properties such as:
File Extension
File Type / MIME Type
operators such as is, is one of, or ends withThis would make it possible to reliably route files based on their actual format without relying on filename conventions.
This would be especially useful inside For Each / Loop actions, where each current file could be routed according to its own file type.
It would be very useful for Box Automate Conditional Splits to have a reliable condition for a file's actual extension or file type.
For example, I need to route files automatically:
.wav / .aif → Audio folder
.mov / .mp4 → Video folder
Everything else → UnsortedI initially tried using the file name with conditions such as “contains .wav” or “contains .mp4,” but these conditions did not work reliably. I eventually had to look for specific words contained in our filenames instead, which is much less flexible and depends on users following a particular naming convention.
Ideally, Conditional Splits…
1 vote -
Allow users to duplicate Conditional Splits in Box Automate
It would be very helpful to have the ability to copy or duplicate a Conditional Split, including all of its branches and conditions.
When building multiple workflows with the same routing logic, users currently have to recreate every condition manually. For example, if a Conditional Split checks for .wav, .aif, .mov, .mp4, and other file types, the same logic has to be rebuilt from scratch in each workflow.
A “Duplicate Conditional Split” option would save a significant amount of time and reduce the chance of errors when recreating complex workflow logic.
Ideally, duplicating the split would preserve:
All branches
All conditions
AND/OR logic
Variable selections
Branch namesThis would be especially useful for workflows that use the same routing structure in different folders or projects.
It would be very helpful to have the ability to copy or duplicate a Conditional Split, including all of its branches and conditions.
When building multiple workflows with the same routing logic, users currently have to recreate every condition manually. For example, if a Conditional Split checks for .wav, .aif, .mov, .mp4, and other file types, the same logic has to be rebuilt from scratch in each workflow.
A “Duplicate Conditional Split” option would save a significant amount of time and reduce the chance of errors when recreating complex workflow logic.
Ideally, duplicating the split would preserve:
All branches
All…1 vote
- Don't see your idea?