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
-
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…
5 votes -
Please add dark mode.
Please add dark mode.
3 votes -
Controlling the Visibility of External Collaboration Folders in Box Drive via Admin Settings
We would like administrators to be able to control the visibility of external folders in Box Drive via the Admin Console.
[Background]
When using Box Drive, the following security risks exist:
・Risk of data leakage due to user error: Files or folders may be accidentally dragged and dropped into external collaboration folders.
・Risk of ransomware spreading to external tenants: If a user falls victim to ransomware, the encryption attack may also affect external collaboration folders belonging to other companies.[Details]
We would like administrators to be able to control the visibility of external folders in Box Drive via the Admin Console. Rather than users configuring this themselves, we want administrators to be able to enforce the hiding of external collaboration folders through Admin settings.
・Control scope: the enterprise level and the group level.
・Target: External Folders
・Control details: Toggle display/hide on Box Drive (access remains available via the web app)
・Configuration permissions: Only administrators can change settings (end users cannot make changes)
・Scope of application: All users at once, or on a per-user or per-group basis[How it works when implemented]
・When an administrator enables “Hide External Folders,” only internal company folders will be displayed in the end user’s Box Drive.
・Access to external collaboration folders remains possible via the Box web app (ensuring business continuity).Please note that the content of this previously published article allows users to choose whether to show or hide external folders, which fails to eliminate security risks;
therefore, this request is different from that one.
https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/36186751-hide-folders-from-box-drive
Furthermore, it appears that the votes for the feature I am requesting in this request have likely been diverted to this existing article.following is Japanese
Box Driveにおける外部コラボレーションフォルダの表示/非表示を管理者制御する機能
[背景]
Box Drive利用時、以下のセキュリティリスクがある。
・誤操作による情報漏洩リスク： ファイルやフォルダを誤って外部コラボフォルダへドラッグ＆ドロップしてしまう
・ランサムウェア被害時の他社テナントへの波及リスク：ユーザーがランサムウェア被害にあった際に、外部コラボされている他社フォルダについても暗号化被害が出てしまう。[詳細]
Admin Consoleから、Box Driveに表示するフォルダの種別を制御できる。ユーザーでの操作ではなく、管理者側における設定で、外部コラボフォルダの非表示を強制することができる。
・制御単位：企業（Enterprise）単位、および、グループ単位で設定できる。
・制御対象：外部フォルダ
・制御内容：Box Drive上での表示・非表示の切り替え（一方、Webアプリ上では引き続きアクセス可能）
・設定権限：管理者のみが設定変更可能（エンドユーザーは変更不可）
・適用範囲：全ユーザー一括、または、ユーザー単位、グループ単位[実装された場合の動作イメージ]
・管理者が「外部フォルダ非表示」を有効化すると、エンドユーザーのBox Driveには自社内フォルダのみが表示される
・外部コラボフォルダへのアクセスはBox Webアプリ経由では引き続き可能（業務継続性を担保）We would like administrators to be able to control the visibility of external folders in Box Drive via the Admin Console.
[Background]
When using Box Drive, the following security risks exist:
・Risk of data leakage due to user error: Files or folders may be accidentally dragged and dropped into external collaboration folders.
・Risk of ransomware spreading to external tenants: If a user falls victim to ransomware, the encryption attack may also affect external collaboration folders belonging to other companies.[Details]
We would like administrators to be able to control the visibility of external folders in Box Drive via the Admin…5 votes -
Shield - Malicious Content alerting should provide greater details
Malicious Content alerts within Shield should provide more information on why a file is considered "malicious", to aid the process of sandboxing and investigation (such as threat type, family etc).
16 votes -
AI
AI studio governance - permissions and sandbox
As a confederation, we need to decentralize the creation and management of custom agents. This requires the following elements:
- Agent creation permission should not require co-admin permission (co-admin receive notifications not relevant to agent creators)
- Agent creators must have access to specific environments and not to all agents. This prevents accessing agents that are managed by others, and also allows creating test environments for experimentation
- Paid AI credits must be allocated to environments so environment admins have appropriate controls/limits over their consumption3 votes -
Do not display “Box Login” from “Required Recipient Authentication” for Enterprise and lower-tier plans
The "Box Login" option for additional recipient authentication in Box Sign is not available for Enterprise and lower-tier plans.
However, even on these plans, “Box Login” is displayed under Enterprise Settings > Box Sign > Required Recipient Authentication.Displaying an unavailable feature may cause confusion for administrators and users.
We request an improvement so that “Box Login” is not displayed for subscription plans at or below Enterprise.（日本語訳）
Enterprise以下の契約プランで”受信者の本人確認方法 (必須) > Boxへのログイン”を表示させないBox Signの追加の受信者認証で「Boxへのログイン」はEnterprise以下のプランでは利用できません。
しかし、Enterprise以下のプランでも、Enterprise設定>Box Sign >受信者の本人確認方法 (必須)に「Boxへのログイン」が表示されます。利用できない機能が表示されてしまうと管理者やユーザーへの混乱を招きます。
Enterprise以下の契約プランでは「Boxへのログイン」を表示しないよう改善を要望します。3 votes -
Apply Box Sign Templates Directly from the File System
The Box Sign template feature is very useful, but currently it is necessary to specify a template from the request creation screen and then replace the file.
We would like to be able to select a template when creating a Box Sign request directly from a file chosen in the file list, and create the request using that template.
Box Signのテンプレート機能は非常に便利ですが、リクエスト作成画面からテンプレートを指定しファイルを差し替える手順が必要です。
ファイル一覧からファイルを指定してBox Signを作成する際に、テンプレートを選択して作成できるようにしてほしい。2 votes -
We want to apply classification labels using Automate without granting Editors permission to change labels
In Relay, we had a workflow where users would manually trigger a workflow, assign an approval task, and upon approval, automatically change or assign a classification label. This was done to assign a label indicating that the content is ready for public release, enabling external sharing.
However, this cannot be achieved with Automate workflows. Upon checking the specifications, we found that unless the Admin Console allows Editors to modify classification labels, Automate workflows cannot assign labels. In our organization, we have only permitted Co-owners and Owners to change labels. If we allow Editors to change labels, general employees would be able to change labels freely, which we want to avoid.
Since this was achievable in Relay, please make Automate have the same specifications as Relay.Japanese follows
Relayを使い、ユーザーが手動でワークフローを起動し、承認タスクを付与し、承認されたら自動的に分類ラベルを変更する、または付与するという運用をしていた。承認を経て公開可能なラベルを付与して、社外公開を可能にするためです。しかし、Automateのワークフローではそれが実現できません。仕様を確認したところ、管理コンソールで、分類ラベルの変更をEditorに対して許可していないと、Automateのワークフローではラベルを付与できないとのこと。共同所有者＆所有者のみラベル変更を弊社では許可しています。編集者にラベル変更を許可すると、一般の社員も勝手にラベル変更ができてしまうため、それは行いたくないです。従来Relayで実現できていたので、AutomateもRelayと同じような仕様にしてくださいIn Relay, we had a workflow where users would manually trigger a workflow, assign an approval task, and upon approval, automatically change or assign a classification label. This was done to assign a label indicating that the content is ready for public release, enabling external sharing.
However, this cannot be achieved with Automate workflows. Upon checking the specifications, we found that unless the Admin Console allows Editors to modify classification labels, Automate workflows cannot assign labels. In our organization, we have only permitted Co-owners and Owners to change labels. If we allow Editors to change labels, general employees would be…
7 votes -
Sign Template Recovery
If a file used for a Sign template is accidentally deleted and restored, the sign template is not restored even though the file is. The sign template should be restored along with the file instead of having to redo the entire template.
4 votes -
Request to Add Genspark to Eco Solutions
We would like to request the addition of Genspark to the Eco Solutions portfolio.
6 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機能の利用促進にもつながります。
5 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…
31 votes -
Enable Device Trust for Co-Administrators as Well
Under the current specification, device trust is not applied to administrators and co-administrators to prevent them from being accidentally locked out of the management console.
Because co-administrators have higher privileges than regular users, they can freely access the console from personal PCs and other unmanaged devices, which raises concerns about the risk of information leakage.
From a security perspective, we would like to request the implementation of a feature that allows administrators to choose whether to apply device trust to co-administrators (“enable” or “disable”).件名：共同管理者に対してもデバイストラストを適用可能にする
内容：現状の仕様は、管理者・共同管理者は誤って管理コンソールからロックアウトされないために、デバイストラストが適用されません。
共同管理者は一般ユーザーより強い権限を持つため、私物PCなどから自由にアクセスできる状態となっており、情報漏えいリスクを懸念があります。
セキュリティの観点から、デバイストラストを共同管理者にも適用を"する" or "しない" の選択可能となる機能の実装を要望します。4 votes -
Request for Customizable Example Prompts in Box AI Agent for Microsoft 365 Copilot
In Box AI Agent for Microsoft 365 Copilot, example prompts are displayed below the chat input field.
This feature is useful, but we would like the ability to customize these examples.
When rolling out the feature to users, it would be even more convenient if we could display prompts configured by our own company so that users can make better use of the tool.
Box AI Agent for Microsoft 365 Copilotで、チャット欄の下にプロンプトの例が表示されています。
この部分は便利に活用できますが、この例をカスタマイズできるようにして欲しいです。
ユーザーに機能を展開する上で、ユーザーが活用しやすいように自社で設定したものを
表示できるとより便利です。9 votes -
Create variables within Box Automate
It would be amazing if we could create temporary variables within Box Automate.
Some examples include: be able to save the name of a file to send in a notification, save the number of times a loop ran outside of the loop, track how many times a loop back occurred, make a list of file names, etc.
3 votes -
Support mapping a single Microsoft Entra ID tenant to multiple Box enterprises (MPIP–Box Shield label integration)
Request: Allow a single Microsoft Entra ID tenant to be connected to multiple Box enterprises, so that MPIP sensitivity labels can be mapped to Box Shield classifications in each of them.
Background：Currently, the MPIP sensitivity label to Box Shield classification integration can only be established between one Microsoft Entra ID tenant and one Box enterprise (1:1).
However, many organizations operate a single Entra ID tenant while maintaining multiple separate Box enterprises — for example, group companies whose subsidiaries keep their content stores separated but share a single corporate identity provider and a single Purview governance policy.
Under the current 1:1 limitation, only one Box enterprise can inherit the organization's MPIP sensitivity labels. The remaining enterprises cannot consume them at all, so Shield classifications and policies must be maintained manually and separately, which undermines the value of centrally governed labeling.
This 1:N topology is already common with SSO — a single Entra ID tenant can serve as the IdP for multiple Box enterprises today, and many customers run exactly that configuration. Customers naturally expect the MPIP–Shield integration to follow the same model.
Request: Allow a single Microsoft Entra ID tenant to be connected to multiple Box enterprises, so that MPIP sensitivity labels can be mapped to Box Shield classifications in each of them.
Background：Currently, the MPIP sensitivity label to Box Shield classification integration can only be established between one Microsoft Entra ID tenant and one Box enterprise (1:1).
However, many organizations operate a single Entra ID tenant while maintaining multiple separate Box enterprises — for example, group companies whose subsidiaries keep their content stores separated but share a single corporate identity provider and a single Purview governance policy.
Under the current 1:1…
4 votes -
filter for inactive users
Enable filtering by Status on the Managed Users screen. When auditing user accounts it would be very helpful to filter to inactive users only and take appropriate action on those accounts. Currently you are required to scroll through the entire user list and pick out the inactive accounts. After you take action on an account, you have to start at the top of the page again when you want to find the next inactive user.
2 votes -
We Want to Easily Obtain the File ID
Currently, in order to obtain a file ID, we have to access the folder where the file is stored and open the file.
If there were a way to easily get the file ID from the screen without opening the file, it would reduce stress and improve work efficiency.
For example, if the file ID could be displayed in the file’s properties section, users would no longer need to open the file’s preview screen each time. Instead, by selecting the target file in the folder view, the file ID would be shown on the right side of the screen, allowing users to check the file ID much more efficiently.
--
現在、ファイルIDを取得するためには、フォルダにアクセスし、対象のファイルを開く必要があります。
ファイルを開かずとも画面上からファイルIDを簡単に取得する方法があれば、ストレスなく、作業効率も上がると思います。
例えば、ファイルのプロパティ欄へファイルIDを表示させることはできれば、フォルダビューで対象ファイルを選択することで画面の右側からファイルIDを確認できるでしょう。Currently, in order to obtain a file ID, we have to access the folder where the file is stored and open the file.
If there were a way to easily get the file ID from the screen without opening the file, it would reduce stress and improve work efficiency.
For example, if the file ID could be displayed in the file’s properties section, users would no longer need to open the file’s preview screen each time. Instead, by selecting the target file in the folder view, the file ID would be shown on the right side of the screen, allowing…
5 votes -
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.
4 votes -
Resolve the inconsistency in logo display between PC and mobile (responsive) views for the sidebar/header, and add a customization option fo
[Title]
Resolve the inconsistency in logo display between PC and mobile (responsive) views for the sidebar/header, and add a customization option for the mobile logo[Body]
We would like to request an improvement to the logo display specifications in Box, as there is currently an inconsistency between the PC and mobile (responsive) views.Current situation:
In the PC view, the Box logo is always fixed and displayed in the sidebar.
In the mobile (responsive) view, the logo shown in the header switches from the Box logo to the company’s custom logo, resulting in an inconsistency in display and preventing the delivery of a unified brand experience to users.Request:
Primary request
We would like the logo displayed in the header for mobile view to be configurable from the admin settings, so that it can be set to one of the following: [Box logo / company logo / hidden].Secondary request
If implementing the individual control described in the primary request is difficult, then at a minimum, we would like the display to be made consistent so that the same logo appears in both the PC view and the mobile view.Thank you for your consideration.
(In Japanese/日本語)
【タイトル】
PCとモバイル（レスポンシブ）表示におけるサイドバー/ヘッダーのロゴ表示の不整合の解消、およびモバイルロゴのカスタマイズ機能の追加【本文】
Boxのロゴ表示仕様について、PCとモバイル（レスポンシブ）で表示が異なる不整合があるため、機能改善を要望します。現状：
PC表示のサイドバーは一律でBoxロゴが固定表示されます。
モバイル（レスポンシブ）表示のヘッダーでは、Boxロゴから自社のカスタムロゴに表示が切り替わり、ユーザーに統一したブランド体験を提供できないという表示の不整合が起きています。要望：
・第1希望
モバイル表示のヘッダーに表示されるロゴを、管理画面の設定項目から【Boxロゴ / 自社ロゴ / 非表示】のいずれかに制御・変更できるようにしてほしい。・第2希望
第1希望の個別制御が難しい場合は、最低限PC表示とモバイル表示で同じロゴが表示されるよう、表示の整合性をとってほしい。よろしくお願いいたします。
[Title]
Resolve the inconsistency in logo display between PC and mobile (responsive) views for the sidebar/header, and add a customization option for the mobile logo[Body]
We would like to request an improvement to the logo display specifications in Box, as there is currently an inconsistency between the PC and mobile (responsive) views.Current situation:
In the PC view, the Box logo is always fixed and displayed in the sidebar.
In the mobile (responsive) view, the logo shown in the header switches from the Box logo to the company’s custom logo, resulting in an inconsistency in display and preventing the…4 votes
- Don't see your idea?