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
9986 results found
-
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…
23 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…
23 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…
118 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検証実施だが、そのドメインが既に利用されている場合、業務影響を及ぼす可能性があります。 そのようなリスクを伴わない方法でドメインを再検証できるようにしてほしいです。
これにより、管理者は本番環境に余計なリスクを持ち込まずに、検証上の問題をより早く安全に解消できるようになります。
15 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…15 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…
18 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…17 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に招待されているユーザーをレポートで出力できる機能を実装してほしいです。31 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 -
Add support in Box UI Elements for users to rename files before upload is completed in mobile/embedded experience
This enhancement would improve document capture workflows where meaningful filenames are needed at the point of upload for easier identification, retrieval, and downstream usability. Today, the lack of rename-during-upload support creates friction for mobile use cases, reduces efficiency when many similar files are uploaded, and can force teams to rely on custom upload logic instead of standard Box UI Elements.
Requested enhancement:
• Allow users to edit filenames before upload commit
• Ensure the experience works well on mobile form factors
• Preserve the user-defined filename in Box after upload
• Optionally support configurable naming rules or validations for admins and developersBusiness value:
• Improves usability in mobile document capture workflows
• Increases searchability and operational efficiency
• Reduces dependence on custom integrations
• Strengthens adoption of Box-native embedded experiencesThis enhancement would improve document capture workflows where meaningful filenames are needed at the point of upload for easier identification, retrieval, and downstream usability. Today, the lack of rename-during-upload support creates friction for mobile use cases, reduces efficiency when many similar files are uploaded, and can force teams to rely on custom upload logic instead of standard Box UI Elements.
Requested enhancement:
• Allow users to edit filenames before upload commit
• Ensure the experience works well on mobile form factors
• Preserve the user-defined filename in Box after upload
• Optionally support configurable naming rules or validations for admins and…12 votes -
Add Ability to Duplicate an Existing Box Form
Please add a feature that allows users to duplicate an existing Box Form, including all fields, structure, metadata mappings, and settings. Users should be able to clone a form, rename it, and make edits without rebuilding from scratch.
Why This Matters
Saves significant time when creating similar forms across departments, programs, or agencies.
Reduces errors by ensuring consistent fields, metadata, and logic across related forms.
Enables scalable templates, especially for public sector workflows like procurement, HR, inspections, grants, benefits, and compliance.
Accelerates PS SE and customer builds, allowing faster demos, labs, and solution rollouts.
Supports versioning needs, since agencies routinely update forms as policies and regulations change.
Impact
Faster solution deployment, higher form adoption, reduced build errors, and more repeatable patterns for enterprise and public sector customers.
Please add a feature that allows users to duplicate an existing Box Form, including all fields, structure, metadata mappings, and settings. Users should be able to clone a form, rename it, and make edits without rebuilding from scratch.
Why This Matters
Saves significant time when creating similar forms across departments, programs, or agencies.
Reduces errors by ensuring consistent fields, metadata, and logic across related forms.
Enables scalable templates, especially for public sector workflows like procurement, HR, inspections, grants, benefits, and compliance.
Accelerates PS SE and customer builds, allowing faster demos, labs, and solution rollouts.
Supports versioning needs, since agencies routinely…
36 votes -
Admin-controlled AI model governance
Public sector and other regulated customers need stronger admin governance over Box AI model behavior. While admins can select a primary AI model today, they cannot control what happens if that model becomes unavailable. For FedRAMP, CJIS, and procurement-constrained environments, automatic failover to an unspecified model introduces compliance and risk concerns. Box should allow admins to select a primary (default) AI model, restrict usage to an approved model list, and explicitly define fallback behavior if the primary model goes down: either fail over to an admin-approved backup model or automatically disable Box AI. That the list of AI Providers in the AI settings tab MUST include all families of LLMs This ensures deterministic, compliant AI behavior aligned to agency authorization, vendor approval, and risk management requirements, while preventing exposure to unapproved models.
Public sector and other regulated customers need stronger admin governance over Box AI model behavior. While admins can select a primary AI model today, they cannot control what happens if that model becomes unavailable. For FedRAMP, CJIS, and procurement-constrained environments, automatic failover to an unspecified model introduces compliance and risk concerns. Box should allow admins to select a primary (default) AI model, restrict usage to an approved model list, and explicitly define fallback behavior if the primary model goes down: either fail over to an admin-approved backup model or automatically disable Box AI. That the list of AI Providers in…
30 votes -
Add Table Layout and Inline Image Support in Box Hubs Content
We’re evaluating Box Hubs as a replacement for our internal SharePoint-based portal, and we’d like a few additional design capabilities.
Specifically, we’d like
(1) a table-style layout option for presenting information in a structured format.
(2) the ability to paste or insert images directly within Hub content.
These features would help us create clearer, more portal-like pages without relying on external tools.（日本語）
SharePoint上に構築している社内ポータルの代替としてHubを検討しており、デザイン面の機能追加を要望します。
具体的には、
(1)情報を整理して見せられる表形式のデザイン（レイアウト）オプション
(2)Hubのコンテンツ内に画像を直接貼り付け・挿入できる機能
これらがあると、外部ツールに頼らずポータルらしい見やすいページを作成できます。23 votes -
Create shared link to a nested page in a Box Hub
Our Box Hubs audience consists of mostly external partners, so we design our Box folder structure and Box Hubs with a novice user in mind. For a critical marketing campaign, I have created a nested page in our main partner shared Hub, but I don't have the ability to create a shared link for just that page that I can post in a call out on our separate partner-specific "sub Hubs." My callout includes instructions to look for the page on the left nav, but it would be nice to be able to link directly to the nested page.
39 votesHi! We are looking into this idea to define the priority
-
Automatically resize input text within defined Box Sign text fields.
Allow text fields added to a Box Sign document to automatically resize the text based on inputs. When used as form fill fields for signers/approvers, text will wrap or extend outside of defined field size. Additional logic to notify users who are inputting text that their text cannot shrink/scale appropriately would also be beneficial.
15 votes -
Support PIV/CAC Authentication for Box Sign Ready-Sign Links
I am requesting that PIV/CAC authentication is supported in Ready-Sign links.
Without PIV signature requests via Ready-Sign link or Automate, federal agencies are left to templates and manual signature requests. This prevents them from implementing broad, end-to-end workflows that involve compliant signatures (e.g., onboarding and offboarding).
8 votes -
Hubs Draft State/Autosave Feature
Implement a 'Draft' state for Hubs.
Example: A feature to have a Hubs 'auto save' option, once it's been generated. They have some users who may close out of the Hub before hitting 'save' and lose all of their work.
10 votes -
Want to allow users with 0byte allocated storage to save Box AI Home responses.
We understand that Box AI Home answers cannot be saved when "Allocated Storage" is set to 0 bytes or insufficient — by design.
However, our company requires end users to have 0 bytes of allocated storage, which prevents them from saving AI Home answers. We request that this limitation be removed to improve usability.「割り当て済みストレージ」を0バイトに設定 or 十分な容量が割り当てられていない場合、Box AI Homeの回答を保存できないことはBoxの仕様と伺っています。
しかしながら会社の都合上、エンドユーザーには「割り当て済みストレージ」を0バイトに設定しており、結果としてAI Homeの回答が保存できません。
利便性向上のため、「割り当て済みストレージ」を0バイトのユーザーでも回答を保存できるようにしてほしいです。7 votes -
Box Shield MIP Integration with GCC High
For customers with GCC High environments (Microsoft), Purview is not currently able to be integrated using the Box Shield integration (as it can be with the commercial version of Purview) to map the MIP Sensitivity labels with Box Shield's classification labels. We would like to see Box Shield to be able to integrate with Purview when it lives in Microsoft's non-commercial environments, including GCC High and DOD.
40 votes -
Enable Metadata Cascading when using the Add Metadata outcome
Description
Allow users to enable metadata cascading when applying the Add Metadata outcome to a folder. This should be a user-selectable option in the workflow builder (for example, a simple "Enable metadata cascading" checkbox for this outcome).
Business Value
Many document-centric processes follow the same pattern:
- A user submits a request through a form.
- A workflow automatically creates a dedicated folder for that request.
- Documents related to the request are uploaded into that folder over time by multiple users.
While workflows can already create the folder and assign metadata to it, there is currently no way to enable metadata cascading as part of the Add Metadata outcome. As a result, newly uploaded files do not inherit the folder metadata automatically.
This creates additional manual work and prevents organizations from leveraging metadata-driven experiences, like Box Apps.
When configuring the Add Metadata outcome for a folder, users should have the option to enable metadata cascadin (and set the overwrite policy).
If selected, in addition to adding the metadatas to the folder, the metadata cascade option should also be set (https://developer.box.com/reference/post-metadata-cascade-policies) :
The metadata template and values applied to the folder will automatically cascade to files within that folder according to the metadata cascading behavior.
Newly added content should inherit the appropriate metadata without requiring additional workflows or manual intervention.Description
Allow users to enable metadata cascading when applying the Add Metadata outcome to a folder. This should be a user-selectable option in the workflow builder (for example, a simple "Enable metadata cascading" checkbox for this outcome).
Business Value
Many document-centric processes follow the same pattern:
- A user submits a request through a form.
- A workflow automatically creates a dedicated folder for that request.
- Documents related to the request are uploaded into that folder over time by multiple users.
While workflows can already create the folder and assign metadata to it, there is currently no way to enable metadata cascading…
7 votes
- Don't see your idea?