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 Box AI for Hubs to scope responses to the current Hub page or selected Hub pages
We would like Box AI for Hubs to support scoping AI responses not only to the entire Hub, but also to the current Hub page or selected Hub pages/subpages.
Box AI for Hubs is very useful because users can ask questions across the content in a Hub. However, when a Hub is organized into multiple pages by department, business process, project, topic, or chapter, users often want to ask questions only about the content on the page they are currently viewing.
Example use cases:
・Ask questions only against the “Travel Policy” page in an internal policy Hub
・Summarize only the “Security Training” page in an onboarding Hub
・Extract action items only from the files listed on a “Meeting Notes” page in a project Hub
・Generate an FAQ only from the files listed on a specific department page in an employee portal HubAlthough users can narrow the reference content by adding specific sources, it is not practical for end users to manually select each file or folder every time, especially when a Hub page already organizes the relevant files and folders for them. Since Hub pages and subpages are part of the Hub’s information architecture, it would be much more intuitive if that structure could also be used as the AI scope.
Requested behavior:
・When launching Box AI for Hubs, users can choose a scope such as “This page only,” “Selected pages,” or “Entire Hub”
・The current Hub page can be used as the AI context, including files, folders, links, and text blocks placed on that page
・Users can select multiple Hub pages/subpages as the AI context
・Citations and source references are limited to the selected page scope
・Existing Box permissions, Hub permissions, Shield classifications, and AI access controls continue to be fully respectedThis would make Box AI for Hubs much more useful for large knowledge portals. It would help users get more accurate and relevant answers by narrowing the AI context to the part of the Hub they are actually working with.
Box AI for HubsでHubページ単位に参照範囲を絞れるようにしてほしい
Box AI for Hubsにおいて、AIが参照する範囲をHub全体だけでなく、現在表示しているHubページ、または選択したHubページ/サブページ単位に絞り込めるようにしてほしいです。
現在、Box AI for HubsはHub内のコンテンツ全体を対象に質問できるため、情報収集には非常に有用です。一方で、Hubを部署別、業務別、プロジェクト別、章立て別にページ分割して運用する場合、ユーザーは「今見ているページに掲載されているコンテンツだけ」を前提にAIへ質問したいケースがあります。
たとえば、以下のようなユースケースがあります。
・社内規程Hubの中で、「旅費規程」ページだけを対象に質問したい
・研修Hubの中で、「第3章：セキュリティ研修」ページだけを要約したい
・プロジェクトHubの中で、「議事録」ページに掲載された資料だけからToDoを抽出したい
・部門ポータルHubの中で、特定部門ページに掲載されたファイルだけを対象にFAQを生成したい現在も@メンション等でコンテンツを指定して参照範囲を絞る方法はありますが、Hubページ上に複数のファイルやフォルダが整理されている場合、それらを毎回個別に指定するのはユーザーにとって手間がかかります。Hubの情報設計としてページやサブページを作成しているため、その構造をAIのスコープとして利用できると、より直感的で実務に即したAI活用が可能になります。
希望する挙動：
・Box AI for Hubs起動時に「このページのみ」「選択したページ」「Hub全体」などを選べる
・現在表示中のページに配置されたファイル、フォルダ、リンク、テキストブロックをAIの参照範囲にできる
・複数ページを選択して質問できる
・回答の引用元も、選択したページ配下のコンテンツに限定される
・既存のBox権限、Hub権限、Shield分類、AI利用制御は引き続き尊重されるこの機能により、Hubを大規模なナレッジポータルとして運用する場合でも、ユーザーは必要な範囲だけに絞って正確な回答を得やすくなります。特に、部門別・業務別・章立て別にHubを整理しているお客様にとって、Box AI for Hubsの回答精度と使いやすさが大きく向上すると考えます。
We would like Box AI for Hubs to support scoping AI responses not only to the entire Hub, but also to the current Hub page or selected Hub pages/subpages.
Box AI for Hubs is very useful because users can ask questions across the content in a Hub. However, when a Hub is organized into multiple pages by department, business process, project, topic, or chapter, users often want to ask questions only about the content on the page they are currently viewing.
Example use cases:
・Ask questions only against the “Travel Policy” page in an internal policy Hub
・Summarize only the…2 votes -
Request for Additional Configurable Shared Link Types
Currently, there are three types of Shared Links: [People with the link, people in your company, and people in this folder], but I’d like to see more granular options.
I’d like a feature that allows me to specify a domain for internal users so that only users from that domain can access the folder.タイトル：
設定可能な共有リンクの種類を増やしてほしい
本文：
現在の共有リンクは[リンクを知っている全員、会社のユーザー、このフォルダ内のユーザー] の3種類ですが、もっと細分化してほしいです。
社内ユーザーのドメインを指定し、そのドメインのみアクセス可能といった機能が欲しいです。1 vote -
Please allow us to change the owner of large folders (containing more than 3 million items)
When deleting an account belonging to a former employee, our standard procedure is to transfer ownership of the user’s content to another user before deleting the account.
However, if a user has a folder containing more than 3 million items, we are unable to delete that user’s account.
We would like to be able to transfer ownership of large folders containing more than 3 million items.タイトル：
300万コンテンツを超える大規模フォルダの所有者変更を可能にしてほしい
本文：
退職者のアカウントを削除する際に、所有していたコンテンツを他のユーザーに所有者変更した後にアカウントを削除する運用を行っています。
しかし、300万コンテンツを超えるフォルダを持っている場合、そのユーザーアカウントを削除できなくなります。
300万コンテンツを超える大規模フォルダの所有者変更を可能にしてほしいです。1 vote -
Rotate PDF files within Box Sign
There is currently a feature request that is labelled as on the roadmap to be able to rotate/zoom PDFs in Box Preview. We are requesting that this feature also be implemented in Box Sign as it is a pain to have to open PDF files in Acrobat to just rotate them, then save them, then upload to Box Sign.
6 votes -
Enable a Group Membership Admin role, which allows add/remove members of a Box group, without enabling modifications to the group.
Dear Box Product Owner,
This request proposes a new "Group Membership Admin" role within Box Groups to improve access control management, particularly for folders containing sensitive information, and to streamline compliance with regulatory requirements.Problem:
Currently, Box Groups are a valuable tool for managing entitlements to folders, especially those containing highly sensitive content. Integrating Box Groups with IAM tools like SailPoint enables efficient access provisioning, access reviews, and adherence to FFIEC and other regulatory standards. By managing access through groups, we can ensure that all collaborators on sensitive folders are added via controlled group memberships.However, the existing "Group Admin" role grants broad permissions that are not always necessary or desirable for folder owners who simply need to manage group membership. Folder owners require the ability to add and remove members from a group to grant/revoke access to the sensitive information within their folders. Granting folder owners full "Group Admin" rights exposes the group to unintended modifications, such as changes to the group's folder associations, which compromises the integrity of the group's defined access scope. Maintaining a clear and consistent understanding of which groups have access to which folders is crucial for effective access reviews and overall security governance.
Proposed Solution:
We propose introducing a new role, tentatively named "Group Membership Admin," with the following limited capabilities:
• Add Members to a Group: This function would allow the designated user to add new members to a specific Box Group.
• Remove Members from a Group: This function would allow the designated user to remove existing members from a specific Box Group.This new role would explicitly exclude the ability to:
• Modify the group's name or description.
• Associate the group with new folders.
• Remove the group's association with existing folders.
• Delete the group.
• Change other group settings beyond membership.Benefits:
• Enhanced Security and Compliance: By limiting the scope of permissions, the "Group Membership Admin" role minimizes the risk of unintended changes to group configurations and ensures that access controls remain aligned with security policies and regulatory requirements.
• Improved Access Management: Folder owners can efficiently manage access to sensitive content by controlling group membership directly, without requiring intervention from IT or security administrators.
• Clearer Entitlement Definitions: Maintaining the integrity of group-to-folder associations ensures that access reviews are accurate and reliable, providing a clear understanding of who has access to what.
• Streamlined Workflows: Delegating group membership management to folder owners empowers them to respond quickly to changing access needs, improving overall operational efficiency.In conclusion, the introduction of a "Group Membership Admin" role would significantly enhance our ability to manage access to sensitive information within Box, improve compliance with regulatory requirements, and streamline access management workflows. We believe this feature enhancement is crucial for maintaining the integrity and security of our Box environment.
Dear Box Product Owner,
This request proposes a new "Group Membership Admin" role within Box Groups to improve access control management, particularly for folders containing sensitive information, and to streamline compliance with regulatory requirements.Problem:
Currently, Box Groups are a valuable tool for managing entitlements to folders, especially those containing highly sensitive content. Integrating Box Groups with IAM tools like SailPoint enables efficient access provisioning, access reviews, and adherence to FFIEC and other regulatory standards. By managing access through groups, we can ensure that all collaborators on sensitive folders are added via controlled group memberships.However, the existing "Group Admin"…
14 votes -
Locking Box files or folders with Box shield so they cannot be deleted
I would like to use Box Shield to have certain standard folders in our folder structure locked so that any files inside can not be deleted
1 vote -
Request to add "Delete," "Move," and "Copy" activities to Folder Insights
Folder Insights is very useful for tracking how folders are being used. However, from an administrative perspective, it would be highly beneficial to monitor other types of activities as well.
Specifically, we would like to request that "Delete," "Move," and "Copy" be added to the activity metrics tracked in Folder Insights.
フォルダインサイトはフォルダの活用状況を確認するのに便利ですが、管理の側面で他のアクティビティも確認できるようにしてほしいです。
具体的には、アクティビティの項目に「削除」「移動」「コピー」も集計項目に加えてほしい。1 vote -
Once a task is completed, I want a completion notification to be sent to the relevant parties.
When a task is completed, I want a completion notification to be sent to the relevant parties.
If a task is assigned to multiple people, I want a completion notification to be sent to the other members assigned to the task once one of them marks it as complete.
タスクが完了したら、関係者に完了通知が配送されるようにしたい。
タスクを複数の担当者に割り当てた場合、1名がタスクを完了にしたら、タスクを割り当てられた他のメンバーに完了通知が配送されるようにしたい。
1 vote -
3 votes
-
Make folder retention policies non-removable (or always visible) to Editors
Today, Editors can remove the visible retention policy from a file or folder’s details panel, even though the underlying non-modifiable retention policy remains active in the background. This means that after an Editor removes the visible policy, there is no indication in the UI that retention still applies, which makes it appear as though the content is not under retention at all.
This behavior causes confusion for end users and admins, and makes it harder to support clear records management and compliance because enforced retention is not transparently visible in the interface.
Feature request
Please provide one or more of the following options:
-An option so Editors cannot remove the visible retention policy from files and folders (only Admins or users with Retention permissions can).
-If Editors can “remove” it, the UI should still clearly indicate that the item is under an enterprise retention policy (for example, a non-removable badge, icon, or message in the details panel).
-An admin-level configuration that controls whether retention policies are removable or always displayed when they apply.Implementing this would make retention behavior more transparent, reduce user confusion, and better support compliance needs.
Thank you.
Today, Editors can remove the visible retention policy from a file or folder’s details panel, even though the underlying non-modifiable retention policy remains active in the background. This means that after an Editor removes the visible policy, there is no indication in the UI that retention still applies, which makes it appear as though the content is not under retention at all.
This behavior causes confusion for end users and admins, and makes it harder to support clear records management and compliance because enforced retention is not transparently visible in the interface.
Feature request
Please provide one or more of…3 votes -
Ability to copy format / use format painter
It would be helpful to be able to use a format painter to copy a format and apply to other text within a boxnote
5 votes -
Make it possible to restrict access to subfolders. This is a highly irritating limitation as you end up with a million folders instead
manage security in folders and subfolders
1 vote -
customize forms
I would like to have more customizability options for Box File Request logo and banner.
We would like the ability to resize the square logo image field. We would also like to customize the top banner with a custom image, like the square logo image field.
2 votes -
File Request to allow global template
Allow File Request Request to suggest template from what has been used previously or templates used at parent or root directory level.
2 votes -
Add co-admin roles or templates
Add co-admin roles or templates. We have multiple groups who need co-admin access. Would be very helpful to have a role that is used to give permissions to an entire team. If a new permission is added, just update the main role\template and the entire team gets updated. Currently I have to go through each individual to change a permission for an entire team.
1 vote -
Restore Folder Insights graphs and activity metrics for folder owners and co-owners.
Folder Insights previously provided quick, at-a-glance visibility into who accessed or downloaded files. This information is valuable for teams responsible for monitoring confidential or sensitive content.
While similar information is available through reports, generating and downloading a report requires additional time and steps. Restoring Folder Insights would provide immediate visibility into file activity and help teams maintain appropriate oversight of sensitive information.
1 vote -
Support for PlantUML File Preview
I would like Box to support previewing PlantUML files directly within the web interface. This would improve usability by allowing users to view UML diagrams without downloading files or using external tools.
タイトル：
plantUMLのプレビューへの対応希望
本文：
BoxのWebインターフェース上でPlantUMLファイルを直接プレビューできるようにサポートしてほしいです。これにより、ファイルをダウンロードしたり外部ツールを使用したりすることなくUML図を確認できるようになり、利便性が向上します。1 vote -
Feature to Automatically Aggregate Folder Activity and File Statistics
I would like a feature that can automatically aggregate the number of views and downloads for specific files and folders in Box on a daily or monthly basis.
Currently, I have to manually open and review Folder Insights or Content Insights from the folder or file menu. I would like to streamline this process and improve efficiency by automating the collection and aggregation of these statistics.
タイトル：
フォルダのアクティビティやファイル統計情報を自動的に集計する機能
本文：1 vote -
Implementation of a Feature to Enable Preview and Co-Editing of Encrypted Files in Box
Files encrypted with solutions such as InfoCage FileShell cannot currently be previewed or collaboratively edited on the Box web interface. We would like these functionalities to be supported for encrypted files as well.
タイトル：
暗号化したファイルについてBox上でプレビュー・共同編集可能になる機能の実装
本文：
InfoCage FileShellなどで暗号化したファイルはBox Web上でプレビューや共同編集の機能を使用できないので、使用可能にしてほしい1 vote -
Developer Console: Add App Deletion Safeguards & Contextual Delete Separation to Prevent Accidental App Deletion
In the Box Developer Console (app.box.com/developers/console), deleting a custom application is an irreversible action that permanently revokes the Client ID and breaks all active client/vendor installations with no self-service or support recovery path.
Currently, two UX gaps lead to catastrophic accidental deletions:
Ambiguous Button Scope Across Tabs: The global "Delete App" option is present in the navigation/footer across individual configuration tabs (such as Integrations, Webhooks, Configuration). Developers frequently mistake "Delete" for deleting the specific integration or webhook they are currently configuring, rather than the entire Box application.
Insufficient Deletion Friction for High-Impact Action: Because app deletion is permanent and cannot be undone, standard one-click modal confirmations are easily bypassed under the mistaken assumption of scoped deletion.
Business Impact / Use Case:
When an enterprise production app (e.g., integrated across hundreds of enterprise users, external vendors, and printing partners) is accidentally deleted:All existing OAuth tokens and client installations immediately stop functioning.
The customer is forced to recreate a new app with a new Client ID/Secret, re-submit for publication review, re-allowlist across multiple external enterprises, and coordinate manual reinstallation across all vendors.
This results in critical business workflow downtime and high support escalation overhead.
Proposed Enhancements / Solutions:
Contextual UI Separation:Remove the global "Delete App" button from sub-feature tabs (Integrations, Webhooks, Authorization, etc.).
Move "Delete Application" into a dedicated, distinct Danger Zone under an Advanced Settings / General tab at the bottom of the page.
Clearly distinguish between "Remove Integration / Webhook" and "Delete Entire Application".
Multi-Step Deletion Safeguards:Explicit Name Confirmation: Require the developer to manually type the full Application Name or Client ID to enable the delete confirmation button.
Require "Disabled / Offline" State First: Require all integrations/endpoints to be toggled to Offline or Disabled before the app can be deleted.
Optional Email / Admin Verification: For published or enterprise-authorized apps, send a confirmation link to the app owner / primary admin before deletion is executed.
Soft-Delete / Grace Period (Optional/Future):Introduce a 7-day to 14-day "Soft Deleted / Deactivated" state where the app is disabled but can be restored with its original Client ID by the owner or Box Support before permanent purging.
In the Box Developer Console (app.box.com/developers/console), deleting a custom application is an irreversible action that permanently revokes the Client ID and breaks all active client/vendor installations with no self-service or support recovery path.
Currently, two UX gaps lead to catastrophic accidental deletions:
Ambiguous Button Scope Across Tabs: The global "Delete App" option is present in the navigation/footer across individual configuration tabs (such as Integrations, Webhooks, Configuration). Developers frequently mistake "Delete" for deleting the specific integration or webhook they are currently configuring, rather than the entire Box application.
Insufficient Deletion Friction for High-Impact Action: Because app deletion is permanent and cannot…1 vote
- Don't see your idea?