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 ~
9835 results found
-
Ability to specify who will be notified when a password is changed.
As part of security operational reviews, administrators may occasionally check whether passwords have been changed multiple times within the same day, when necessary.
Currently, I believe password change notifications are sent to users with administrative privileges, including group administrators.
For operational reasons, we would like group administrators not to receive these notifications, so we would like to be able to optionally configure the recipients of password change notifications.セキュリティ面の運用見直しの一環で、管理者で同日内に何度もパスワード変更していないか等を必要な時にチェック行うことがあります。
現状、グループ管理者含めた管理者権限のあるユーザー宛にパスワード変更通知が届くと思います。
運用上の理由からグループ管理者がこれらの通知を受け取らないようにしたいため、任意でパスワード変更通知先を設定できるようにしたいです。13 votes -
AI-Powered Confirmation Before Adding Collaborators/Sending Links
I’d like Box to add an AI-powered confirmation step when users invite collaborators to a file or folder or send shared links to other users. The AI would quickly scan the content, detect PII or sensitive information, understand the context, and check whether the invited collaborator seems appropriate (e.g., external domain, personal email, unrelated teammate). If something looks unusual, Box would display a confirmation prompt asking the user to verify the invitation. This would help prevent accidental oversharing and reduce security risks caused by human error, while still keeping the collaboration workflow smooth.
15 votes -
I want to save Copilot for Microsoft 365-generated content directly to Box
Currently, when I use Copilot’s generative AI features, the only default save destination is OneDrive—Box isn’t even an option. For those of us who live and breathe Box it would be fantastic if we could save Copilot-generated content directly to Box and keep everything in one place.
Right now, every time Copilot asks, “Save to OneDrive?” I feel like saying, “Nice try, Copilot, but my heart belongs to Box!” Please help us Box fans avoid this daily heartbreak and make Box a first-class citizen for Copilot saves. Thank you!
〈Copilot for Microsoft 365で生成したコンテンツを直接Boxに保存したい〉
現在、Copilotで生成AI機能を利用し作成したコンテンツの保存先は、OneDriveがデフォルトとなっており、Boxを選択することができません。
Boxでコンテンツを一元管理するため、Copilotで生成したコンテンツの保存先にBoxを追加してほしいです。23 votes -
IP Address Restriction for Webapp and SELECTED API calls
We want to enable IP address restrictions only for the web app and selected applications.
Possible methods include submitting a list of client IDs exempt from restrictions during application, or providing a UI to specify an app list excluded from IP address restrictions.Currently, only the following two options are available.
- Enable only for Webapp
- Enable for Webapp and All API callsWhat we truly want is to apply IP address restrictions to the web app and BoxDrive. However, selecting “All APIs” renders nearly all other cloud-based integration apps unusable.
For example, losing integrations that significantly boost productivity—like Salesforce, Zoom, or Box connectors for Zapier and n8n—is a major issue. While we could ask providers for their IP addresses and allowlist them all, maintaining a list of potentially changing IP addresses is impossible.
Box itself recommends setting rules by domain in its firewall configuration support article, acknowledging IP addresses can change.The reason IP address restrictions via SSO cannot solve this is that they cannot prevent scenarios where employees authenticate internally, then take their device outside and access the company Box from an unspecified access point. Box's own IP address restrictions are powerful because they can prevent this, and it is essential to configure them to work alongside various integrations.
We want to enable IP address restrictions only for the web app and selected applications.
Possible methods include submitting a list of client IDs exempt from restrictions during application, or providing a UI to specify an app list excluded from IP address restrictions.Currently, only the following two options are available.
- Enable only for Webapp
- Enable for Webapp and All API callsWhat we truly want is to apply IP address restrictions to the web app and BoxDrive. However, selecting “All APIs” renders nearly all other cloud-based integration apps unusable.
For example, losing integrations that significantly boost productivity—like…21 votes -
Hubs Draft State/Autosave Feature
Implement a 'Draft' state for Hubs.
Example: A feature to have a Hubs 'auto save' option, once it's been generated. They have some users who may close out of the Hub before hitting 'save' and lose all of their work.
6 votes -
I would like Box Sign to have more flexible permission settings.
When Box Sign is enabled for a user, he/she can send sign requests, check the contents of requests shared with them, and view their inbox.
However, there are users for whom I do not want to allow sending sign requests, but I do want them to be able to check their inbox.For example, our executives who frequently approve or sign documents in Box Sign but do not need to send signature requests by themselves.
I believe it is a potential security risk to give users the authority to send signature requests even though they do not need it.Currently, Box Sign does not have a function to control external Sign sending. It would be great if we could have more granular control, such as allowing users to view the Sign inbox but not send requests.
After signing, users can download and review the signed document and signature log via the sign completion email.
But searching through the email inbox for them is inconvenient, so I would like to be able to complete everything within Box. So want to allow users to check the past signed document in Box via inbox of Box sign.I understand that with Shield access policies it is possible to restrict Box Sign request sending both internally and externally. However, since Box Sign may also be used for internal approval processes, I think making it completely impossible to send is too much.
When Box Sign is enabled for a user, he/she can send sign requests, check the contents of requests shared with them, and view their inbox.
However, there are users for whom I do not want to allow sending sign requests, but I do want them to be able to check their inbox.For example, our executives who frequently approve or sign documents in Box Sign but do not need to send signature requests by themselves.
I believe it is a potential security risk to give users the authority to send signature requests even though they do not need it.Currently,…
27 votes -
Regarding the time it takes for scheduled reports to be generated
Content: The Box support site mentions that report generation can take up to 12 hours.
Most reports are usually generated within a few minutes to a few tens of minutes, but scheduled reports often take about 12 hours to be output.
Although it is within the expected range, waiting half a day for the output affects business operations, so we request a functional improvement to shorten the time it takes for reports to be generated.(日本語)
件名：スケジュールされたレポートが出力されるまでの時間について
内容：Boxサポートサイトにレポートの生成には最大で12時間かかる場合があると記載されております。
ほどんどのレポートは数分から数十分程で出力されることが多いですが、スケジュールされたレポートの場合出力されるまでに12時間程かかることがとても多いです。
範囲内ですが、出力までに半日かかるのは業務に影響がある為、レポート出力されるまでの時間帯を短縮されるよう機能改善要望をします。28 votes -
Enable Box AI API for Specific Users or Groups
Currently, the Box AI API can only be enabled or disabled for "all users" at once. To allow custom applications to use Box AI, we have to enable the API for every user in our tenant.
However, it is difficult to estimate how many additional API Units we need to purchase, since we cannot predict how much each user will use the Box AI API. We are also concerned about users utilizing the AI API without proper authorization or oversight.
Just like Box AI for Notes and Box AI for Hubs, we would like to be able to enable or disable the Box AI API for specific users or groups. This would allow us to manage access more flexibly and securely. We would appreciate your consideration of this feature.
〈特定のユーザーまたはグループに対してBox AI APIを有効にする〉
現在、Box AI APIは「すべてのユーザー」に対して一括で有効／無効を設定する仕様になっています。そのため、カスタムアプリでBox AIを利用できるようにしたい場合、全ユーザーに対してAI APIを有効化する必要があります。しかし、どのユーザーがどれくらいBox AI APIを利用するか事前に把握できず、API Unitの追加購入がどれほど必要か判断できません。また、意図しないユーザーが勝手にBox AI APIを利用してしまうリスクもあります。
Box AI for NotesやBox AI for Hubsのように、Box AI APIも特定のユーザーやグループ単位で有効化／無効化できるようにしていただきたいです。
Currently, the Box AI API can only be enabled or disabled for "all users" at once. To allow custom applications to use Box AI, we have to enable the API for every user in our tenant.
However, it is difficult to estimate how many additional API Units we need to purchase, since we cannot predict how much each user will use the Box AI API. We are also concerned about users utilizing the AI API without proper authorization or oversight.
Just like Box AI for Notes and Box AI for Hubs, we would like to be able to enable or…
18 votes -
Box Drive Cloud Files: Selecting the Cache Storage
With the release of Box Drive Cloud Files, the specification for where the Box Drive cache is stored has been changed:
Traditional Box Drive: C:\Users<USERNAME>\AppData\Local\Box\Box\cache
Box Drive Cloud Files: Same folder as Box Drive
In our company, we have changed the Box Drive mount location and are operating with a reduced capacity on that mounted drive. Due to the above specification change, upload errors caused by insufficient space are occurring.
It is not realistically possible to re-image all corporate users’ PCs and change their storage capacities. A forced migration to Box Drive Cloud Files would therefore impact all users in our organization and could potentially lead to a decline in Box usage.
We strongly request the addition of a feature in Box Drive Cloud Files that allows us to select the cache storage location on the C drive, as was possible with the previous specification.
[Box Drive Cloud Files：キャッシュ保存先の選択]
Box Drive Cloud Filesのリリースにより、Box Driveのキャッシュの保存先が仕様変更されました。
・従来のBox Drive：C:\Users<USERNAME>\AppData\Local\Box\Box\cache
・Box Drive Cloud Files：Box Driveと同じフォルダ内社内ではBox Driveのマウント先を変更しており、マウント先の容量を少なくして運用しています。
上記の仕様変更の影響で、容量不足によるアップロードエラーが発生しています。
社内のユーザーすべてのPCで再キッティングと容量変更をすることは現実的に不可能となり、
Box Drive Cloud Filesへの強制移行は社内のすべてのユーザーに影響が出るため、Boxの利用率低下につながりかねません。従来の仕様と同じように、Box Drive Cloud Filesでもキャッシュの保存先をCドライブに選択できる機能の追加を強く要望します。
With the release of Box Drive Cloud Files, the specification for where the Box Drive cache is stored has been changed:
Traditional Box Drive: C:\Users<USERNAME>\AppData\Local\Box\Box\cache
Box Drive Cloud Files: Same folder as Box Drive
In our company, we have changed the Box Drive mount location and are operating with a reduced capacity on that mounted drive. Due to the above specification change, upload errors caused by insufficient space are occurring.
It is not realistically possible to re-image all corporate users’ PCs and change their storage capacities. A forced migration to Box Drive Cloud Files would therefore impact all users in…7 votes -
Enhance Metadata Input Fields in Box Forms (Multi-line Support & Character Limit)
[Background and Problem]
A customer is looking to migrate their FAQ management system from Microsoft Lists to Box. Their plan is to store the FAQ answers as metadata. However, we have received feedback that this is impractical because the metadata input field in Box Forms is restricted to a single line, making it difficult to enter long answers.Below are our feature improvement requests.
Multi-line Input Support
We request the ability to either adjust the height of the text input field for metadata, or to select the same format as the "Long Text" field for metadata fields.Increased Character Limit (Optional)
We also have a comment from the customer regarding the character limit for the metadata field in Forms:
"While 400 characters for Japanese is sufficient for basic needs, it would be even better if it were expanded to around 1,000 characters to allow for more detailed information and broaden its use."
＝＝＝＝＝＝＝＝＝
【背景と課題】
現在、Microsoft ListsでFAQ管理を行っている顧客がBoxへの移行を検討しています。 この際、FAQの回答をメタデータに格納する計画ですが、Box Formsのメタデータ入力欄が単一行であるため、「これでは長文の回答が入力できず、実用的ではない」というフィードバックを受けました。以下、機能改善のリクエストです。
入力フィールドの複数行化
メタデータ用のテキスト入力フィールドの高さを調整できる、または「ロングテキスト」フィールドと同じ形式をメタデータフィールドでも選択できるようにしてほしい。入力文字数の拡張 ※オプショナル
Formsのメタデータフィールドに入力できる文字数に関しても、顧客からコメントをいただいております。
「日本語で400文字あれば最低限の用途では問題ないが、より詳細な情報を記述できるよう、1000文字程度まで拡張されると活用の幅が広がり、さらに良い」
[Background and Problem]
A customer is looking to migrate their FAQ management system from Microsoft Lists to Box. Their plan is to store the FAQ answers as metadata. However, we have received feedback that this is impractical because the metadata input field in Box Forms is restricted to a single line, making it difficult to enter long answers.Below are our feature improvement requests.
Multi-line Input Support
We request the ability to either adjust the height of the text input field for metadata, or to select the same format as the "Long Text" field for metadata fields.Increased Character Limit…
21 votes -
Can we get the ability to set which agent is the default agent per hub?
It would be great if we could set which agent is the default for each hub. If left blank, then the default Box agent is selected. If we have an agent for each hub, our users may forget to switch the agent as they switch between hubs.
21 votes -
AI chat history should be saved
Any AI chat history, whether on a document(s) or in a Hub, is not saved in the same way other AI platforms do (ex, ChatGPT, Google Gemini, CoPilot, Perplexity, etc.). Retaining the chat history will improve efficiency in future conversations and improve personalization. This seems to be the biggest flaw/miss in the rollout of Box AI.
25 votes -
Request for a Report Listing Groups and Their Members
The [Group] report has been released, and it is now more convenient since we can check the list of groups.
However, it would be even more useful for inventory/cleanup purposes if we could see a list of the members belonging to each group.
We are currently recording group member lists manually, so we are looking forward to the release of a feature that allows us to export both the list of groups and their members all at once in a report.
[グループ] レポートがリリースされ、グループの一覧が確認できて便利になりました。
ですが、実際に各グループに所属しているメンバーの一覧が確認できるともっと棚卸に活用しやすいです。
レポートでグループ一覧及びその所属メンバーが一括で出力できる機能のリリースをお待ちしています。
現在は手作業でグループのメンバー一覧を記録しているため、レポートでグループ一覧及びその所属メンバーが一括で出力できる機能のリリースをお待ちしています。7 votes -
Allow a table in Box Forms
Allow a table in Box Forms to make entry easier for end users with copying and pasting
5 votes -
Function to disable the display of the login authentication screen for Box for Microsoft Office co-editing features on a per-user basis.
The following is a request regarding the seamless login feature.
https://support.box.com/hc/ja/articles/44224534926355To avoid displaying the login authentication screen, we understand that enabling the co-editing feature for only certain users in the tenant settings will resolve the issue.
However, if the number of users enabling or disabling the co-editing feature increases, managing user and group additions or removals through tenant settings each time becomes extremely cumbersome and impractical.
Implementing this feature enables end users to handle issues immediately on their own, reducing the burden on administrators.下記シームレスログイン機能に関する要望です。
https://support.box.com/hc/ja/articles/44224534926355ログイン認証画面を表示させないためには、テナント設定で一部のユーザーにのみ共同編集機能を有効にすれば回避できると認識しています。
但し、共同編集機能を有効/無効にするユーザーが増えたりした場合に都度テナント設定からの制限ではユーザーやグループの出し入れ等の操作が非常に手間となり現実的ではありません。
本機能を実装することでエンドユーザー自身で即時に対応できるようになり管理者の負担を減らすことができます。18 votes -
AI restriction in shield access policy
Shield Access Policy Settings to include the possibility to restrict the use of AI on content. That would prevent using AI on files containing PII, or other files including sensitive content in particular when using Box AI in Box Hubs.
15 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 -
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を使用する際に署名リクエスト者がフィールドを追加するケースが多々あります。
その状況下で署名者自身でも新たなフィールドを追加したい時がありますが、追加することできず社内全体で利便性に欠けている声が多く上がっています。
利便性向上のため本機能の実装をお願いしたいです。18 votes -
Reverse Image Search
Being able to upload an image and Box browser finding it (or similar) within a specified folder. Similar idea to Google lens.
66 votes -
Export Metadata from Apps Views
Export Metadata from Apps Views to CSV, XLSX, PDF
37 votes
- Don't see your idea?