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
-
Automate: Request for Copy Feature for Approval Tasks
When defining Outcomes in Box Automate, the copy function is useful for cases where similar outcomes need to be set up repeatedly within the same flow, for example when creating a flow that requires multiple rounds of approval, where there is likely to be considerable demand for this capability.
Currently, however, this option is not available for Approval Tasks, as the copy icon does not appear when the outcome type is an Approval Task.
It would be helpful if Approval Tasks could also support the same copy functionality as other outcome types.(日本語)
Box Automateで結果を定義する際、同じフロー内で類似の結果を繰り返し設定する必要がある場合にコピー機能が便利です。例えば、複数回の承認が必要なフローを作成する場合、この機能の需要はかなり高いと考えられます。しかし現時点では、結果が承認タスクの場合はコピーアイコンが表示されないため、コピー機能を利用できません。
承認タスクについてもほかの結果と同様にコピー機能がサポートされると、とても助かります。
6 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…
6 votes -
Dynamic approving
Customer has a workflow which requires 2 out of 3 stakeholders to approve a document before it progresses. Asking the product team to provide dynamic approval so, for example, when one stakeholder approves a document, the the workflow progresses to require one of the remaining assignees to approve the document.
6 votes -
Allow retention policies to dispose content to Trash, not only permanently delete
Please allow a retention policy disposition of Delete (move to Trash), not only Permanently delete.
Background: With permanent deletion, content can be removed without anyone noticing, so we may not detect that it has been deleted.
3 votes -
Add VTT (transcript) file support to Box AI
Request:
Enable Box AI (Ask, Extract, Hubs, Agents) to ingest and analyze VTT (.vtt / WebVTT) files.Reasons:
VTT is the default transcript format for Zoom and Microsoft Teams, so a massive volume of VTT files is already stored in Box.
Transcripts contain high-value data (decisions, action items, customer voice, Q&A), but Box AI currently cannot read them at all.
Leaving this data unusable is a major lost opportunity for Box AI's value.Nice to have:
VTT preview support in Box Preview.
要望：
Box AI（Ask / Extract / Hubs / Agents）で VTT（.vtt / WebVTT）ファイルを取り込み・分析できるようにしてほしい。理由：
VTT は Zoom と Microsoft Teams のデフォルトのトランスクリプト形式であり、すでに大量の VTT ファイルが Box に蓄積されている。
トランスクリプトには意思決定・アクションアイテム・顧客の声・Q&A など価値の高い情報が含まれるが、現状 Box AI は一切読み込めない。
このデータを活用できないことは、Box AI の価値にとって大きな機会損失。あると嬉しい：
Box Preview での VTT 表示対応。Request:
Enable Box AI (Ask, Extract, Hubs, Agents) to ingest and analyze VTT (.vtt / WebVTT) files.Reasons:
VTT is the default transcript format for Zoom and Microsoft Teams, so a massive volume of VTT files is already stored in Box.
Transcripts contain high-value data (decisions, action items, customer voice, Q&A), but Box AI currently cannot read them at all.
Leaving this data unusable is a major lost opportunity for Box AI's value.Nice to have:
VTT preview support in Box Preview.
要望：
Box AI（Ask / Extract / Hubs / Agents）で VTT（.vtt / WebVTT）ファイルを取り込み・分析できるようにしてほしい。理由：
VTT は Zoom と Microsoft…5 votes -
Request for Improvement of the “People with the Link” Feature in Box
Request for Improvement of the “People with the Link” Feature in Box
We would like to request the following improvements to the “People with the link” option within Box’s Share Link feature, which is used to grant viewing or downloading access to folders or files for organisations or email addresses that do not have a Box account or existing folder permissions.
At present, requiring the link creator to manually set a password is rather cumbersome, and as a result, many users choose not to do so. Since there is no enforcement mechanism, some organisations restrict or even prohibit the use of this feature due to concerns over security management.
Furthermore, when compared with other file transfer services, the People with the link option provides somewhat limited functionality for securely sharing files with users or organisations that do not have a Box subscription. Consequently, some organisations opt to use existing external file transfer services instead of relying on the People with the link feature.
For these reasons, we would like to propose the implementation of the following enhancements.
- Enable password protection for the “People with the link” option. ※No further action should be required from the user.
- The generated “People with the link” URL can then be sent to the recipient via email or other means.
- When the recipient accesses the link, they are prompted to enter their email address in order to receive the password.
- The recipient receives the password notification via email and enters it on the access page.
- After entering the password, the recipient is granted permission to view and download the file.
By providing the above functionality, it would become possible—through administrative console activity logs—to identify, via email address, who accessed or downloaded files shared through the “People with the link” option and when.
This would enable organisations to verify that files have not been downloaded by unintended recipients, thereby strengthening overall information security management.
＜日本語＞
共有リンク機能にて「リンクを知っている全員」を設定し、パスワード設定を有効化した場合の機能改善を提案します。本来、「リンクを知っている全員」はBoxのアカウント持たない組織または人達にファイル送信する際に利用され、ファイル転送サービスの代替方法として活用を提案するものです。
しかしながら、「リンクを知っている全員」のパスワード設定は、共有リンクを作成した本人がパスワードを任意で設定する必要がありとても操作が煩雑です。
また、パスワードを設定したとしても別のメールで連絡をしなくてはなりません。
更に、送信した相手が本当に参照したのか、ダウンロードをしたのか知る方法もないためセキュリティの観点から、ファイル転送サービスを利用した方が安全にファイル送信できると判断し、利用を禁止している組織も多いはずです。そのため以下のような機能を提供するのが良いと考えています。
１．「リンクを知っている全員」を設定。パスワードの有効化を設定。
※ユーザーの操作はここまで２．上記で生成された共有リンクのURLをメール等で相手に送信
３．メール受信者は、共有リンクにアクセスするとパスワードを送信するためメールアドレスの入力が求められる。
４．メールアドレスを入力すると、入力したメールアドレスにパスワードが送信される。
５．受信したパスワードを入力するとファイルを参照またはダウンロードできるようになる。
上記の機能を提供することで、「リンクで知っている全員」でファイルを送信したとしても、入力されたメールアドレスをログで確認できるようにすることで、いつ誰がファイルを参照しダウンロードしたのか管理コンソールのレポート機能で確認できるようにすることで、意図しない相手がダウンロードしていないかチェックすることも可能となり、組織全体のセキュリティ強化に繋がると考えます。
Request for Improvement of the “People with the Link” Feature in Box
We would like to request the following improvements to the “People with the link” option within Box’s Share Link feature, which is used to grant viewing or downloading access to folders or files for organisations or email addresses that do not have a Box account or existing folder permissions.
At present, requiring the link creator to manually set a password is rather cumbersome, and as a result, many users choose not to do so. Since there is no enforcement mechanism, some organisations restrict or even prohibit the use…
22 votes -
Request for Flexible Report Output Naming and Folder Configuration
We would like to request enhanced flexibility in report output management.
Specifically:1.The ability to assign arbitrary names to report output files
2.Support for adding dynamic variables (e.g., date) to file names
3.The ability to specify separate output folders for each report definitionThese enhancements would improve usability and enable more efficient organization and management of report outputs.
5 votes -
Ability to log and review user-entered prompts in Box AI
After deploying Box AI to users, it would be very helpful to have the ability to log and review the prompts that users enter.
This would support security and compliance needs, such as detecting potential malicious usage and enabling proper auditing when required.Since Box is a platform where sensitive and confidential information is often stored, having this capability is important for safely leveraging AI features.
55 votes -
Movable preview screen toolbar
When the preview screen is opened, a toolbar appears at the bottom of the screen showing the zoom factor and page number, but since it is fixed at the bottom of the page, the preview screen is partially hidden in some documents, making it difficult to see.
If this toolbar could be temporarily hidden or moved, it would make the preview screen easier to see.（日本語）
プレビュー画面を開くと、画面下に拡大率やページ数が表示されているツールバーが表示されるかと思いますが、
ページの下に固定されているため、ドキュメントによってはプレビュー画面が一部隠れてしまい、見づらいです。
このツールバーを一時的に隠したり、移動できるようにすれば、
プレビュー画面がより見やすくなると思うので、改善を希望します。48 votes -
"File that triggered the flow" variable is unavailable in Box Automate.
In Box Automate, when implementing a process triggered by a file request and selecting "Move" as the "File Action," the "File that Triggered the Flow" variable is unavailable as the file to be moved.
This variable is available in Box Relay and can be used for purposes such as distributing the triggered file to a specified folder.
Without this variable, Box Automate is clearly inferior to Box Relay.
We hope that the "File that Triggered the Flow" variable will be made available soon.
6 votes -
Feature Request: Add Folder Tree View with Result Count Display in Box Search
Currently, Box's search results page does not provide a folder tree view, making it impossible for users to visually understand how search results are distributed across the folder hierarchy. Users need the ability to exclude irrelevant department folders from their search results, but there is currently no way to get an overview of the folder structure within search results. We request the addition of a folder tree view in the search results page that displays the number of hits per folder and subfolder. This would allow users to drill down into the most relevant folders and refine their searches more effectively.
Currently, Box's search results page does not provide a folder tree view, making it impossible for users to visually understand how search results are distributed across the folder hierarchy. Users need the ability to exclude irrelevant department folders from their search results, but there is currently no way to get an overview of the folder structure within search results. We request the addition of a folder tree view in the search results page that displays the number of hits per folder and subfolder. This would allow users to drill down into the most relevant folders and refine their searches more…
3 votes -
Expose flags or metadata indicating delays for Event Stream events
We use information from the Event Stream to immediately detect actions that are prohibited by our internal rules. For this reason, knowing the timeliness and reliability of events is critical for our governance and security operations.
Box has informed us that delays can occur before events appear in the Event Stream. We fully understand that in cases such as incidents or platform-level issues, it may take time for events to be reflected, and we are not requesting that all events always be strictly real-time.
However, what we are missing today is visibility into:
Which events were delayed
How long each delayed event took to appear in the Event Stream
Requested enhancement:Provide some form of delay indicator for each event when it is delivered via the Event Stream.
For example, an additional field or flag that shows:
Whether the event was delayed beyond the normal/expected latency
The approximate delay duration or the time difference between when the event occurred and when it became available in the Event Stream
Why this matters:We rely on Event Stream data to immediately detect and respond to prohibited actions according to our internal rules.
Without any visibility into delays, we cannot distinguish between:
A normal situation where no prohibited events occurred, and
A situation where prohibited events did occur but are simply delayed in appearing in the Event Stream.
This lack of visibility makes it difficult to design robust governance, monitoring, and alerting on top of the Event Stream.
Reference:Events overview – Box Dev Docs
https://developer.box.com/ja/guides/events/index
We would greatly appreciate it if you could consider adding such delay indicators or flags for Event Stream events so that customers can better assess and manage the impact of any event delivery delays.We use information from the Event Stream to immediately detect actions that are prohibited by our internal rules. For this reason, knowing the timeliness and reliability of events is critical for our governance and security operations.
Box has informed us that delays can occur before events appear in the Event Stream. We fully understand that in cases such as incidents or platform-level issues, it may take time for events to be reflected, and we are not requesting that all events always be strictly real-time.
However, what we are missing today is visibility into:
Which events were delayed
How long each…3 votes -
I want to define multiple AI classification policies.
Only one AI classification policy can be defined in "Classification Policy". Since the policies that I want to apply to each folder are different, I want to be able to define multiple AI classification policies.
[In Japanese]
「分類ポリシー」に、AI分類ポリシーを一つしか定義できない。フォルダごとに適用したいポリシーが異なる為、複数のAI分類ポリシーを定義できるようにしたい。5 votes -
The ability to search by creator when searching workflows in the “Relay” section of the management console
The administrator will check whether there are any problems with the workflow settings owned by each user, and if there are any problems, they may discuss with the user what needs to be corrected.
Currently, workflows can be searched by name, but users cannot view a list of workflows they individually maintain, which lacks convenience.
Searching by workflow creator improves work efficiency.管理者では各ユーザー毎の所有するワークフローの設定に問題がないか確認のうえ、問題があればユーザーと一緒に修正箇所を議論することがあります。
現在はワークフローの名称で検索か可能となっていますが、各ユーザー毎に保持しているワークフロー一覧を出すことができず利便性に欠けます。
ワークフローの作成者単位で検索できることで作業の効率化が上がります。19 votes -
More flexible permission settings: control external Sign sending
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,…
31 votes -
Past password changes included in the report.
Currently, it is possible to check the date and time of the last password change, but we have confirmed that past password change history is not included in the report.
Being able to check how frequently passwords are changed will also help improve security.現在、最後にパスワード変更した日時を確認することは可能ですがこれまでに変更された実績がレポートに載らないことを確認してます。
どれくらいの頻度で変更されているのか確認できることでセキュリティ向上にも繋がります。14 votes -
Box for MIP
Allow a single Microsoft Tenant to connect to more than one Box EID. We have two box EID's, one for "regular" content and the other for "FTI".
13 votes -
Removal of BoxAI’s limits or publication of the limit values
There is a daily usage limit for BoxAI, and this has led to complaints from within the company.
As an administrator, I do not know the limit values and am unable to respond.
Can anything be done about this situation where internal users cannot use it freely?
At the very least, please publish the limit values or release a new plan without limits.2 votes -
Reference loop variables in a conditional branch within the loop in Box Automate workflow
In a Box Automate workflow, when looping through files, we need to be able to run conditional checks on values/properties of the file within that loop.
Potential use case: a user may want the workflow to ignore certain file types, or to only run Box AI Agent operations on certain files.
Currently, many variables can be referenced within the "conditional split" element within a "loop" element, but not the loop variables themselves.
5 votes -
Allow admins to control which Prompt Library items are visible at the tenant level
▼What problem could Box solve for you?
Box AI Home provides access to the Prompt Library, which helps users start with predefined prompts. However, in enterprise environments, not every prompt or prompt library is appropriate for every tenant, department, or business process.Administrators need the ability to control which prompt libraries are shown or hidden for their organization. Without this control, users may see prompts that are not relevant to their business, not aligned with internal policies, or not suitable for their industry-specific workflows.
▼Requested enhancement
Please add tenant-level administrative controls for the Prompt Library, allowing admins to:- View all prompt libraries available to the tenant.
- Choose which prompt libraries are displayed to users.
- Hide prompt libraries that are not relevant or not approved for organizational use.
- Optionally configure visibility by user group, department, or role.
- Provide a preview of the end-user Prompt Library experience from the admin console.
▼Business impact / use case
In large enterprises, administrators are responsible for ensuring that AI features are adopted in a controlled and policy-aligned way. If the Prompt Library contains too many prompts, or prompts that do not match the organization’s use cases, users may become confused or may use prompts that do not fit internal guidelines.For example, an organization may want to display only prompts related to document summarization, policy review, and meeting preparation, while hiding prompts related to sales, marketing, legal, or other functions that are not relevant to the tenant’s rollout plan.
This would also help organizations phase their Box AI adoption. Admins could start with a limited set of approved prompts, then gradually enable additional libraries as internal training and governance mature.
▼Expected outcome
Admins can curate the Prompt Library experience for their tenant, improving usability, reducing confusion, and supporting safer Box AI adoption at scale.
プロンプトライブラリの表示対象をテナント単位で管理者が制御できるようにしてほしい
▼Boxに解決してほしい課題
Box AI Homeではプロンプトライブラリにアクセスでき、ユーザーはあらかじめ用意されたプロンプトを利用してAI活用を開始できます。一方で、エンタープライズ環境では、すべてのプロンプトライブラリがすべてのテナント、部門、業務プロセスに適しているとは限りません。管理者として、組織の方針や利用目的に合わせて、ユーザーに表示するプロンプトライブラリと表示しないプロンプトライブラリを選択できる必要があります。現状のままでは、業務に関係のないプロンプトや、社内ポリシーに沿わない可能性のあるプロンプトが一覧に表示され、ユーザーの混乱や誤った利用につながる懸念があります。
▼要望内容
プロンプトライブラリについて、管理者がテナント単位で以下を設定できるようにしてほしいです。- テナントで利用可能なプロンプトライブラリの一覧を管理者が確認できる。
- ユーザーに表示するプロンプトライブラリを選択できる。
- 組織で利用しない、または承認していないプロンプトライブラリを非表示にできる。
- 可能であれば、ユーザーグループ、部門、ロール単位で表示対象を制御できる。 5.管理コンソール上で、エンドユーザーにどのように表示されるかをプレビューできる。
▼業務上の効果・ユースケース
大企業では、AI機能の展開において、管理者が社内ポリシーやガバナンスに沿った形で利用範囲を設計する必要があります。プロンプトライブラリに表示される項目が多すぎる場合や、自社の業務に合わないプロンプトが表示される場合、ユーザーが混乱したり、社内ルールに沿わない利用をしてしまう可能性があります。例えば、導入初期には「文書要約」「社内規程確認」「会議準備」に関するプロンプトのみを表示し、営業、マーケティング、法務など他部門向けのプロンプトは非表示にしたいケースがあります。
また、Box AIの展開を段階的に進める際にも、管理者が承認済みのプロンプトライブラリのみを先に表示し、社内トレーニングや運用ルールが整った段階で追加のライブラリを有効化できると、より安全かつ計画的にAI活用を進められます。
▼期待される結果
管理者がテナント単位でプロンプトライブラリの表示内容を管理できるようになり、ユーザーの利便性向上、混乱の抑制、Box AIの安全かつ統制された利用促進につながります。▼What problem could Box solve for you?
Box AI Home provides access to the Prompt Library, which helps users start with predefined prompts. However, in enterprise environments, not every prompt or prompt library is appropriate for every tenant, department, or business process.Administrators need the ability to control which prompt libraries are shown or hidden for their organization. Without this control, users may see prompts that are not relevant to their business, not aligned with internal policies, or not suitable for their industry-specific workflows.
▼Requested enhancement
Please add tenant-level administrative controls for the Prompt Library, allowing admins to:- View all…
6 votes
- Don't see your idea?