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 ~
9875 results found
-
Notification(s) for Box Notes
In the "Inbox" of Box Notes, any Note that gets updated by someone is conveniently displayed at the top. While this feature is helpful, it can also be bothersome because Notes that I no longer need to see keep appearing at the top of my screen every time someone opens them. Additionally, I’d like to be able to turn off unread notifications for Notes that aren’t relevant to me.
It would be helpful to have a setting that allows users to turn update/unread notifications ON or OFF for each Note individually.
Box Notesの「Inbox」で表示されるBox Notesは、誰かに更新されるたびに分かりやすく一番上に更新されたNoteが表示されます。この機能は便利ですが、もう見る必要がないNoteも誰かが開くたび、自分の画面のトップに表示され続けるため煩わしいです。また、未読通知も自分にとって必要ないものはOFFにしたいです。
ユーザー自身でNoteごとに更新通知/未読通知をON/OFFできる設定があると便利です。
15 votes -
Image Crop in Box Canvas
Enable image cropping in box canvas.
Be really useful when creating mood boards to crop the images and screenshots in box canvas rather than doing this before uploading
3 votes -
Request to Enable Start Time Configuration for Shared Link Validity
I would like the ability to configure the start date and time for a shared link’s validity period.
For example, a shared link would become active and accessible 60 minutes after it is created.
This feature would help prevent issues caused by misconfigured shared link permissions or sending a shared link to the wrong recipient.3 votes -
We would like to be able to check users’ departments from the UI:
Currently, you can view the usernames of users invited to a folder and the permissions granted to them within that folder.
However, there is no field in the account profile settings for entering a user’s department, so it cannot be easily checked.
While it is possible to work around this by adding the department to the username, this makes usernames longer and harder to read.
For example, I would like to be able to confirm a user’s department by displaying it in the same area as the permissions granted in the folder, or by showing the department when hovering the cursor over the username.--
UIからユーザーの所属部署を確認できるようにしたい:現在、フォルダに招待されたユーザーのユーザー名と、そのフォルダ内で付与された権限を確認できます。
しかし、アカウントプロファイル設定にはユーザーの所属部署を入力するフィールドがないため、簡単に確認できません。
ユーザー名に部署名を追加することで回避は可能ですが、これによりユーザー名が長くなり、読みづらくなります。例えば、フォルダ内で付与された権限と同じ領域に部署を表示する、またはユーザー名にカーソルを合わせた際に部署を表示するなどして、ユーザーの所属部署を確認できるようにしたいと考えています。
Currently, you can view the usernames of users invited to a folder and the permissions granted to them within that folder.
However, there is no field in the account profile settings for entering a user’s department, so it cannot be easily checked.
While it is possible to work around this by adding the department to the username, this makes usernames longer and harder to read.
For example, I would like to be able to confirm a user’s department by displaying it in the same area as the permissions granted in the folder, or by showing the department when hovering the…5 votes -
Disposition Report should be able to show files that were deleted in the past
It's important for GxP compliance and ease of auditing to know what files were disposed of in the past, or during a specific period, like in the last 30 days, last 6 months, etc.
Disposition report should be able to show previous deletions, not just upcoming deletions, and admins should be able to filter by retention policy, and date.
31 votesthe reporting on deleted content is under consideration but the requirement will be satisfied by different solution
-
ability to select a source folder and have the outcome automatically include all subfolders
In Box Automate, I created a custom extract agent and selected a source folder. However, after reviewing the run history, I noticed that only the files in the top-level source folder are processed, while files in subfolders are ignored. I would like the ability to select a source folder and have the agent automatically include all subfolders within it or give you the option to include them.
We currently have a couple scenarios where we would like to run extraction on existing files and folders in a parent folder retroactively, not just new uploads.
Thank you, and please let me know if you need any additional details.
In Box Automate, I created a custom extract agent and selected a source folder. However, after reviewing the run history, I noticed that only the files in the top-level source folder are processed, while files in subfolders are ignored. I would like the ability to select a source folder and have the agent automatically include all subfolders within it or give you the option to include them.
We currently have a couple scenarios where we would like to run extraction on existing files and folders in a parent folder retroactively, not just new uploads.
Thank you, and please let me…
2 votes -
Create More Filters for User Details Reporting
I am looking to have a User Details report automatically filter out platform users from managed users. Additionally, I'd like to see some other configurations of user outputs:
All Users (managed, unmanaged, external, and platform users)
Managed Users (managed users ONLY [without platform users])
Platform Users (only platform users)
Unmanaged Users (unmanaged users)
External Users (external users)
Managed and Unmanaged (managed [not platform] and unmanaged users)
Managed and Platform Users (managed users report as of today)2 votes -
Hover over file name
I see that a hover option to view whole file names was offered in 2022. This used to work fine for me but recently stopped. I can no longer hover to see whole file names and have to go back to opening the doc to view full names. Am I the only one having this problem or did it stop for everyone?
2 votes -
Show Folder size
Please add feature to show size of a folder not just number of files.
2 votes -
Please review the reordering of menu items and consider using a pop-up display.
Because “Hide this folder,” “Share,” and “Update folder” are arranged vertically, users are more likely to click the wrong option during operation.
In particular, a user trying to select “Share” may accidentally click “Hide,” causing the folder to disappear from the list and making it difficult to tell whether the folder was deleted by mistake or merely hidden.
In addition, because no confirmation pop-up (reconfirmation message) is shown when “Hide” is clicked, there is insufficient protection to prevent accidental actions.3 votes -
Add Box Hubs to mobile app
Can Box Hubs be added to the mobile app, or is that in the roadmap already?
35 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,…
2 votes -
Do not send notifications to group members when inviting a group to Hubs, as is the case when inviting a group to a folder.
Currently, when you invite a group to Box Hubs, all group members receive a notification.
However, if there are many group members, if all group members receive the email, it may violate some rules of Exchange Online.
Therefore, I would like to see an improvement so that notifications are not sent to group members when inviting a group to Hubs, as is the case when inviting a group to a folder.
ーーーーーー
＜フォルダへのグループ招待時のようにHubsへのグループ招待時もグループメンバーへの通知を送信しない＞
現在Box Hubsでグループを招待すると、グループメンバー全員に通知が届きます。
しかし、グループメンバーが多い場合、グループメンバー全員がメールを受信すると、受信するExchange Onlineの何らかのルールに抵触する可能性があります。
そのため、フォルダへのグループ招待時のように、Hubsへのグループ招待時もグループメンバーへの通知が送信されないように改善してほしいです。24 votesThank you for your request. We will take it into account but this feature is not planned yet. We may get back to it in the future.
-
Prevent LFO from occurring due to Box Relay
When running folder actions (copy/move/delete) in Relay workflows, if the source or destination folder contains a large volume of content, that folder may become subject to LFO, causing files to be locked and preventing other users from accessing them.
Therefore, when a user attempts to configure a flow with a folder that could be subject to LFO, we want to prevent unexpected LFO by clearly indicating on the flow creation screen that the workflow cannot be created due to LFO—for example, by displaying an error message or making the folder unselectable.
〈Box RelayによるLFOの発生防止〉
Relayのワークフローでフォルダアクション（コピー／移動／削除）を実行する際、コピー元またはコピー先のフォルダに大量のコンテンツがあると、そのフォルダがLFOの対象となり、ファイルがロックされて他のユーザーがアクセスできなくなる場合があります。そのため、LFOの対象になり得るフォルダをフローに設定しようとした時点で、フロー作成画面でエラーメッセージを表示する、または該当フォルダを選択不可にするなどの対策により、「LFOの影響で当該ワークフローは作成できない」ことを明確にし、想定外のLFO発生を防ぎたいと考えています。
8 votes -
Add an Option to Hide Global IP Address in Box Sign Signature Logs
Currently, when using Box Sign to request a signature, the signature log that can be obtained after completion displays the global IP address of the requester.
In our company, the global IP address is treated as confidential information and is considered highly sensitive according to our internal policies. Therefore, having this information visible in the signature log, which can be accessed by the recipient, is a significant concern for us.
For privacy protection and compliance with company regulations, we strongly request the implementation of a feature that prevents the global IP address from being recorded or displayed in Box Sign signature logs.
〈Box Sign署名ログでグローバルIPアドレスを非表示にするオプションを追加する〉
現在、Box Signで署名依頼を行うと、署名完了後に取得できる署名ログに署名依頼者のグローバルIPアドレスが表示されてしまいます。
グローバルIPアドレスは会社の規定として機密情報として扱う重要な情報です。
そのため、依頼先の相手が閲覧できる署名ログに表示されるのは非常に困ります。
プライバシー保護や会社規定への準拠のため、Box Signの署名ログにグローバルIPアドレスが記録・表示されないようにする機能を実装してほしいです。Currently, when using Box Sign to request a signature, the signature log that can be obtained after completion displays the global IP address of the requester.
In our company, the global IP address is treated as confidential information and is considered highly sensitive according to our internal policies. Therefore, having this information visible in the signature log, which can be accessed by the recipient, is a significant concern for us.
For privacy protection and compliance with company regulations, we strongly request the implementation of a feature that prevents the global IP address from being recorded or displayed in Box Sign…
9 votes -
Box Forms - Collaboration Feature needed
The ability to collaborate with another on a Box form, is a necessity. Additionally should be able collaborate with internal or external members of your organization.
10 votes -
AI chart interpretation, and visual element recognition
OCR capabilities, chart interpretation, and visual element recognition would allow us to combine image-derived data with text analysis for truly comprehensive insights on image
4 votes -
API Support for Managing Shared Links on Hubs
This request is to add Box API capabilities to view, create, update, and remove Shared Links for Hubs. Currently, there is no API support for managing Shared Links on Hubs, which limits automation and integration with enterprise workflows.
Enabling this functionality would allow for programmatic control of Hub sharing, improve governance, and support scalable content distribution strategies.
14 votes -
Bulk grant and remove permissions to Box Hub.
When BoxHubs is managed by an administrator, it is necessary to be able to grant or revoke access permissions to BoxHubs in bulk in order to manage users who can access BoxHubs.
The current functionality requires granting access permissions to a large number of BoxHubs, which would be too time-consuming to do manually.
For example, a tenant using BoxHubs manages around 80 to 100 BoxHubs,
It would take too much time and effort to do all of this manually, one by one.[日本語訳]
BoxHubsを管理者にて管理している場合に、BoxHubsへアクセスできるユーザー管理を行う目的で、
BoxHubsへのアクセス権限を一括で付与または権限の削除を行えるようにしたい。
現在の機能では多数のBoxHubsに対しアクセス権限の付与が必要になり、手作業で行うには工数がかかりすぎてしまう。
一例として、BoxHubsを活用しているテナントでは80～100程のBoxHubsを活用し管理を行っているため、
これらをすべて手動で一つ一つ手作業で行うには工数がかかりすぎる。19 votes -
Need to be able to circle options
We have many documents that require a selection to be made, rating service, etc. the text field, check box and radio options are not the best solution for our needs. I chatted with Emma at BOX support and she mentioned adding it here. Is there a way that we can have an additional feature added where, if someone was going to rate on a scale of 0-5, they could circle the option w/o having to download and manually act on the request?
3 votes
- Don't see your idea?