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
-
Network Connectivity Insights in Admin Console
As an Admin, it would be useful to have network/connectivity insights available in the Admin Console for the identification of slow speeds / network issues across the tenant.
This would allow the proactive investigation into network issues such as slow uploads/downloads and office-specific issues.
3 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…9 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.
16 votes -
Multilingual support for BoxStatus
Hello Box Team,
I would like to suggest an improvement for the Box Status page.
As Box is a global service, it would be ideal if the Status page itself could support multiple languages and provide a more localized experience for customers around the world.
However, even if full localization is not currently planned, I would greatly appreciate an improvement to the way timestamps are displayed.
At present, incident updates and maintenance notifications are shown only in PDT/PST. For customers outside North America, this requires manual time conversion every time we review a status update. For example, users in Japan must convert PDT/PST to JST to understand when an incident actually occurred.
During active incidents, having to calculate time differences can make it harder to quickly assess the situation and communicate accurately with internal stakeholders.
It would be very helpful if Box Status could provide one or more of the following options:
- Display timestamps in the viewer's local browser time zone
- Allow users to select their preferred time zone
- Show UTC alongside PDT/PST
- Provide a time zone conversion feature or tooltip
While multilingual support for the entire Status page would be the ideal long-term solution, improving timestamp localization alone would already make a significant difference for international customers.
Thank you for your consideration.
Hello Box Team,
I would like to suggest an improvement for the Box Status page.
As Box is a global service, it would be ideal if the Status page itself could support multiple languages and provide a more localized experience for customers around the world.
However, even if full localization is not currently planned, I would greatly appreciate an improvement to the way timestamps are displayed.
At present, incident updates and maintenance notifications are shown only in PDT/PST. For customers outside North America, this requires manual time conversion every time we review a status update. For example, users in Japan…
3 votes -
Allow a table in Box Forms
Allow a table in Box Forms to make entry easier for end users with copying and pasting
7 votes -
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 -
Display the count of all workflows from "Relay" in the management console
It is assumed that administrators will quantitatively understand the usage of Relay within their company and develop operational policies and improvement plans. To do this, it is necessary to check the quantitative indicator of how much Box Relay is being used across the entire tenant.
By confirming the total number of workflows and understanding Relay usage, you can strengthen the promotion of business process automation within the company.管理者が社内のRelay利用状況を定量的に把握して運用方針や改善計画を立てることを想定しており、そのためには、テナント全体でBox Relayがどれだけ利用されているかの定量指標として確認する必要があります。
ワークフローの全件数を確認してRelayの利用状況を把握できることで、社内での業務プロセスの自動化推進強化に繋がります。16 votes -
Invite Box Groups from Another Tenant
Currently, when inviting users who belong to a different tenant to our tenant, each user must be invited individually. This process is time-consuming and inefficient.
We would like the ability to invite users from another tenant by group, rather than having to invite them one by one.（InJapanese）
別テナントからBoxグループを招待したい現状別テナントに所属しているユーザを弊社テナントへ招待する場合、1ユーザずつ招待する必要があり、対応に時間がかかり非効率です。
ユーザーを1人ずつ招待するのではなく、別テナントのユーザをグループ単位で招待できる機能を希望します。4 votes -
Increase the Maximum Number of Actions per Box Automate Workflow
{English}
We would like to request an increase in the maximum number of actions that can be executed within a single Box Automate workflow.Currently, the limit is 200 actions per workflow execution. However, based on real customer business requirements, some workflows are reaching this limit and cannot be fully implemented within the current constraints.
Increasing the limit to approximately 2,000 actions would address these use cases and enable customers to automate larger-scale business processes without requiring complex workarounds or workflow redesign.
This request was submitted based on customer feedback.
====
{Japanese}
Box Automateワークフローで一度に実行できるアクション数の上限拡張を希望します。現在、1回のワークフロー実行で利用できるアクション数は200に制限されています。しかし、実際の顧客業務要件を考慮すると、この上限に達してしまい、実現できないフローが存在します。
上限を2,000アクション程度まで拡張いただけると、このようなユースケースに対応でき、大規模な業務プロセスをワークアラウンドや複雑なフロー分割なしで実装できるようになります。
本要望は顧客からのフィードバックに基づくものです。
4 votes -
Box automate email notifications to non box emails
Box Automate should allow emails to be sent to addresses outside the company, especially when those addresses are pulled from a form field and used as a trigger value — allowing these workflows to reach external users
2 votes -
Allow separate collaboration and shared link controls for Box Automate and AI Home
Currently, the following Enterprise Setting controls both Box Automate workflow sharing and sharing of content located in AI Home session folders.
Enterprise Settings > Content & Sharing > Additional Collaboration Configuration
Our organization would like to apply different sharing policies to Box Automate and AI Home.
Box Automate
・Allow workflows to be shared between managed users within our organization
・Prevent workflows from being shared with external users
AI Home
・Prevent collaboration on content created or uploaded in AI Home session folders, including Notes containing saved AI responses, for both internal and external users
・Prevent shared links from being created for this contentHowever, the current configuration requires us to choose between the following options:
・When “Restrict all collaboration and shared links” is selected, sharing of AI Home-related content can be restricted for both internal and external users, but Box Automate workflows cannot be shared with managed users.
・When “Restrict external collaboration and public shared links” is selected, Box Automate workflows can be shared with managed users, but internal collaboration on AI Home-related content remains available.As a result, we cannot implement our desired configuration:
・Box Automate workflows can be shared between managed users.
・AI Home-related content cannot be shared with either internal or external users.Box Automate and AI Home have different purposes and sharing requirements. To enable organizations to use Box Automate collaboratively while maintaining strict controls over AI Home-related content, we request separate administrative settings for the following:
1.Sharing of Box Automate workflows
2.Collaboration on content and Notes located in AI Home session folders
3.Shared link creation for content and Notes located in AI Home session foldersOur desired configuration is:
・Box Automate: Allow workflow sharing with managed users
・Box Automate: Prevent workflow sharing with external users
・AI Home-related content: Prevent collaboration with all users, including managed users
・AI Home-related content: Prevent shared link creationSeparating these settings would allow organizations to securely collaborate on Box Automate workflows while continuing to restrict the sharing of AI Home-related content.
現在、Enterprise設定の以下の項目により、Box Automateのワークフロー共有と、AI Homeのセッションフォルダ配下にあるコンテンツの共有が同一の設定で制御されています。
Enterprise設定 ＞ コンテンツと共有 ＞ 追加のコラボレーション構成
当組織では、以下のように機能ごとに異なる共有制御を行いたいと考えています。
Box Automate
・管理対象ユーザー間でワークフローを共有可能としたい
・外部ユーザーへのワークフロー共有は許可しない
AI Home
・セッションフォルダ配下に作成またはアップロードされたコンテンツ、およびAI回答を保存したNotesについて、組織内外を問わずコラボレーションを制限したい
・同コンテンツについて、組織内外を問わず共有リンクの作成を制限したいしかし、現在の設定では、以下のいずれかを選択する必要があります。
・「すべてのコラボレーションと共有リンクを制限する」を選択すると、AI Home関連コンテンツの組織内外への共有を制限できますが、Box Automateのワークフローも管理対象ユーザーへ共有できません。
・「外部のコラボレーションと公開共有リンクを制限する」を選択すると、Box Automateのワークフローを管理対象ユーザーへ共有できますが、AI Home関連コンテンツについても組織内でのコラボレーションが可能となります。このため、当組織が希望する以下の状態を実現できません。
・Box Automateのワークフローは、管理対象ユーザー間で共有可能
・AI Home関連コンテンツは、組織内外を問わず共有不可Box AutomateとAI Homeでは、共有を許可する目的や対象が異なります。セキュリティを維持しながらBox Automateを組織内で活用できるよう、以下の設定を分離し、それぞれ個別に制御できるようにしていただきたいです。
- Box Automateのワークフロー共有に関する設定
- AI Homeのセッションフォルダ配下にあるコンテンツおよびNotesのコラボレーションに関する設定
- AI Homeのセッションフォルダ配下にあるコンテンツおよびNotesの共有リンクに関する設定
希望する設定例は以下のとおりです。
・Box Automate：管理対象ユーザーへの共有を許可
・Box Automate：外部ユーザーへの共有を禁止
・AI Home関連コンテンツ：管理対象ユーザーを含むすべてのユーザーへのコラボレーションを禁止
・AI Home関連コンテンツ：共有リンクの作成を禁止機能ごとに設定を分離することで、AI Home関連コンテンツに対する共有制限を維持しながら、Box Automateのワークフローを組織内で安全に共同利用できるよう、製品の改善を希望します。
Currently, the following Enterprise Setting controls both Box Automate workflow sharing and sharing of content located in AI Home session folders.
Enterprise Settings > Content & Sharing > Additional Collaboration Configuration
Our organization would like to apply different sharing policies to Box Automate and AI Home.
Box Automate
・Allow workflows to be shared between managed users within our organization
・Prevent workflows from being shared with external users
AI Home
・Prevent collaboration on content created or uploaded in AI Home session folders, including Notes containing saved AI responses, for both internal and external users
・Prevent shared links from being created for…2 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時間程かかることがとても多いです。
範囲内ですが、出力までに半日かかるのは業務に影響がある為、レポート出力されるまでの時間帯を短縮されるよう機能改善要望をします。30 votes -
I want to use the form trigger variables even outside of the [Request Signature] action.
Currently, when [Form Submitted] is used as the trigger in Box Automate, the [Request Signature] action can use variables from the form trigger. However, these variables cannot be used in other actions, such as [Task Action].
If form-trigger variables could be used in other actions as well, the range of automations that can be achieved with Box Automate would expand further, making it much more convenient. We kindly ask you to consider this enhancement.（日本語）
現在、Box Automateで [フォームを送信] をトリガーとした場合、[署名をリクエスト] アクションではフォームトリガーの変数を利用できます。しかし、[タスクアクション] など、その他のアクションではこれらの変数を利用できません。
他のアクションでもフォームトリガーの変数を利用できるようになると、Box Automateで実現できる自動化の幅がさらに広がり、大変便利になると考えています。ご検討をお願いいたします。2 votes -
Redesigning Box Drive to Be More Resilient Against Ransomware Attacks
Due to the nature of Box Drive, once a ransomware attack occurs, it is easy for the damage to spread laterally, and the reality is that some companies with specific security requirements are unable to adopt it.
Of course, certain countermeasures can be implemented through the adoption of Shield Pro, the purchase of third-party products, or restoration operations. However, all of these require additional costs, and companies are often unwilling to approve them.
Please reconsider the architecture so that the native Box Drive becomes more resilient against ransomware attacks.2 votes -
Admin controls for the Solutions menu
We would like Box Admins to have the ability to manage the Solutions menu in the Box web app.
The Solutions menu can create confusion because it allows end users to contact Box Consulting directly, which may bypass internal IT, helpdesk, procurement, or governance processes.
Please consider adding admin controls to either:
1) Enable or disable the Solutions menu for the enterprise
2) Replace the default Box Consulting contact path with an internal helpdesk or support contact, similar to the support contact email setting in Admin Console (Custom Settings)This would help to route end user inquiries through the right internal channels while still allowing access to Solutions where appropriate.
We would like Box Admins to have the ability to manage the Solutions menu in the Box web app.
The Solutions menu can create confusion because it allows end users to contact Box Consulting directly, which may bypass internal IT, helpdesk, procurement, or governance processes.
Please consider adding admin controls to either:
1) Enable or disable the Solutions menu for the enterprise
2) Replace the default Box Consulting contact path with an internal helpdesk or support contact, similar to the support contact email setting in Admin Console (Custom Settings)This would help to route end user inquiries through the right…
5 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.
19 votes -
Request for Hubs Version History Feature
Customer Pain Point & Concern:
Our customer is highly concerned about the risk of editors accidentally deleting or overwriting pages or sections within Hubs. Currently, there is no built-in version control or version history feature for Hubs (similar to what is available in Box Notes). As a workaround to prepare a backup plan, they are currently forced to take manual, regular backups by copying content, which has proven to be extremely tedious and inefficient.Requested Feature:
Version History for Hubs: A feature similar to Box Notes that allows users to view, restore, and revert to older versions of Hubs pages and sections.
This is a critical requirement for this large-scale customer to ensure secure content management and operational efficiency. We would highly appreciate it if this could be considered for the product roadmap.Thank you for your support!
Customer Pain Point & Concern:
Our customer is highly concerned about the risk of editors accidentally deleting or overwriting pages or sections within Hubs. Currently, there is no built-in version control or version history feature for Hubs (similar to what is available in Box Notes). As a workaround to prepare a backup plan, they are currently forced to take manual, regular backups by copying content, which has proven to be extremely tedious and inefficient.Requested Feature:
Version History for Hubs: A feature similar to Box Notes that allows users to view, restore, and revert to older versions of Hubs pages…
4 votes -
Allow admins to set AI Home as a homepage for all users
Allow administrators to configure AI Home as the default landing page for all users at enterprise level.
By making AI Home available immediately after users sign in, organizations can improve usability, increase AI feature adoption, and reduce the need for users to navigate to AI Home manually.
管理者が、ユーザーのサインイン後のデフォルトのランディングページとしてAI Homeをエンタープライズレベルで設定できるようにしてほしいです。
これにより、ユーザーはサインイン後すぐにAI Homeを利用できるため、ユーザーエクスペリエンスが向上します。また、ユーザーがAI Homeへ移動する手間がなくなり、AI機能をより簡単に見つけて活用できるようになるため、AI機能の利用促進にもつながります。
3 votes -
Show the date the classification label was applied for items uploaded by external users.
件名：外部ユーザーがアップロードしたアイテムに対して、分類ラベルが適用された日付を表示する
Regardless of whether the user checking the date the classification label was applied has the appropriate permissions, if the user who uploaded the item is an external user, the date the classification label was applied is not displayed.
It is inconvenient that this cannot be confirmed from the Box UI.
While it is possible to check the classification label application date in the User Activity Report, doing so requires an administrator or co-admin and can take time.
Please make the date the classification label was applied visible on the item details page for the relevant item.訳：
分類ラベルが適用された日を確認するユーザが適切な権限を付与されているか否かにかかわらず、アイテムをアップロードしたユーザが外部ユーザの場合、分類ラベルが適用された日付が表示されません。
Boxの画面で確認することができないのは不便です。
ユーザーアクティビティレポートで分類ラベルの適用日を確認することは可能ですが、管理者もしくは共同管理者にて対応する必要があり確認に時間がかかります。
対象アイテムの詳細画面で分類ラベルが適用された日付を確認できるように表示してください。件名：外部ユーザーがアップロードしたアイテムに対して、分類ラベルが適用された日付を表示する
Regardless of whether the user checking the date the classification label was applied has the appropriate permissions, if the user who uploaded the item is an external user, the date the classification label was applied is not displayed.
It is inconvenient that this cannot be confirmed from the Box UI.
While it is possible to check the classification label application date in the User Activity Report, doing so requires an administrator or co-admin and can take time.
Please make the date the classification label was applied visible on the item details page for the relevant item.訳：
分類ラベルが適用された日を確認するユーザが適切な権限を付与されているか否かにかかわらず、アイテムをアップロードしたユーザが外部ユーザの場合、分類ラベルが適用された日付が表示されません。
Boxの画面で確認することができないのは不便です。…4 votes -
Security & Governance Risk Caused by Retained Collaborations After Folder Moves
To help prevent unintended external access to internal-only content and strengthen data governance, we would like to request a feature that either controls collaboration inheritance when folders are moved or restricts folder moves within designated folder hierarchies.
In the current Box environment, my understanding is that when a folder is moved, any collaborations directly assigned to that folder are retained.
This behavior may lead to situations where folders with different access policies become mixed within the same hierarchy. For example, a folder collaborated with external users could be moved into a directory intended exclusively for internal use. As a result, external collaborators may continue to have access within an area that is expected to be restricted to internal users only. We believe this introduces a potential security and governance risk.
To help mitigate this risk, we would like to request consideration of one of the following options:
A configurable setting that automatically removes existing collaborations when a folder is moved.
A configurable setting that prevents folders and their entire descendant folder tree from being moved under specified parent folders.
More generally, administrative controls that allow organizations to enforce folder placement and collaboration governance policies when folder moves occur.We understand that similar requests have previously been discussed on Box Pulse and were not adopted, partly due to concerns regarding the complexity of collaboration changes and the volume of user notifications that could be generated when folders are moved.
However, we have not found any recent discussions addressing this concern. Given the increasing importance of data governance and the prevention of unintended external access, we would appreciate it if Box could reconsider this capability.
Additionally, we are not necessarily requesting these specific approaches. Any solution that achieves an equivalent level of risk mitigation would be equally appreciated.
Thank you for your consideration.
Japanese：
社内専用領域への意図しない外部アクセスを防止するため、フォルダ移動時のコラボレーション継承制御、または指定フォルダ配下への移動抑止機能の提供をご検討いただけないでしょうか。現在のBoxの仕様では、フォルダを移動した際、そのフォルダに直接付与されているコラボレーション設定は維持されると認識しています。
この挙動により、異なるアクセスルールを持つフォルダが同一のフォルダ階層内に混在する可能性があります。例えば、外部ユーザーがコラボレーションされているフォルダが、社内専用として運用されているディレクトリ配下へ移動された場合でも、その外部ユーザーのアクセス権は継続されます。その結果、本来は内部利用を想定している領域内に外部ユーザーがアクセス可能なフォルダが存在することになり、セキュリティおよびガバナンス上のリスクにつながると考えています。
このリスクを軽減するため、以下のいずれかの機能の実装をご検討いただけないでしょうか。
フォルダ移動時に既存のコラボレーションを自動的に削除する設定
指定した親フォルダ配下への移動を、対象フォルダおよびその配下階層を含めて制限する設定
より広義には、フォルダ移動時に組織のアクセス管理ポリシーやコラボレーション管理方針を強制できる管理者向けの制御機能過去にBox Pulseにおいて同様の要望が議論され、フォルダ移動に伴うコラボレーション変更処理や、それによって発生するユーザー通知の煩雑さなどを理由に採用されなかった経緯があることは認識しております。
しかしながら、近年ではデータガバナンスの重要性や、意図しない外部アクセスを防止する必要性が一層高まっています。また、直近では同様の要望を見受けなかったため、改めて本機能についてご検討いただければ幸いです。
また、上記の実装方式に限定するものではなく、同等のリスク低減効果を実現できる代替的な機能や制御手段についてもご検討いただけますと幸いです。
ご検討のほどよろしくお願いいたします。
To help prevent unintended external access to internal-only content and strengthen data governance, we would like to request a feature that either controls collaboration inheritance when folders are moved or restricts folder moves within designated folder hierarchies.
In the current Box environment, my understanding is that when a folder is moved, any collaborations directly assigned to that folder are retained.
This behavior may lead to situations where folders with different access policies become mixed within the same hierarchy. For example, a folder collaborated with external users could be moved into a directory intended exclusively for internal use. As a result,…
2 votes
- Don't see your idea?