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
3 results found
-
Box Integartion with Power bi
hi Team,
We have a use case in which we are storing all our data in side the Box. For visualization purpose we are using PowerBi.Issue faced- Unable to perfrom PowerBI Integration with BOX Through web connector. Could you please provide connector or Any other alternative approach to accomplish this use case.
Please suggest !
89 votesHello, unfortunately this is not on our roadmap at this time. Please feel free to continue leaving feedback and comments, as we may consider this again in the future.
-
Consistent data size output from folder and file report
Don't shorten, or allow us to choose if we want the file sizes shortened (KB, MB, GB) when calling the Files & Folders report. Full data sizes would allow for much more consistent and streamlined ingestion into data analytics tools like PowerBi.
8 votes -
Data Insights for Box Tasks
I am looking for a way to see a matrix of box tasks for each member of my team with their status, completion, etc. for all members of my team. Ultimately a dashboard view that indicates the number of tasks received, approved, denied, completed, outstanding, and overdue. Alternatively, a data connection to Monday.com or PowerBi would assist in seeing where we are at individually and as a team.
3 votes
10051 results found
-
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.
47 votesHi everyone,
We've heard your feedback and added a new setting to manage the sharing window in version 2.55. You can access it by opening the Box Drive Search UI, clicking Settings, and selecting Preferences.
Thank you for your patience as this update rolls out to enterprise users.
-
Request to Pool the Box Agent Daily Limit Across the Entire Enterprise
Box AI Home, Documents, Hubs, and Notes now have daily token limits, which I believe are applied on a per-user basis. We strongly request the development of a feature that would allow the limit to be pooled across the entire Enterprise and allocated by admins to specific users or groups.
e.g. Some users do not use AI that often, so we would like to allocate their unused quota to users who actively use AI.
【日本語】
Box AI Agentにはユーザーごとの日時利用トークン数制限がありますが、これをテナント全体でプール（共有化）し、必要なユーザーやグループに割り当てる機能を開発してほしい。AIをあまり利用しないメンバーの利用枠を積極的に利用するメンバーへ割り当てたい。44 votes -
Enable processing in folders with editor permissions in Box Automate
Currently, due to Box restrictions, if the option “Limit sending invitations to collaborators to folder owners and co-owners only” is enabled for a folder specified in an Automate flow, and the flow owner specifies a folder to which they have been invited as an editor, errors will occur for “task assignments, file operations, and folder operations,” causing the process to fail.
Many companies allow co-owners and higher-level users to be invited, but if that were the case, it would significantly reduce usability under the current system. Therefore, I would like the workflow to function properly even when folders with editor permissions are set up.
現在、Boxの制限事項によりAutomateのフローに指定したフォルダが「コラボレータへの招待の送信をフォルダ所有者と共同所有者のみに制限する」有効の場合、フロー所有者が編集者として招待されているフォルダを指定すると、"タスクの割り当て、ファイル操作、フォルダ操作"いずれもエラーが発生し処理に失敗します。
多くの企業が共同所有者以上を招待可能にしていると思われますが、そうなりますと現在の動作においては非常に利便性が低下してしまうため、編集者権限のフォルダを指定してもフローを正常に動作できるようにしてほしいです。
Currently, due to Box restrictions, if the option “Limit sending invitations to collaborators to folder owners and co-owners only” is enabled for a folder specified in an Automate flow, and the flow owner specifies a folder to which they have been invited as an editor, errors will occur for “task assignments, file operations, and folder operations,” causing the process to fail.
Many companies allow co-owners and higher-level users to be invited, but if that were the case, it would significantly reduce usability under the current system. Therefore, I would like the workflow to function properly even when folders with editor…
56 votes -
I want to check the remaining tokens until the daily usage limit for the Box Agent.
Currently, a daily usage limit for the Box Agent is set for each user, but users are unable to check the limit or their current consumption status. As a result, restrictions are suddenly applied, impairing user convenience.
We request the addition of a feature on the user interface that allows users to self-manage their AI usage by checking token consumption status and the remaining available amount until the limit.（日本語）
現在、ユーザーごとに1日あたりのBox Agentの利用上限が設定されていますが、ユーザー側からは上限値や現在の消費状況が確認できない状態です。そのため、制限が突然かかってしまい、ユーザーの利便性が損なわれています。
ユーザー自身でAI利用の自己管理ができるように、トークンの消費状況や上限までの残り利用可能量など、ユーザーインターフェース上で確認できる機能の追加を要望します。26 votes -
Task Feature in Box Automate
In the current Box Automate, the Task outcome fails when the folder or enterprise setting is "Only folder owners and co-owners can send collaborator invites", which we understand is officially stated on the Box Support page.
However, many companies in Japan use this configuration, making the Task feature in Box Automate practically unavailable.Our understanding was that Box had initially stated the existing Box Relay features would remain available after the upgrade to Box Automate. If that is not the case, this may impact customers’ existing business operations, which we consider to be a concern.
We would like to request a product enhancement so that the Task feature would be usable in Box Automate even when the “Only folder owners and co-owners can send collaborator invites” setting is enabled.
>About Box Automate:
>The Task outcome fails when the folder or enterprise setting is “Only folder owners and co-owners can send collaborator invites.”
Link:https://support.box.com/hc/en-us/articles/51191250727955-About-Box-Automate#:~:text=The%20Task%20outcome%20fails%20when%20the%20folder%20or%20enterprise%20setting%20is%20%22Only%20folder%20owners%20and%20co%2Downers%20can%20send%20collaborator%20invites.%22＜Box Automateのタスク機能について＞
フォルダやEnterprise設定において、[コラボレータへの招待の送信をフォルダ所有者と共同所有者のみに制限する]設定が有効化されている場合、Box Automateのタスク機能が利用できません。 この動作は、現在の既知の制限事項に該当し、仕様と理解しております。 ※こちらの設定が有効化されている場合、Box Automateの作成者が所有者/共同所有者の場合も、タスク機能は利用できませんしかしながら、日本企業では、多くの場合こちらの設定が有効化されているため、Box Automateでタスク機能が利用できないことになります。 当初、Box社からは「Box Relayと同様の設定がBox Automateで可能」と説明を受けていたため、タスク機能が実質利用不可となっており非常に残念です。
Box Automateにおいて、[コラボレータへの招待の送信をフォルダ所有者と共同所有者のみに制限する]設定が有効化されている場合でも、タスク機能を利用可能となるように機能改善をお願いいたします。
＞Box Automateについて： ＞フォルダや企業の設定が [コラボレータへの招待の送信をフォルダ所有者と共同所有者のみに制限する] に設定されている場合は、タスクの結果が失敗します。
In the current Box Automate, the Task outcome fails when the folder or enterprise setting is "Only folder owners and co-owners can send collaborator invites", which we understand is officially stated on the Box Support page.
However, many companies in Japan use this configuration, making the Task feature in Box Automate practically unavailable.Our understanding was that Box had initially stated the existing Box Relay features would remain available after the upgrade to Box Automate. If that is not the case, this may impact customers’ existing business operations, which we consider to be a concern.
We would like to request…
36 votes -
External Notification Support
Allow for notifications to be sent to external (non-box users) partners, vendors, submitters, etc as part of an automate workflow.
Box Forms and File Request allow for seamless ingestion of content and metadata but does not allow for an easy way to update those submitters after their document has been ingested. Many times there is a formal internal review process where a submitter would want to receive an email notification as the document or application moves through the review process inside of Box.
Example use cases: notifying an external submitter that their submission has been rejected after an internal approval workflow. Sending an email receipt to the email provided in a Box Form confirming receipt of documents.
Allow for notifications to be sent to external (non-box users) partners, vendors, submitters, etc as part of an automate workflow.
Box Forms and File Request allow for seamless ingestion of content and metadata but does not allow for an easy way to update those submitters after their document has been ingested. Many times there is a formal internal review process where a submitter would want to receive an email notification as the document or application moves through the review process inside of Box.
Example use cases: notifying an external submitter that their submission has been rejected after an internal approval…
33 votes -
Real-time reporting on box STATUS
I think that the timing of updates regarding outage detection and recovery information on the status page is somewhat slow.
I understand the situation that information should be posted officially only after thorough investigation, however some social media platforms like X and third-party outage monitoring services provide faster alerts.
I would like to improvements in real-time reporting.
Once an outage occurs, I receive inquiries not only from within the company but also from external partners. As an administrator, I need to be able to access this information quickly.障害検知や復旧情報について、Statusサイトへ掲載されるタイミングやや遅いと思います色々調査したうえで公式情報として掲載されるのは理解しますが、XなどのSNSや他の障害検知サービスのほうが速報性があります。リアルタイム性をもう少し改善してほしいです。障害発生に関しては、社内だけでなく、外部からの問い合わせ（外部コラボしている取引先）も来るので、管理者として早く情報をCatchしたいです
12 votes -
Folder event in Automate
Please read the following on the assumption of a tenant where, under Enterprise settings, "Restrict invites" is checked and users with Editor permission cannot invite others.
When trying to create a new workflow in Automate, folders where the user was invited as an Editor cannot be selected at all. For many flow triggers — such as file events, folder events, and sending file requests — folder selection is not possible.
In the past, in cases where Relay was opened up to managed users (who are often invited as Editors), those users can create almost no workflows in Automate. This is because only a limited number of people, such as IT staff or Box administrators, hold Co-owner or higher permissions.
For example, why can't a person who has Editor permission on a given folder create a simple workflow that sends a notification to the other managed users or to themselves when a new file is uploaded to that folder? It seems a bit too strict.この投稿はEnterprise設定で「招待を制限する」がチェックされており、Editor権限を持つユーザーが他のユーザーを招待できないテナントを想定しています。
Automateで新しいワークフローを作成しようとすると、ユーザーがEditorとして招待されたフォルダは一切選択できません。ファイルイベント、フォルダイベント、ファイルリクエストの送信など、多くのフローのトリガーではフォルダの選択ができません。
過去に、Relayがマネージドユーザー（多くの場合Editorとして招待される）に開放された場合、それらのユーザーはAutomateでほとんどワークフローを作成できませんでした。これは、ITスタッフやBox管理者など、ごく一部のユーザーのみがCo-owner以上の権限を持っているためです。
例えば、特定のフォルダでEditor権限を持つユーザーが、そのフォルダに新しいファイルがアップロードされたときに、他のマネージドユーザーまたは自分自身に通知を送信する簡単なワークフローを作成できないのはなぜでしょうか。少し厳しすぎるように思えます。Please read the following on the assumption of a tenant where, under Enterprise settings, "Restrict invites" is checked and users with Editor permission cannot invite others.
When trying to create a new workflow in Automate, folders where the user was invited as an Editor cannot be selected at all. For many flow triggers — such as file events, folder events, and sending file requests — folder selection is not possible.
In the past, in cases where Relay was opened up to managed users (who are often invited as Editors), those users can create almost no workflows in Automate. This is…13 votes -
Provide a safe way to re-verify already-registered domains
The only current self-service workaround is to delete and re-add a domain to trigger DNS verification. If the domain is already in active use, this carries a risk of operational disruption. We request a way to re-verify a registered domain without removing it, eliminating this risk.
This would allow admins to resolve verification issues more quickly and safely, without introducing unnecessary risk into the production environment.
(In Japanese / 日本語)
安全に登録済ドメインのDNS検証を行う方法を提供してほしい現在Box社依頼なしでできる対処法は、登録済のDNSを一旦削除→再登録によるDNS検証実施だが、そのドメインが既に利用されている場合、業務影響を及ぼす可能性があります。 そのようなリスクを伴わない方法でドメインを再検証できるようにしてほしいです。
これにより、管理者は本番環境に余計なリスクを持ち込まずに、検証上の問題をより早く安全に解消できるようになります。
18 votes -
Make it clear whether a registered domain has been DNS-verified
Unfortunately, domains specified at the time of tenant creation are not recognized as verified domains, and therefore all unmanaged users under that corporate domain may fail to appear as unmanaged users. On top of that, admins cannot distinguish this state from the Admin Console, which leaves us continuously exposed to the risk of free accounts. This is a very serious and disappointing limitation, so we would like this state to be clearly identifiable.
Requested enhancement:
- Clearly distinguish initially registered domains from DNS-verified domains in the Admin Console.
- If the required DNS verification has not been completed and unmanaged users therefore will not appear, please display a clear warning in the UI.Under the current specification, admins cannot reliably determine the true verification status of a domain. As a result, accounts under corporate domains that should be visible and governed can remain outside administrative visibility and control. This is not just confusing—it could lead to serious governance, compliance, and security risks.
（In Japanese / 日本語）
テナント作成時に指定したドメインは、残念ながら検証済ドメインとして認められておらず、管理対象外ユーザーとして表示されないのが現状です。その上、管理コンソールからも識別することが出来ず、我々はフリーアカウントという驚異にさらされ続けます。これは非常に残念です。そのため、識別できるようにして欲しいです。Requested enhancement:
・Admin Consoleで初期登録ドメインと DNS 検証済みドメインを明確に区別できるようにしてほしい
・必要条件であるDNS検証を行っていない場合、管理対象外ユーザーが表示されないことになるが、そのことをUI 上で明確に警告してほしい現状の仕様では、管理者がドメインの真の検証状態を確実に判別できず、本来可視化・統制されるべき企業ドメイン配下のアカウントが管理の外に残り得ます。これは単なる分かりにくさではなく、ガバナンス・コンプライアンス・セキュリティ上の重大なリスクにつながる恐れがあります。
Unfortunately, domains specified at the time of tenant creation are not recognized as verified domains, and therefore all unmanaged users under that corporate domain may fail to appear as unmanaged users. On top of that, admins cannot distinguish this state from the Admin Console, which leaves us continuously exposed to the risk of free accounts. This is a very serious and disappointing limitation, so we would like this state to be clearly identifiable.
Requested enhancement:
- Clearly distinguish initially registered domains from DNS-verified domains in the Admin Console.
- If the required DNS verification has not been completed and unmanaged…18 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分類ポリシーを定義できるようにしたい。19 votes -
Request for Improvement of BOX Drive Proxy Server Authentication Response Function
BOX Drive is not working properly in our environment.
We recognize that BOX Drive is designed to read Pac files, but the communication is succeeding up to the proxy server according to the Pac file.
However, it seems that it is not able to respond to the authentication response of the proxy server.As a result, when we open files in our Office products (Excel and Word) that cannot be opened in a web browser, we have to download the file once from
BOX.
This method is not productive for us.As a solution, we would like to be able to use BOX Drive to open files directly from Office products (Office desktop applications).
Please consider improving the support for proxy authentication responses.Please note that SSL decoding is not performed for communications to BOX.
Thank you very much for your time.
(Japanese)
BOX Driveのプロキシサーバー認証応答機能改善のお願い弊社環境において、BOX Driveが正常に動作しておりません。
BOX DriveはPacファイルを読み込む仕様と認識していますが、Pacファイルに従ってプロキシサーバーまでは通信が成功しています。
しかし、プロキシサーバーの認証応答に対応できていないようです。これにより、弊社ではWebブラウザ上で開けないファイルをOffice製品（ExcelやWord）で開く際、
BOXからファイルを一旦ダウンロードする必要があります。
この方法では生産性が低下してしまいます。解決策として、BOX Driveを活用し、Office製品（Officeのデスクトップアプリ）から直接ファイルを開けることが望ましく、
プロキシ認証応答への対応機能の改善をぜひご検討いただきたく存じます。なお、BOX宛の通信に関してはSSLのデコードは行っておりません。
お忙しいところ恐縮ですが、何卒よろしくお願い申し上げます。
BOX Drive is not working properly in our environment.
We recognize that BOX Drive is designed to read Pac files, but the communication is succeeding up to the proxy server according to the Pac file.
However, it seems that it is not able to respond to the authentication response of the proxy server.As a result, when we open files in our Office products (Excel and Word) that cannot be opened in a web browser, we have to download the file once from
BOX.
This method is not productive for us.As a solution, we would like to be able…
120 votes -
Allow control over Box notification emails
Currently, notification emails are sent immediately whenever users or groups are granted access to Box content (such as folders, files, or Box Hubs).
Please provide the ability to control whether these notification emails are sent and when they are sent, helping organizations manage large-scale migrations, organizational changes, and phased rollouts more smoothly.
12 votes -
Show Shield-flagged files in the folder list, and tell users when a folder download skips them
When Shield flags a file as malicious, there is no way to see that in All Files or the folder list. Users have to open each file to find the red banner. If someone downloads the whole folder, the flagged file is left out of the download and there is no notice of what was skipped.
Please add a clear indicator on flagged files in the folder view, and tell the user when a folder download omits a flagged file. End users should not have to click every item, and they should not lose content silently.
9 votes -
We would like to obtain access logs for Box Hubs.
I would like information about users accessing Hubs to be visible in the Activity Report.
Currently, the only Hub-related information that can be obtained in the Activity Report is the history of using Box AI for Hubs and records of Hub admins inviting users.
It would be very helpful if the Activity Report could display which user accessed which Hub and when.
誰が、いつ、どの Hubにアクセスしたかをアクティビティレポートで表示したいです。
現在は、アクティビティレポートにログを残すにはBox AI for HubでAIの機能を利用したり、Hubの管理者がコラボレータを招待したりした時でないとレポートに記録されません。11 votes -
API included with Box license neesd to be a per-user basis rather a uniform number of grants
Please allocate the API calls included with the license on a per-user basis rather than per tenant (EID).
With the current EID-based allocation, large organizations find it difficult even to conduct limited trials. This has become a blocker to starting projects because they cannot confidently justify purchasing additional API calls. While the current allocation may be sufficient for EIDs with a small number of users, applying the same allocation across EIDs of vastly different sizes is unfair.
【日本語】
ライセンスに付帯するAPI数はテナント単位で【一律】ではなくユーザー数に応じた数を付与してほしい現在Boxライセンスに付帯するAPIはテナント（EID）単位で付与されていますが、これは小規模テナントでは問題なく試行できるとしても、大規模テナントでは正式購入に向けた試行さえも困難な付与数です。ある程度ユーザー数に応じた付与数を確保することでAPIを必要とするプロジェクトの開始を支援できるようになります。
8 votes -
AI Units included with Box license neesd to be a per-user basis rather than a uniform number of grants
Please allocate the AI Units included with the license on a per-user basis rather than per tenant (EID).
With the current EID-based allocation, large organizations find it difficult even to conduct limited trials. This has become a blocker to starting projects because they cannot confidently justify purchasing additional AI Units. While the current allocation may be sufficient for EIDs with a small number of users, applying the same allocation across EIDs of vastly different sizes is unfair.
【日本語】
ライセンスに付帯するAIユニットはテナント単位で【一律】ではなくユーザー数に応じた数を付与してほしい現在Boxライセンスに付帯するAIユニットはテナント（EID）単位で付与されていますが、これは小規模テナントでは問題なく試行できるとしても、大規模テナントでは正式購入に向けた試行さえも困難な付与数です。ある程度ユーザー数に応じた付与数を確保することでAIユニットを必要とするプロジェクトの開始を支援できるようになります。
8 votes -
Hub Collaboration Report
Box Hubs is a convenient feature that we use in our daily operations.
We would like to regularly perform checks to make sure there are no users who have been unintentionally invited to our Hubs.Currently, we can check this through the UI, such as the Admin Console or the [Share] screen of each relevant Hub, but there is no way to obtain a list.
If there were a function similar to the Collaboration Report that could export a report of all users invited to each Hub, our work would be much smoother.
Hubに意図せず招待されたユーザーがいないか定期的に棚卸作業を実施したいです。
現在は、管理コンソールや対象のHub画面の[共有]などUI上から確認できますが、一覧を取得する方法がありません。
コラボレーションレポートのように各Hubに招待されているユーザーをレポートで出力できる機能を実装してほしいです。35 votes -
Increase of the upper limit on the number of metadata templates that can be created and permission management for metadata templates
Currently, our company has a wide variety of unstructured data, and we would like to make use of metadata templates. However, there are significant differences in the templates that each on-site team wants to use. At present, metadata templates can only be created up to 500 per tenant, which leads to competition over templates. We would like to be able to create an almost unlimited number of metadata templates.
In addition, once a metadata template is created, it becomes viewable across the entire tenant, which feels inconsistent with Box’s underlying philosophy of content-level permission management. We would like metadata templates as well to be controllable by permissions, from viewing to actual usage.ーー日本語ーー
現在、当社では様々な非構造データがあるため、メタデータテンプレートを活用したいと考えているが、各現場で利用したいテンプレートにかなりの差異がある。
しかしメタデータテンプレートは現在テナント上で500個までしか作成が出来ないため、テンプレートの取り合いが発生してしまう。
無制限に近い数のメタデータテンプレートが作成できるようになってほしい。また、現在はメタデータテンプレートを作成するとテナント内すべてで閲覧ができるようになってしまうが、これはBoxの各コンテンツの権限管理の思想と乖離しているように感じます。
メタデータテンプレートも閲覧から利用の範囲が権限でコントロールできるようになってほしい。Currently, our company has a wide variety of unstructured data, and we would like to make use of metadata templates. However, there are significant differences in the templates that each on-site team wants to use. At present, metadata templates can only be created up to 500 per tenant, which leads to competition over templates. We would like to be able to create an almost unlimited number of metadata templates.
In addition, once a metadata template is created, it becomes viewable across the entire tenant, which feels inconsistent with Box’s underlying philosophy of content-level permission management. We would like metadata templates…18 votes -
Box Sign for Autodesk Integration
Build a productized, out-of-the-box Box Sign integration for Autodesk. This will allow customers to replace current eSignature integrations with Box Sign without bespoke iPaaS, custom scripting, or one-off engineering, preserving user experience and automation while reducing costs.
Request to Build a Box Sign Autodesk connector that:
- Creates Box Sign envelopes via API from Autodesk-generated documents.
- Subscribes to Box Sign webhooks for lifecycle events and updates Autodesk objects.
- Transfers signed artifacts into Autodesk commitment attachments via Autodesk APIs.
- Ensures attachments continue to sync to Box files.
- Provide a template-mapping UI in Autodesk and comprehensive admin documentation.
Aim to embed logic in the connector so customers avoid custom codeBuild a productized, out-of-the-box Box Sign integration for Autodesk. This will allow customers to replace current eSignature integrations with Box Sign without bespoke iPaaS, custom scripting, or one-off engineering, preserving user experience and automation while reducing costs.
Request to Build a Box Sign Autodesk connector that:
- Creates Box Sign envelopes via API from Autodesk-generated documents.
- Subscribes to Box Sign webhooks for lifecycle events and updates Autodesk objects.
- Transfers signed artifacts into Autodesk commitment attachments via Autodesk APIs.
- Ensures attachments continue to sync to Box files.
- Provide a template-mapping UI in Autodesk and comprehensive admin documentation.…24 votes
.png){kind=link}
- Don't see your idea?