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
-
Allow for Duplication of Automate Workflows and Creation of Automate Templates
Currently, Relay has the ability to duplicate workflows, but Automate does not. We can also create templates for Relay workflows, but not for Automate. Automate should have the same capabilities.
8 votes -
Need for User Self-Removal from the Suppression List
Currently, only Box administrators or co-admins can remove email addresses that have been added to the Suppression List.
Furthermore, users cannot tell whether they are on the Suppression List and have no choice but to contact an administrator.
To reduce the burden on administrators, it is desirable that users be able to remove themselves from the Suppression List.
(In Japanese)
現在、Suppression List に登録されたメールアドレスの解除は、Box 管理者または共同管理者にしかできません。
また、ユーザーは自分が Suppression List の対象になっているか分からず、管理者に連絡するしかありません。
管理者の負担を減らすためには、ユーザー自身が Suppression List から自分の登録を解除できることが望ましいです。12 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 -
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 -
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 -
We'd like Box Agent to reference not only the files but also the text information within the Hub site
Before Box AI Home was released, when we asked the AI a question, it would reference not only the files linked within the Hub but also the text information on the site. However, after enabling AI Home and asking questions to the Box Agent in Hub, it now only references the content linked to the Hub. I would also like it to reference the text information (such as the descriptions written on the Hub site).
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 -
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 -
Enhanced Hide Function for Drive Folders/Files
Starting with Box Drive v2.48, it has become possible to hide folders and files. This is a very welcome feature.
However, when the “Show hidden files” setting is enabled in File Explorer, even if you use the folder hide function in Box Drive, the target folder is only grayed out on the screen and not completely hidden.
Users would be pleased if a more complete hide function were implemented.
エクスプローラーで「隠しファイル」の表示設定を行っているとき、Box Driveでフォルダ非表示機能を利用しても、画面上で対象のフォルダがグレーアウトするだけで完全には隠れないため、より完全な非表示機能が実装してほしい。
3 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 -
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 -
Audit log for changes to Hub settings.
I would like changes to the “Hubs Global Presets” or “Hub Settings” to be recorded in the security log.
Even if we apply restrictions on collaboration and shared links, there is currently no way to trace what happened when those restrictions are somehow removed. From a security and compliance standpoint, not being able to review an audit trail of these operations poses a significant risk.（日本語）
「Hubs全体のプリセット」もしくは「Hubsの設定」を変更した際、セキュリティログに記録してほしいです。
コラボレーションや共有リンクに制限をかけていても、何らかの理由でその制限が外れてしまった場合、現状では経緯を追跡する手段がありません。セキュリティやコンプライアンスの観点から、これらの操作履歴を確認できないことは、非常に大きなリスクです。8 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…
29 votes -
Metadata attribute update
As the increased use of metadata becomes popular, it would be great to have updates attributes in the metadata templates automatically update in the file requests/ forms or metadata options where they are being used.
Currently, in files requests and forms the metadata templates needs to be manually updated in the designated forms, which can be hard to track.
Request: metadata updates to attributes to be dynamically updated in their embedded/ functionality locations
12 votes -
Enable True/False Metadata Mapping for Checkboxes and Radio Buttons in Box Forms
Description:
Today in Box Forms, checkbox and radio button inputs are not natively mapped to Boolean metadata fields (true/false or yes/no), which limits the ability to trigger workflows or create metadata-driven views based on user responses.Feature Request:
Allow checkboxes and radio buttons in Box Forms to map directly to Boolean metadata fields:If a checkbox is checked, metadata should reflect “true”; if unchecked, “false.”
For yes/no radio button questions, allow mapping directly to true/false metadata fields.
Impact & Value:
Streamlines workflow automation with Box Relay (e.g., trigger based on form input).
Enables metadata-driven views (e.g., show only records where “Sensitive Data” = true).
Reduces reliance on workarounds to parse and apply Boolean logic from form responses.
Supports regulated and high-volume environments with binary decision routing needs.
Example Use Case:
In a procurement request form, checking a box labeled “Over $10,000?” would automatically set metadata to “true” and trigger an approval chain through Box Relay.Description:
Today in Box Forms, checkbox and radio button inputs are not natively mapped to Boolean metadata fields (true/false or yes/no), which limits the ability to trigger workflows or create metadata-driven views based on user responses.Feature Request:
Allow checkboxes and radio buttons in Box Forms to map directly to Boolean metadata fields:If a checkbox is checked, metadata should reflect “true”; if unchecked, “false.”
For yes/no radio button questions, allow mapping directly to true/false metadata fields.
Impact & Value:
Streamlines workflow automation with Box Relay (e.g., trigger based on form input).
Enables metadata-driven views (e.g., show only records where…
61 votes -
I want to be able to search for File requests from content manager and global search
Customer wants to be able to add "File request" as a search option in the global search and content manager as they sometimes get asked to look for folders where file requests were uploaded to.
3 votes -
"Select All" option in Map Data
In the Map Data screen when configuring a Box Shuttle Analysis job, it would be useful to have a "Select All" option rather than having to select one-by-one from the list.
3 votes -
Enforce Content Owner's Box AI Home Policy for External Collaborators (Prevent External Search on Owned Content)
Background & Current Behavior:
Our organization has enabled Box AI but intentionally disabled Box AI Home. However, we discovered that external collaborators who have Box AI Home enabled in their own tenant can still use Box AI Home to search for and access our content. This applies to our content they have explicit permissions for, as well as content they do not have permissions for but have a viewing history of and can preview via a shared link.Problem & Security Risk:
From a security, data privacy, and compliance perspective, if an organization restricts the use of Box AI Home, this policy must be strictly enforced on all owned content, regardless of the external collaborator's tenant settings. The current behavior creates a critical loophole where our confidential data is processed and exposed through an AI interface that we have deliberately disabled as an organization.We acknowledge that the risk of confidential data exposure via Box AI Home theoretically would not exist assuming access control and permission management are absolutely perfect. However, in reality, permission management can sometimes be imperfect or delayed. We are requesting this restriction as an essential fail-safe (defense-in-depth) to prevent unintended data exposure in such realistic scenarios.
Feature Request:
We strongly request a feature—either at the tenant level or the folder level—that prevents external users from discovering or searching our owned content via Box AI Home. The content owner's AI policy must always take precedence over the collaborator's tenant settings to ensure complete data governance and serve as a crucial safety net for our organization.背景と現在の挙動：
当組織では、Box AIを有効にする一方で、Box AI Homeは意図的に無効化しています。しかし、自身のテナントでBox AI Homeを有効にしている外部コラボレーターは、Box AI Homeを使用して当社のコンテンツを検索し、アクセスできてしまうことが判明しました。これには、彼らが明示的な権限を持つ当社のコンテンツだけでなく、権限がなくとも過去に閲覧履歴があり、共有リンクでプレビュー可能なコンテンツも含まれます。課題とセキュリティリスク：
セキュリティ、データプライバシー、コンプライアンスの観点から、組織がBox AI Homeの利用を制限している場合、そのポリシーは外部コラボレーター側のテナント設定に関わらず、自社が所有するすべてのコンテンツに対して強制的に適用されるべきです。現在の挙動は、当社が組織として意図的に無効化しているAIインターフェース経由で、当社の機密データが処理・露出されてしまうという重大な抜け穴を生み出しています。AI Homeによる機密データの露出は、もともとの権限管理が完璧に行われている前提であれば理論上存在しないリスクであることは理解しています。しかしながら、現実の運用において権限管理が完全に漏れなく行われないケースは起こり得ます。私たちは、そうした現実的なシナリオにおける予期せぬデータ露出を防ぐための、不可欠なフェイルセーフ（多層防御の予防線）としてこの制限を要望しています。
機能リクエスト：
自社が所有するコンテンツに対して、外部ユーザーがBox AI Home経由で検索や発見をすることを防ぐ機能（テナントレベルまたはフォルダレベルの設定）を強く要望します。完全なデータガバナンスを確保し、組織の重要なセーフティネットとして機能させるために、コンテンツ所有者のAIポリシーがコラボレーターのテナント設定よりも常に優先される必要があります。Background & Current Behavior:
Our organization has enabled Box AI but intentionally disabled Box AI Home. However, we discovered that external collaborators who have Box AI Home enabled in their own tenant can still use Box AI Home to search for and access our content. This applies to our content they have explicit permissions for, as well as content they do not have permissions for but have a viewing history of and can preview via a shared link.Problem & Security Risk:
From a security, data privacy, and compliance perspective, if an organization restricts the use of Box AI Home,…3 votes
- Don't see your idea?