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 ~
9986 results found
-
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 -
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 -
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 -
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 -
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,…
29 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 -
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 -
Silent contextual menu Copy Shared Link on desktop
There’s a popup dialogue box every time I try to share a file from the contextual drop down menu on the desktop. This is very disruptive to the process and adds needless time. I do this frequently and Box is asking me to confirm with an extra step.
The internet is inundated with pop ups. Data privacy groups are actively trying to rescind cookie pop-ups because users are overwhelmed.
My point being, this is a bad user experience.
I understand there's a need to notify users that the system is calling out to an external app. Unfortunately, it's at the cost of user's expeience.
I recommend offering an option to turn off this feature bug. Bring back the silent contextual menu Copy Shared Link.
There’s a popup dialogue box every time I try to share a file from the contextual drop down menu on the desktop. This is very disruptive to the process and adds needless time. I do this frequently and Box is asking me to confirm with an extra step.
The internet is inundated with pop ups. Data privacy groups are actively trying to rescind cookie pop-ups because users are overwhelmed.
My point being, this is a bad user experience.
I understand there's a need to notify users that the system is calling out to an external app. Unfortunately, it's at the cost…
3 votes -
Make the new "Copy Shared Link" pop-up window optional
This new pop-up window slows down my workflow. I understand some people benefit from it, but please consider a setting to disable the window for fast, high-volume workers.
**I am one of the top Box users with my company and we spend a lot of money with you.
3 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 -
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 -
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…
20 votes -
I want to save Copilot for Microsoft 365-generated content directly to Box
Currently, when I use Copilot’s generative AI features, the only default save destination is OneDrive—Box isn’t even an option. For those of us who live and breathe Box it would be fantastic if we could save Copilot-generated content directly to Box and keep everything in one place.
Right now, every time Copilot asks, “Save to OneDrive?” I feel like saying, “Nice try, Copilot, but my heart belongs to Box!” Please help us Box fans avoid this daily heartbreak and make Box a first-class citizen for Copilot saves. Thank you!
〈Copilot for Microsoft 365で生成したコンテンツを直接Boxに保存したい〉
現在、Copilotで生成AI機能を利用し作成したコンテンツの保存先は、OneDriveがデフォルトとなっており、Boxを選択することができません。
Boxでコンテンツを一元管理するため、Copilotで生成したコンテンツの保存先にBoxを追加してほしいです。23 votes -
If there is only one app which can open a file, let the “open” button call that app.
Having to click the “open” button to hit the “open” button is infuriating. Perhaps, consider just opening the file when I click on it from the list and skipping this entire step all together? Skipping this page would be especially helpful when the preview does not reflect the current state of the document.
3 votes -
IP Address Restriction for Webapp and SELECTED API calls
We want to enable IP address restrictions only for the web app and selected applications.
Possible methods include submitting a list of client IDs exempt from restrictions during application, or providing a UI to specify an app list excluded from IP address restrictions.Currently, only the following two options are available.
- Enable only for Webapp
- Enable for Webapp and All API callsWhat we truly want is to apply IP address restrictions to the web app and BoxDrive. However, selecting “All APIs” renders nearly all other cloud-based integration apps unusable.
For example, losing integrations that significantly boost productivity—like Salesforce, Zoom, or Box connectors for Zapier and n8n—is a major issue. While we could ask providers for their IP addresses and allowlist them all, maintaining a list of potentially changing IP addresses is impossible.
Box itself recommends setting rules by domain in its firewall configuration support article, acknowledging IP addresses can change.The reason IP address restrictions via SSO cannot solve this is that they cannot prevent scenarios where employees authenticate internally, then take their device outside and access the company Box from an unspecified access point. Box's own IP address restrictions are powerful because they can prevent this, and it is essential to configure them to work alongside various integrations.
We want to enable IP address restrictions only for the web app and selected applications.
Possible methods include submitting a list of client IDs exempt from restrictions during application, or providing a UI to specify an app list excluded from IP address restrictions.Currently, only the following two options are available.
- Enable only for Webapp
- Enable for Webapp and All API callsWhat we truly want is to apply IP address restrictions to the web app and BoxDrive. However, selecting “All APIs” renders nearly all other cloud-based integration apps unusable.
For example, losing integrations that significantly boost productivity—like…21 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.
18 votes -
Allow a table in Box Forms
Allow a table in Box Forms to make entry easier for end users with copying and pasting
6 votes
.png){kind=link}
- Don't see your idea?